Syncing Agent Tiers

Push the canonical sub-agent tier definitions (executor, architect, scout, worker) into every listed repository's .claude/agents/ and .codex/agents/, opening one auto-merging PR per repository. Use after changing a tier's model or effort, when adding a repository to the sync list, or as the last step of distributing-plugins.

5 starsAI, LLMs & Agents Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add tomada1114/tomada-claude-plugins

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add tomada1114/tomada-claude-plugins --skill syncing-agent-tiers
Manual install
git clone --depth 1 https://github.com/tomada1114/tomada-claude-plugins.git /tmp/tomada-claude-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/tomada-claude-plugins/tomada-kit/skills/syncing-agent-tiers ~/.claude/skills/syncing-agent-tiers

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# syncing-agent-tiers

Repositories keep their own copies of the tier files because cloud sessions and Codex
read only what is in the repository. This skill makes those copies generated output:
the only place a tier's model or effort is written is `assets/tiers.json`.

## Rules for repositories that receive the tiers

- Repository prose (AGENTS.md, CLAUDE.md, skills) names tiers by agent name and role
  only — never a model name or an effort level. Workflow `agent()` stages that need a
  model name one in a single constant the skill defines once, not inline per stage.
- Tests check structure (the four tiers exist in both hosts, the Codex instructions
  equal the Claude body, Claude files set `model` and `effort`, Codex files omit
  `model`), never the model or effort values.
- Repository-specific agents (any other file in `.claude/agents/`) are not touched.

## Steps

1. Edit `assets/tiers.json` (models, efforts, descriptions, bodies). Keep it in step
   with `orchestrating-models`, which explains the choices.
2. Preview: `python3 scripts/sync_agent_tiers.py --dry-run`.
3. Run: `python3 scripts/sync_agent_tiers.py` (or name repos). Each repo gets a PR from
   a temporary worktree of `origin/main`, with auto-merge queued when the repository
   allows it; the local checkout is not touched. Report every PR URL and every repo
   that printed a failure or "merge it yourself".
4. After the PRs merge, bring the local checkouts up to date:
Read the full skill on GitHub

Details

Skill name
syncing-agent-tiers
Path
tomada-kit/skills/syncing-agent-tiers/SKILL.md
Repo updated
12 November 2026

FAQ

What does the Syncing Agent Tiers skill do?

Push the canonical sub-agent tier definitions (executor, architect, scout, worker) into every listed repository's .claude/agents/ and .codex/agents/, opening one auto-merging PR per repository. Use after changing a tier's model or effort, when adding a repository to the sync list, or as the last step of distributing-plugins.

How do I install the Syncing Agent Tiers skill?

Claude Code plugin: /plugin marketplace add tomada1114/tomada-claude-plugins. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Syncing Agent Tiers popular?

It lives in tomada1114/tomada-claude-plugins, which has 5 GitHub stars and 0 forks.

Related skills

Auditing Prompt Docs

5

tomada1114/tomada-claude-plugins

Audit and fix prompt-bearing documents — SKILL.md, CLAUDE.md, AGENTS.md, agent and command definitions, reference files, whole repositories — against Anthropic's published prompting guidance for current Claude models, proposing edits for approval before writing anything. Also answers how to prompt a specific model: holds the per- model guidance for Claude Fable 5.2, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5 alongside the cross-model practices. Use when reviewing or slimming an instruction file, when instructions are ignored or fire too often, when migrating a prompt to a newer m

AI, LLMs & Agents

Auditing Repositories

5

tomada1114/tomada-claude-plugins

Audit the repository you are in, often a template or an app cut from one, for technical debt and room to improve in four areas: architecture and design patterns; tests; file structure and code quality; and tooling, CI, dependencies and the agent harness. Design a safe, test-first fix for every evidenced finding, and file the findings as GitHub issues that follow the repository's own issue conventions (triaging-issues, issue forms, past issues). A finding inherited from the template is also filed in the template repository. Cheap read-only sub-agents collect the evidence and high-effort analyst

Testing & QA

Authoring Goal Prompts

5

tomada1114/tomada-claude-plugins

Author a self-contained prompt for Claude Code's /goal command, run unattended in a separate session — a lead-to-staff handoff where this session researches, designs, and decides with full context, and a fresh executor session (Opus 5.5 or Fable 5.2, with none of that context) implements. Drafts a goal with measurable done-criteria, transcript-verifiable checks, scope + anti-cheat constraints, and stop rules; packages design intent, code examples, research findings, checklists, and pre-answered decisions as support files in a per-goal state directory whenever the executor would otherwise re-de

AI, LLMs & Agents

AI Company Search

9

Lord1Egypt/RA-Skills

Search artificialintelligencecompanies.com to find AI vendors and startups serving a given niche or addressing a given problem, returning name, canonical URL, and description per match via the site's public JSON API and JSON-LD category pages.

AI, LLMs & Agents

Rethinking Prompt Assets

5

tomada1114/tomada-claude-plugins

Rethink a set of prompt assets from zero — memory files (CLAUDE.md, AGENTS.md), skills, sub-agent definitions, and the flows they form — and propose large changes: delete, merge, split, rebuild, reroute. A sub-agent blind to the current assets designs the ideal set for the jobs they serve; the current set is compared with it and with usage evidence from transcripts. Finds what a one-file review cannot: overlap and contradiction between skills, unclear ownership, skills unused or never firing, delegation that drifted from the model-assignment source, flows with wasted stages or ill-fitting agen

AI, LLMs & Agents

AI Meeting

1

bin1874/ai-meeting-skill

Run structured AI meetings for plans, product ideas, technical designs, business decisions, feature proposals, and strategy choices. Use when the user wants an AI meeting, AI roundtable, multi-agent discussion, debate, proposal review, plan review, decision review, or wants Codex, Claude Code, qoderclicn, and other CLI agents to analyze a proposal across multiple expert roles, challenge assumptions, preserve per-agent sessions, and produce a final decision report with provenance. 也适用于中文场景:方案评审、多 Agent 讨论、技术路线评审、商业决策评审。

AI, LLMs & AgentsIn 1 list

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.