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/jimmc414/cctrace/restore-backupgit clone --depth 1 https://github.com/jimmc414/cctraceWrote 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/jimmc414/cctrace/restore-backup)<a href="https://agentmods.dev/commands/jimmc414/cctrace/restore-backup"><img src="https://agentmods.dev/badge/commands/jimmc414/cctrace/restore-backup.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.1 | $0.00011 | $0.00311 |
| Opus 5 | $0.00005 | $0.00156 |
| Sonnet 5 | $0.00002 | $0.00062 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
restore-backup 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 6d 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
Restore the session state from before the last import. Use this if an import caused problems or you want to undo an import.
Usage
/restore-backup
What This Does
- Shows information about the pre-import snapshot:
- When it was created
- What directory it protects
- Whether there was existing content before import
- Lists session files that will be affected
- Requires typing "RESTORE" to confirm (safety measure)
- Restores the pre-import state:
- If there was existing content: restores it
- If directory was empty: removes imported content
- Deletes the snapshot after successful restore
Important Notes
- DESTRUCTIVE: Any sessions created AFTER the import will be LOST
- ONE SNAPSHOT: Each import overwrites the previous snapshot
- IRREVERSIBLE: Once restored, cannot undo the restore
Examples
Check snapshot status (no restore):
/restore-backup --info
Perform restore (will prompt for confirmation):
/restore-backup
Implementation
Show snapshot info first:
python3 restore_backup.py
If user confirms, perform restore:
python3 restore_backup.py --restore
For the --info flag, just show info without prompting:
python3 restore_backup.py
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.
- 6d ago First seen · 60 lines · 11 tokens per session scan A a490d2099617
restore-backup is a command published in the GitHub repository jimmc414/cctrace (200 stars, last pushed 8mo ago), licensed MIT. It adds 11 tokens to every session and 311 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.