Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add bdfinst/agentic-dev-team --skill agent-addgit clone --depth 1 https://github.com/bdfinst/agentic-dev-teamWrote 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-add)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/agent-add"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/agent-add.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
- medium Agent Snooping · line 44 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00096 | $0.00720 |
| Opus 5 | $0.00048 | $0.00360 |
| Sonnet 5 | $0.00019 | $0.00144 |
| Haiku 4.5 | $0.00010 | $0.00072 |
Grade A, and why
agent-add 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.
What it actually says
Agent Add
Role: implementation.
Implementation constraints
- Follow the official sub-agent schema and token budgets.
- Delegate the build to the agent-create skill; do not improvise structure.
- Be concise. Report the created agent file, no narration.
Steps
1. Parse arguments
Capture the agent name/spec or URL from $ARGUMENTS.
2. Delegate
Invoke the agent-create skill with the arguments.
3. Report
Output the created file path.
Apply the guidelines defined in skills/agent-create/SKILL.md to the current task. Read the skill file and follow its steps exactly.
If $ARGUMENTS starts with http:// or https://, fetch the URL with
WebFetch first and extract the relevant guidance, then use that content as
the agent description.
Pass these flags through to the skill as context:
--plugin <dir>→ target plugin directory (resolved by agent-create Step 0)--name <name>→ set agent name (skips name prompt)--type review|team→ set agent type (skips type prompt)--model sonnet|opus|haiku|fable|inherit|<full model ID>→ sets the agent's model (invalid values rejected against agent-contract.json)--effort low|medium|high|xhigh|max→ sets the agent's reasoning effort (invalid values rejected against agent-contract.json)--memory user|project|local/--isolation worktree/--color <color>/--max-turns <int>/--background true|false/--skills <name1,name2,...>→ optional native fields, no forced defaults--context diff-only|full-file|project-structure→ setsContext needs:field--lang <exts>→ adds language scope declaration to the body--dry→ show generated content without writing to disk or updating registry
Apply this skill to: $ARGUMENTS
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 · 64 lines · 96 tokens per session scan A d8ea430bc1ad
agent-add is a skill published in the GitHub repository bdfinst/agentic-dev-team (280 stars, last pushed 2d ago), licensed MIT. It adds 96 tokens to every session and 720 once invoked, about $0.0005 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…