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 add-plugingit 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/add-plugin)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/add-plugin"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/add-plugin.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
- medium Excessive Agency · line 27 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00046 | $0.00717 |
| Opus 5 | $0.00023 | $0.00358 |
| Sonnet 5 | $0.00009 | $0.00143 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
add-plugin 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Plugin
Role: implementation. This skill installs a Claude Code plugin and
adds it to .claude/settings.json so the project's plugin set is
reproducible.
You have been invoked with the /add-plugin skill.
Implementation constraints
- Always update settings.json. Installing without registering defeats the purpose — the whole point is reproducibility.
- Derive marketplace from the identifier. The
name@marketplaceformat encodes both; never ask the user to repeat information already in the argument. - Do not duplicate entries. Check settings.json before adding; if the plugin is already registered, report it and stop.
- Be concise. Report only the outcome — no narration of each step.
Parse Arguments
Arguments: $ARGUMENTS
Required: plugin identifier ($0) in name@marketplace format —
e.g. skill-creator@claude-plugins-official or refactoring@refactoring.
Optional:
--repo <owner/repo>: GitHub repository to register as the marketplace source before installing (e.g.elifiner/refactoring). Required for plugins not on an official marketplace.
Steps
1. Parse arguments
Extract:
NAME— the part before@in$0MARKETPLACE— the part after@in$0REPO— value of--repo, or empty string if not provided
2. Check for existing registration
Read .claude/settings.json. If enabledPlugins already contains
"<NAME>@<MARKETPLACE>": true, report:
<NAME>@<MARKETPLACE> is already registered in settings.json. Nothing to do.
and stop.
3. Register marketplace (if --repo provided)
If REPO is non-empty, run:
claude plugin marketplace add <REPO>
If this fails, report the error and stop.
4. Install the plugin
Run:
claude plugin install <NAME>@<MARKETPLACE>
If this fails, report the error and stop — do not update settings.json for a plugin that did not install successfully.
5. Add to settings.json
Add to the enabledPlugins object in .claude/settings.json:
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 · 113 lines · 46 tokens per session scan A dd392ed91569
add-plugin is a skill published in the GitHub repository bdfinst/agentic-dev-team (280 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 717 once invoked, about $0.0002 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.