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/codebloodedai/claude-code-ops-commandsWrote 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/codebloodedai/claude-code-ops-commands/status)<a href="https://agentmods.dev/commands/codebloodedai/claude-code-ops-commands/status"><img src="https://agentmods.dev/badge/commands/codebloodedai/claude-code-ops-commands/status/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/codebloodedai/claude-code-ops-commands/status"><img src="https://agentmods.dev/badge/commands/codebloodedai/claude-code-ops-commands/status.svg" alt="Reviewed on agentmods" width="80" 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.00222 |
| Opus 5.5 | $0.00008 | $0.00089 |
| Sonnet 5.5 | $0.00004 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
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 2mo 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
Give me a fast cross-project status check. Do the following:
- Read
~/CLAUDE.md"Leadership Priorities" section and list each priority with its owner + % complete. - For each priority that's owned by You, check if the corresponding vault note in
~/vault/projects/has been updated in the last 7 days. Flag stale ones. - Run
cd ~/Code/<repo> && git status -son every repo listed in~/CLAUDE.md"Project Repos" table. Report any with uncommitted changes. - Run
cd ~/Code/<repo> && git log --oneline origin/main..HEAD 2>/dev/null | head -3on the same repos. Report any with unpushed commits. - Output a single summary table: Priority | Owner | % | Vault freshness | Git state.
This is a read-only recon. Do not modify anything.
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.
- 2mo ago First seen · 15 lines · 20 tokens per session scan A c6a0e5a0c893
status is a command published in the GitHub repository codebloodedai/claude-code-ops-commands (2 stars, last pushed 6mo ago), licensed MIT. It adds 20 tokens to every session and 222 once invoked, about $0.0001 per session on Opus 5.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-31.
Other commands, from other repositories
revisit
Intake recorded each item below as blocked: something had to happen first. Work lands in parallel, so a blocker can be resolved, superseded or made irrelevant while its issue is still open, and an item can stay blocked long after it could move. Judge, for each item, whether it still looks blocked now. You don't…
create-issue
Create a GitHub issue with proper template discovery and population.
afcl
Close feature [agent] [--adopt] - merges branch, cleans up, optionally adopts from losers (shortcut for feature-close).
mach12:issue-implement
Implement a specific stage of an issue's implementation plan.
next
Suggest the most likely next workflow action based on current context.
aft
Transfer feature from its current agent to a different agent — preserves commits and in-flight work (shortcut for feature-transfer).