Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bdfinst/agentic-dev-team/plugin install marketplace-devWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/bdfinst/agentic-dev-team/agent-create)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/agent-create"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/agent-create.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00110 | $0.05825 |
| Opus 5 | $0.00055 | $0.02913 |
| Sonnet 5 | $0.00022 | $0.01165 |
| Haiku 4.5 | $0.00011 | $0.00583 |
Grade A, and why
agent-create scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Create
Automates production of Claude Code sub-agent files that pass schema validation
and stay within token-efficiency budgets. For conventions, anti-patterns, and
registration checklists, see skills/agent-skill-authoring/SKILL.md.
Constraints
- Do not write any file until validation passes and the user confirms the draft
- Name validation is a hard gate — exit immediately if the name is invalid
- Never include
hooks,mcpServers, orpermissionModewithout explicit user confirmation after the plugin warning - Body line budgets are hard limits enforced at generation time; trim content is shown to the user before any file is written
- Registry and CLAUDE.md updates are append-only; never edit existing rows
Step 0 — Resolve Target Plugin
Determine $PLUGIN (the target plugin directory) and $NAME (the plugin's
name field from .claude-plugin/plugin.json):
- If
--plugin <dir>was passed, use that directory as$PLUGIN. - Else if exactly one
plugins/*/directory exists in the repo root, use it. - Else if the current working directory is inside a directory containing
.claude-plugin/plugin.json, use that directory. - Else ask:
Which plugin directory should the agent be added to?
Read $PLUGIN/.claude-plugin/plugin.json and extract the name field as
$NAME. All subsequent path references use $PLUGIN/ and $NAME.
Step 1 — Parse Arguments
Accept these inputs (from arguments or interactive prompts):
| Input | Required | Notes |
|---|---|---|
name |
yes | file stem of the new agent |
type |
yes | review or team |
description |
yes | one-line summary for frontmatter |
tools |
no | comma-separated tool list |
--plugin <dir> |
no | target plugin directory (resolved in Step 0) |
--model sonnet|opus|haiku|fable|inherit|<full model ID> |
no | model the agent runs on; a value is suggested and confirmed in Step 5 if omitted |
--effort low|medium|high|xhigh|max |
no | reasoning effort for this agent; a value is suggested and confirmed in Step 5 if omitted |
--memory user|project|local |
no | persistent memory scope; omitted unless specified |
--isolation worktree |
no | run in an isolated git worktree; omitted unless specified |
--color red|blue|green|yellow|purple|orange|pink|cyan |
no | display color in the task list/transcript; omitted unless specified |
--max-turns <int> |
no | cap on agentic turns before the subagent stops; omitted unless specified |
--background true|false |
no | always run as a background task; omitted unless specified |
--skills <name1,name2,...> |
no | skill names to preload into context at startup; omitted unless specified |
--context diff-only|full-file|project-structure |
no | sets Context needs: field in review body |
--lang <exts> |
no | adds language scope line to review body (e.g. Scope: .ts, .tsx files only) |
--dry |
no | display generated content without writing file or updating registry |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 550 lines · 110 tokens per session scan A 778fb7728a80
agent-create is a skill published in the GitHub repository bdfinst/agentic-dev-team (280 stars, last pushed 2d ago), licensed MIT. It adds 110 tokens to every session and 5,825 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…