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/tommymorgan/claude-plugins/statusgit clone --depth 1 https://github.com/tommymorgan/claude-pluginsWhat 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.00017 | $0.00711 |
| Opus 5 | $0.00009 | $0.00356 |
| Sonnet 5 | $0.00003 | $0.00142 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
tommymorgan: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 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Plan Status
Parse plan file scenarios and report completion status. Shows TODO vs DONE scenarios and overall progress.
Workflow
Step 1: Find Plan File
If a path is provided as argument, use it:
$ARGUMENTS
If no path provided, find the plan file:
- Check current directory for
plans/*.mdordocs/plans/*.md - Check parent directories
- Look for most recent plan file by date in filename (YYYY-MM-DD pattern)
If multiple plans found and ambiguous, list them and ask user to specify.
Step 2: Read and Parse Plan
Read the plan file and extract scenarios from both sections:
User Requirements section:
<!-- TODO -->
Scenario: <description>
Given <context>
When <action>
Then <outcome>
<!-- DONE -->
Scenario: <description>
Given <context>
When <action>
Then <outcome>
Technical Specifications section: Same format as User Requirements.
Step 3: Count Scenarios
Parse the plan and count:
- Total TODO scenarios (in both sections)
- Total DONE scenarios (in both sections)
- User Requirements TODO/DONE
- Technical Specifications TODO/DONE
Extract scenario titles (the "Scenario: " line).
Step 4: Report Status
Report current progress:
## Plan Status: <plan filename>
**Progress**: X/Y scenarios complete (Z% done)
### User Requirements
- ✅ <DONE scenario title>
- ✅ <DONE scenario title>
- ⏳ <TODO scenario title>
### Technical Specifications
- ✅ <DONE scenario title>
- ⏳ <TODO scenario title>
- ⏳ <TODO scenario title>
**Next scenario**: <first TODO scenario title>
If all scenarios DONE:
## Plan Complete! 🎉
All Y scenarios implemented and marked DONE.
User Requirements: X/X complete
Technical Specifications: Y/Y complete
Feature ready for deployment!
If no TODO scenarios remain but work seems incomplete:
## Status Check
All scenarios marked DONE.
Consider:
- Has exploratory testing been run?
- Have all quality gates passed?
- Is documentation up to date?
- Ready to squash commits and finalize?
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 · 138 lines · 17 tokens per session scan A ea3738681463
tommymorgan:status is a command published in the GitHub repository tommymorgan/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 711 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.