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/MadeByTokens/claude-code-plugins-madebytokensWrote 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/madebytokens/claude-code-plugins-madebytokens/resume-status)<a href="https://agentmods.dev/commands/madebytokens/claude-code-plugins-madebytokens/resume-status"><img src="https://agentmods.dev/badge/commands/madebytokens/claude-code-plugins-madebytokens/resume-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/madebytokens/claude-code-plugins-madebytokens/resume-status"><img src="https://agentmods.dev/badge/commands/madebytokens/claude-code-plugins-madebytokens/resume-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.00009 | $0.00759 |
| Opus 5 | $0.00005 | $0.00380 |
| Sonnet 5 | $0.00002 | $0.00152 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
resume-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 9d 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.
This is a copy
100% identical to resume-status — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume Status Command
Display the current status of the resume development loop.
Instructions
-
Read
working/state.jsonfrom the current working directory -
If file doesn't exist:
No active resume development loop found. Start one with: /resume-helper:resume-loop "experience.md" -
If file exists, display status based on state:
Active Loop Display
═══════════════════════════════════════════════════
RESUME DEVELOPMENT STATUS
═══════════════════════════════════════════════════
Status: ACTIVE
Phase: [WRITING | FACT_CHECK | REVIEWING | ANALYZING | COACHING]
Iteration: [X] of [maxIterations]
Started: [timestamp]
Experience File: working/inputs/experience.md
Job Description: [working/inputs/job_description.md or "Not provided"]
Last Verdict: [verdict or "N/A"]
Working Directory:
working/
├── inputs/ # Your input files
├── writer/ # Current resume in output.md
├── fact_checker/ # Verification reports
├── interviewer/ # Review feedback
├── analysis/ # Analysis results
└── coach/ # Coach assessment and questions
Commands:
- Continue: The loop will auto-resume
- Cancel: /resume-helper:cancel-resume
═══════════════════════════════════════════════════
Completed Loop Display
═══════════════════════════════════════════════════
RESUME DEVELOPMENT STATUS
═══════════════════════════════════════════════════
Status: COMPLETE
Final Verdict: [READY | MAX_ITERATIONS]
Total Iterations: [X]
Started: [timestamp]
Completed: [timestamp]
Output Files:
- Resume: [output path]
- Interview Prep: working/output/interview_prep.md
- Coach Assessment: working/coach/assessment.md
To start a new loop: /resume-helper:resume-loop "experience.md"
═══════════════════════════════════════════════════
Blocked Loop Display
═══════════════════════════════════════════════════
RESUME DEVELOPMENT STATUS
═══════════════════════════════════════════════════
Status: BLOCKED - Waiting for User Input
Iteration: [X]
The Coach has requested additional information.
See: working/coach/questions.md
Please provide this information, then the loop will continue.
═══════════════════════════════════════════════════
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.
- 9d ago First seen · 117 lines · 9 tokens per session scan A 647fb3b2cb65
resume-status is a command published in the GitHub repository MadeByTokens/claude-code-plugins-madebytokens (2 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 759 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to resume-status, differing in 0 lines, and is treated as a copy.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.