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.
git 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/commands/bdfinst/agentic-dev-team/upgrade)<a href="https://agentmods.dev/commands/bdfinst/agentic-dev-team/upgrade"><img src="https://agentmods.dev/badge/commands/bdfinst/agentic-dev-team/upgrade.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.00020 | $0.01757 |
| Opus 5 | $0.00010 | $0.00879 |
| Sonnet 5 | $0.00004 | $0.00351 |
| Haiku 4.5 | $0.00002 | $0.00176 |
Grade A, and why
upgrade 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrade
Role: worker. This command updates the security-assessment plugin to the latest version and ensures its marketplace is set to auto-update going forward.
You have been invoked with the /upgrade command.
Steps
1. Read current version
claude plugin list
Parse the output to find security-assessment and its current version.
Also read the installed plugin.json directly:
~/.claude/plugins/cache/*/security-assessment/*/.claude-plugin/plugin.json
Report:
Current version: security-assessment v{version} (installed from {marketplace})
2. Check auto-update status and ask the user
First, check the current auto-update status by running the script below and reporting it to the user.
python3 - <<'PY'
import json, os
PLUGIN = "security-assessment"
home = os.path.expanduser("~")
cwd = os.getcwd()
def load(path):
try:
with open(path) as f:
return json.load(f)
except FileNotFoundError:
return None
except json.JSONDecodeError as e:
print(f"unknown ({path} is not valid JSON)")
raise SystemExit(0)
installed = (load(os.path.join(home, ".claude", "plugins", "installed_plugins.json")) or {}).get("plugins", {})
market = next((pid.split("@", 1)[1] for pid in installed if pid.split("@", 1)[0] == PLUGIN and "@" in pid), None)
if not market:
print("unknown (marketplace not found)")
raise SystemExit(0)
candidates = [
os.path.join(cwd, ".claude", "settings.json"),
os.path.join(cwd, ".claude", "settings.local.json"),
os.path.join(home, ".claude", "settings.json"),
]
for path in candidates:
data = load(path)
if data and market in (data.get("extraKnownMarketplaces") or {}):
flag = data["extraKnownMarketplaces"][market].get("autoUpdate")
print("enabled" if flag is True else "disabled")
raise SystemExit(0)
print("disabled")
PY
Then ask the user:
Auto-update for the
{marketplace}marketplace is currently {enabled/disabled}. Would you like to enable auto-update so future releases install automatically? (yes/no)Note: this flag is marketplace-level and affects every plugin published from
{marketplace}— including the companion dev-team plugin if you have it installed.
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 · 237 lines · 20 tokens per session scan A 7f98e78cc9e8
upgrade is a command published in the GitHub repository bdfinst/agentic-dev-team (280 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 1,757 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.