new-agent
Skill1 starsChanged 12 days agoMITView on GitHub
Creates Claude Code subagents and agent plugins in foreman's format. Writes one agent file with the model, effort and tools its kind of work needs, or a whole plugin (manifest, marketplace entry, agents, an optional skill that launches them, README, changelog, license), lints agent files for fields Claude Code ignores without a warning, validates the plugin, and registers a new agent so foreman's dispatch routes work to it. Use when the user asks to create, add or write an agent or subagent, make or publish an agent plugin, turn a repeated job into an agent, check or fix an agent file, or teach foreman a new kind of work.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- AcKeskin/contexturetheir own version, first seen Nov 1, 2026
- jnotsknab/mux-swarmtheir own version, first seen Oct 11, 2026
- iDiagoValeta/claude-code-agentstheir own version, first seen Oct 8, 2026
- hcussi/claude-code-toolkittheir own version, first seen Jul 2, 2026
- InfiniteRoomLabs/agent-opstheir own version, first seen Jun 23, 2026
- jiayi-ThE-CREATOR/macos-llm-agentstheir own version, first seen Jun 12, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- jnotsknab/mux-swarm★ 9same name
- AcKeskin/contexture★ 2same name
- hcussi/claude-code-toolkit★ 1same name
- iDiagoValeta/claude-code-agents★ 1same name
- InfiniteRoomLabs/agent-ops★ 1same name
- TheLatentSpaceLab/Qubito★ 1same name
- jiayi-ThE-CREATOR/macos-llm-agents★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 50
Pin the job: before writing anything. One sentence each: what the agent does, what it gets in its brief, what it returns, whether it edits …
- Very specific: line 76
Fill every
<<fillmarker: Follow references/agent-format.md: the description says what the agent does, who calls it, and what it never … - Distinctive: line 123
Put a secret, token or personal path in an agent file or manifest.
- Very specific: line 126
Leave a <<fill marker or a lint error in a file you report as done.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
new-agent
An agent is a Markdown file: frontmatter that says when to use it and how it
runs, and a body that becomes its system prompt. Most agent files that
misbehave do so silently: an unknown field is dropped, a : in the name
skips the file, a plugin agent's permissionMode is ignored, a model other
than the session's runs at the default effort. This skill writes files that
avoid those traps and checks them with a linter that reports each one.
Request: $ARGUMENTS
The script is ${CLAUDE_SKILL_DIR}/scripts/scaffold.py (Python 3.12+,
standard library). The commands below say python3; on Windows use python
or py when python3 is not found.
Read first
- references/agent-format.md: every frontmatter field, where agent files live and which wins, and how to write the description and the body
- references/plugin-layout.md: the plugin folder, both manifests, testing locally, and publishing
Pick the mode
| the user wants | mode |
| one agent for this project or for every project | agent |
| a set of agents to share or publish | plugin |
| foreman to send a kind of work to their agent | register |
| to know why an agent file does not load or behave | lint |
Procedure
- Pin the job before writing anything. One sentence each: what the
agent does, what it gets in its brief, what it returns, whether it edits
files. A job that is really two jobs is two agents. Then pick the
closest kind from
python3 "${CLAUDE_SKILL_DIR}/../dispatch/scripts/plan.py" routes; the kind sets the default model, effort and tools. - Name it in kebab-case after the job, not the technique
(
migration-auditor, nothelperorsql-agent-v2). No:in the name. Check it is not already taken: list.claude/agents/,~/.claude/agents/and the agents the session already shows. Write it.
One agent, with
--destset to.claude/agents(this project, shared through git),~/.claude/agents(every project, only this user), or a plugin'sagentsfolder:
python3 "${CLAUDE_SKILL_DIR}/scripts/scaffold.py" agent migration-auditor --kind review --dest .claude/agents --description "<what it does and when to use it>"A plugin, one --agent NAME:KIND per agent and --skill when the agents
should run as a sequence the user can call by name:
python3 "${CLAUDE_SKILL_DIR}/scripts/scaffold.py" plugin db-crew --dest ../db-crew --agent migration-writer:implement --agent migration-auditor:review --skill- Fill every
<<fillmarker. Follow references/agent-format.md: the description says what the agent does, who calls it, and what it never does; the body gives the role, the procedure, the return block and the boundaries. Keep the return block: foreman's dispatch integrates on it. - Lint and validate until both are clean:
python3 "${CLAUDE_SKILL_DIR}/scripts/scaffold.py" lint .claude/agents
claude plugin validate <plugin folder>claude plugin validate checks manifests and paths; the lint checks the
agent fields it lets through (a bad model, effort or color, a : in the
name, misspelled fields, plugin-ignored fields).
6. Register the agent when foreman should route to it. An existing kind
is overridden for this project; a new kind needs --what and --writes
or --read-only:
python3 "${CLAUDE_SKILL_DIR}/scripts/scaffold.py" register migration-auditor --kind review --model opusThis writes .claude/foreman/routing.json. Commit it to share the route.
7. Prove it loads and works. Claude Code watches .claude/agents/ and
~/.claude/agents/ and picks up a new or edited file within seconds,
except when that agents folder did not exist when the session started
(then restart). A plugin agent needs /reload-plugins, or a session
started with claude --plugin-dir <folder>. Run the agent once through
the Agent tool on a small real task and check that the reply ends in the
return block.
Output
mode: agent | wrote .claude/agents/migration-auditor.md (kind review: sonnet, high)
lint: 0 errors, 0 warnings | validate: passed
route: review -> migration-auditor (opus) in .claude/foreman/routing.json
proof: one Agent run as migration-auditor returned the block (status done)Must not
- Overwrite an existing agent or plugin file without the user's yes
(
--force). - Give a read-only job Edit or Write, or leave
toolsopen on an agent that only reads. - Put a secret, token or personal path in an agent file or manifest.
- Publish, push, or add a marketplace for the user; hand them the commands in references/plugin-layout.md.
- Leave a
<<fillmarker or a lint error in a file you report as done.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

