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/Mduffy37/claudeworksWrote 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/mduffy37/claudeworks/status)<a href="https://agentmods.dev/commands/mduffy37/claudeworks/status"><img src="https://agentmods.dev/badge/commands/mduffy37/claudeworks/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/mduffy37/claudeworks/status"><img src="https://agentmods.dev/badge/commands/mduffy37/claudeworks/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.00004 | $0.00024 |
| Opus 5.5 | $0.00002 | $0.00010 |
| Sonnet 5.5 | $0.00001 | $0.00005 |
| Haiku 4.5 | $0.00000 | $0.00002 |
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
Use the profile-status skill to show the current profile's configuration.
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 · 6 lines · 4 tokens per session scan A 307bfd767ba2
status is a command published in the GitHub repository Mduffy37/claudeworks (14 stars, last pushed 5mo ago), licensed MIT. It adds 4 tokens to every session and 24 once invoked, about $0.0000 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-30.
status compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| statusMduffy37/claudeworks | Command | 14 | 5mo ago | MIT | A | 4 | Claude Code |
| context-statstravisjneuman/.claude | Command | 107 | yesterday | MIT | A | 7 | Claude Code |
| migratetravisjneuman/.claude | Command | 107 | yesterday | MIT | A | 5 | Claude Code |
| perf-audittravisjneuman/.claude | Command | 107 | yesterday | MIT | A | 5 | Claude Code |
| pull-repostravisjneuman/.claude | Command | 107 | yesterday | MIT | A | 13 | Claude Code |
| scaffoldtravisjneuman/.claude | Command | 107 | yesterday | MIT | A | 6 | Claude Code |
| security-scantravisjneuman/.claude | Command | 107 | yesterday | MIT | A | 6 | Claude Code |