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/ddunnock/claude-plugins/concept.resumegit clone --depth 1 https://github.com/ddunnock/claude-pluginsWrote 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/ddunnock/claude-plugins/concept.resume)<a href="https://agentmods.dev/commands/ddunnock/claude-plugins/concept.resume"><img src="https://agentmods.dev/badge/commands/ddunnock/claude-plugins/concept.resume.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.00015 | $0.00806 |
| Opus 5 | $0.00008 | $0.00403 |
| Sonnet 5 | $0.00003 | $0.00161 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
concept:resume 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/concept:resume
Resume a concept development session after interruption.
Procedure
Step 1: Load State
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/update_state.py --state .concept-dev/state.json show
If no state file exists: "No active session found. Run /concept:init to start a new session."
Step 2: Identify Resume Point
Determine the current phase and gate status:
===================================================================
RESUMING SESSION
===================================================================
Session: [id]
Project: [name]
Last Updated: [timestamp]
Current Phase: [phase name]
Phase Status: [in_progress / completed]
Gate Status: [passed / pending]
===================================================================
Step 3: Load Context
Based on current phase, load the relevant artifacts:
| Phase | Artifacts to Load |
|---|---|
| spitball | (none — session state only) |
| problem | .concept-dev/IDEAS.md |
| blackbox | .concept-dev/IDEAS.md, .concept-dev/PROBLEM-STATEMENT.md |
| drilldown | .concept-dev/BLACKBOX.md (+ prior artifacts) |
| document | All artifacts |
Read each artifact and summarize key points to the user.
Step 4: Present Context Summary
===================================================================
SESSION CONTEXT
===================================================================
[For each loaded artifact, provide a 2-3 sentence summary]
Phase 1 (Spit-Ball):
Themes selected: [list]
Phase 2 (Problem):
Problem: [1-sentence summary]
[if completed]
Phase 3 (Black-Box):
Approach: [name]
Blocks: [list]
[if completed]
Phase 4 (Drill-Down):
Blocks researched: [N] of [N]
Sources: [N] | Gaps: [N]
[if in progress or completed]
-------------------------------------------------------------------
RESUMPTION POINT:
Based on the state, you were in [phase] — [status].
[Specific context about where in the phase you were]
Ready to continue?
[A] Continue from where we left off
[B] Go back to a previous phase
[C] Show full status dashboard (/concept:status)
===================================================================
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 · 121 lines · 15 tokens per session scan A 28ebffda406b
concept:resume is a command published in the GitHub repository ddunnock/claude-plugins (12 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 806 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
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.