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 agentmods add commands/fighter90/career-ops-ui/sdd-statusgit clone --depth 1 https://github.com/Fighter90/career-ops-uiWrote 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/fighter90/career-ops-ui/sdd-status)<a href="https://agentmods.dev/commands/fighter90/career-ops-ui/sdd-status"><img src="https://agentmods.dev/badge/commands/fighter90/career-ops-ui/sdd-status.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 | $0.00024 | $0.00186 |
| Opus 5 | $0.00012 | $0.00093 |
| Sonnet 5 | $0.00005 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
sdd-status 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 4d 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
Run a fast triage of the GSD pipeline state for this repo:
- Read
.planning/ROADMAP.md(if it exists) and list each phase with its status. - List directories under
.planning/phases/and report which one hasSTATE.json: active. - Show the latest entries in
.planning/CHANGELOG.mdif present. - Cross-check
docs/ROADMAP.md(the public roadmap) against.planning/ROADMAP.md— flag drift.
Output:
## GSD state — <today>
- Active phase: <name>
- Pending phases: <list>
- Public roadmap drift: <none | description>
Use Read + Glob only — don't write anything. Under 200 words.
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.
- 4d ago First seen · 22 lines · 24 tokens per session scan A 2d613c69b551
sdd-status is a command published in the GitHub repository Fighter90/career-ops-ui (60 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 186 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-08-30.
Other commands, from other repositories
triage
Triage a GitHub issue and present findings on validity, code locations, and optionally create a failing test or resolution plan.
burn-rate
Compute the recent 7-day spend trend (burn rate) from daily sessions and per-session cost.
cost-today
Quick total cost plus a per-model one-liner from the dashboard pricing engine.
inventory
One-screen inventory of skills, agents, commands, MCP servers, and hooks counts.
top-spenders
List the top N most expensive Claude Code sessions by inline cost.
budget
Show current Claude Code spend versus a budget number.