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/forsonny/maker-framework/maker-resumegit clone --depth 1 https://github.com/forsonny/maker-frameworkWrote 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/forsonny/maker-framework/maker-resume)<a href="https://agentmods.dev/commands/forsonny/maker-framework/maker-resume"><img src="https://agentmods.dev/badge/commands/forsonny/maker-framework/maker-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.00007 | $0.00408 |
| Opus 5 | $0.00003 | $0.00204 |
| Sonnet 5 | $0.00001 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
maker-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.
What it actually says
MAKER Resume Command
Resume pipeline execution from the last checkpoint or specified checkpoint.
Process
- If $ARGUMENTS provided, load that specific checkpoint
- Otherwise, find most recent checkpoint in
.maker-checkpoints/metadata/ - Validate checkpoint state is consistent with file system
- Resume execution from that point
- Continue with normal MAKER pipeline flow
Checkpoint Discovery
# List available checkpoints
ls -la .maker-checkpoints/metadata/*.json
Resume Flow
==========================================
MAKER RESUME
==========================================
[CHECKPOINT FOUND]
Checkpoint ID: {id}
Created: {timestamp}
Step: {N} of {Total}
Task ID: {task_id}
------------------------------------------
VALIDATION
------------------------------------------
Files Match: {yes/no}
State Valid: {yes/no}
------------------------------------------
RESUMING
------------------------------------------
Resuming from step {N}: {step_name}
[MAKER] Executing step {N}/{Total}...
...
If No Checkpoints Found
==========================================
MAKER RESUME
==========================================
No checkpoints found.
Possible reasons:
- No MAKER pipeline has been run in this directory
- Checkpoints were cleaned up after completion
- Pipeline failed before first checkpoint
Use /maker-framework:maker <task> to start a new pipeline.
==========================================
If Checkpoint Invalid
==========================================
MAKER RESUME
==========================================
[CHECKPOINT INVALID]
Checkpoint ID: {id}
Error: {description of mismatch}
The file system state does not match the checkpoint.
Options:
1. Restore checkpoint: Use maker-checkpoint-manager RESTORE operation
2. Start fresh: Use /maker-framework:maker <task>
==========================================
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 · 92 lines · 7 tokens per session scan A b6f8bb4820c7
maker-resume is a command published in the GitHub repository forsonny/maker-framework (7 stars, last pushed 8mo ago), licensed MIT. It adds 7 tokens to every session and 408 once invoked, about $0.0000 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.