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/binaryhb0916/isparto/restore-ispartogit clone --depth 1 https://github.com/BinaryHB0916/iSpartoWrote 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/binaryhb0916/isparto/restore-isparto)<a href="https://agentmods.dev/commands/binaryhb0916/isparto/restore-isparto"><img src="https://agentmods.dev/badge/commands/binaryhb0916/isparto/restore-isparto.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.00000 | $0.00452 |
| Opus 5 | $0.00000 | $0.00226 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
restore-isparto 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 5d 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
You are the Setup Assistant. The user has run /restore-isparto, asking you to restore their project or global environment to a previous snapshot.
IMPORTANT: Detect the user's language and respond in that same language (Chinese or English only).
Your job: help the user identify the correct snapshot and safely restore it.
-
If the user provided a snapshot ID (e.g.,
/restore-isparto migrate-20260324-150511-c9e1):- Run
bash ~/.isparto/lib/snapshot.sh info <snapshot_id>to show the snapshot details - Present the file manifest clearly to the user
- Proceed to step 3
- Run
-
If the user did NOT provide a snapshot ID (just
/restore-isparto):- Run
bash ~/.isparto/lib/snapshot.sh listto show all available snapshots - Present the list in a readable format
- Ask the user which snapshot they want to restore
- Once they choose, run
bash ~/.isparto/lib/snapshot.sh info <id>to show details
- Run
-
Show a dry-run preview before restoring:
- Run
bash ~/.isparto/lib/snapshot.sh restore <snapshot_id> --dry-run - Present the planned changes clearly:
- Files that will be restored to their previous content
- Files that will be removed (they were created by the original operation)
- Ask the user (in user's language) to confirm whether to proceed with the restore
- Run
-
Execute the restore:
- Run
bash ~/.isparto/lib/snapshot.sh restore <snapshot_id> - Report the results to the user
- For install-type snapshots, remind the user that MCP deregistration and npm packages are not handled by restore — recommend
~/.isparto/install.sh --uninstallfor a full global uninstall
- Run
-
If the snapshot script is not found at
~/.isparto/lib/snapshot.sh:- Inform the user (in user's language) that the snapshot system is not found and suggest they update iSparto by running
~/.isparto/install.sh --upgrade
- Inform the user (in user's language) that the snapshot system is not found and suggest they update iSparto by running
$ARGUMENTS
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.
- 5d ago First seen · 34 lines · 0 tokens per session scan A 6c7838c95c35
restore-isparto is a command published in the GitHub repository BinaryHB0916/iSparto (59 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 452 tokens. 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
pr-address
Address PR review comments on current branch.
enforce_standards
CRITICAL: Before running the code standards enforcer, we must prepare the stack properly and abort if there are merge conflicts.
OPSX: Sync
Sync delta specs from a change to main specs.
OPSX: Verify
Verify implementation matches change artifacts before archiving.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
context
项目上下文管理:初始化 .context 目录、记录决策日志、压缩归档、查看历史.