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-removegit 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-remove)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/agent-remove"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/agent-remove.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector fail
SkillSpector: 1 finding, up to high
- high Tool Misuse · line 101 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00074 | $0.01531 |
| Opus 5 | $0.00037 | $0.00766 |
| Sonnet 5 | $0.00015 | $0.00306 |
| Haiku 4.5 | $0.00007 | $0.00153 |
Grade A, and why
agent-remove 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Remove
Role: implementation. This skill removes an agent and all its references from the system — it does not modify agent behavior or content.
You have been invoked with the /agent-remove skill. Fully remove a named
agent and update all required documentation.
Implementation constraints
- Confirm before deleting. Always show the user what will be removed and wait for confirmation before any destructive action.
- Detect agent type first. Review agents (declare
Model tier:) and team agents (declare persona sections) require different cleanup paths. - Remove all references. An agent that is deleted but still referenced in other files leaves the system in an inconsistent state.
- Always update documentation. Documentation steps are mandatory. Review updated docs before reporting completion.
- Be concise. Report only what changed. No narration of each step.
Parse Arguments
Arguments: $ARGUMENTS
Required: agent name ($0) — the filename stem without .md
(e.g., js-fp-review, security-engineer)
Optional:
--plugin <dir>: target plugin directory. Resolved as: this flag if given; else singleplugins/*/; else cwd ancestor with.claude-plugin/plugin.json; else ask. Stored as$PLUGIN.--dry: Show what would be removed without making changes
Steps
0. Resolve target plugin
Determine $PLUGIN using the convention above. Read
$PLUGIN/.claude-plugin/plugin.json and extract name as $NAME.
1. Locate agent file
Verify $PLUGIN/agents/<name>.md exists. If not, list all agent files
and report that the named agent was not found.
2. Detect agent type
Read $PLUGIN/agents/<name>.md:
- If it declares
Model tier:→ review agent - Otherwise → team agent
3. Show removal plan
Display a confirmation prompt listing every action that will be taken:
Remove agent: <name> (<type>) from $PLUGIN
Files to delete:
- $PLUGIN/agents/<name>.md
[review agents only — if eval fixtures exist at repo root]
- evals/$NAME/fixtures/<name>-* (if any)
- evals/$NAME/expected/<name>-* (if any)
Registry entries to remove:
- $PLUGIN/knowledge/agent-registry.md: <table row> (if file exists)
- $PLUGIN/CLAUDE.md: Quick Reference list entry (if section exists)
[team agents only — if plugin maintains team-structure docs]
- $PLUGIN/docs/team-structure.md: <diagram node and edges> (if file exists)
Documentation to update:
- $PLUGIN/docs/agent_info.md: remove table row (if file exists)
[team agents only]
- $PLUGIN/agents/orchestrator.md: Tier guidance bullet (if listed)
- Other agent files in $PLUGIN/agents/ referencing <name>
Proceed? (yes to continue)
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 · 198 lines · 74 tokens per session scan A e7d855a72f20
agent-remove is a skill published in the GitHub repository bdfinst/agentic-dev-team (280 stars, last pushed 2d ago), licensed MIT. It adds 74 tokens to every session and 1,531 once invoked, about $0.0004 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.