restore-isparto

restore-isparto is a command for coding agents from BinaryHB0916/iSparto. It costs 0 tokens per session (452 once invoked), scanned A, original, MIT.

A setup command for restoring a project or global environment from an earlier snapshot. A snapshot is a saved record of files and their contents at a particular point in time.

In plain words
What is it for?
Use it to list available snapshots, inspect a snapshot's file list, preview a restoration, and restore the selected snapshot.
Why use it?
It helps identify the right saved state and preview which files would be restored or removed before making the change.

Command

Install

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.

agentmods
npx agentmods add commands/binaryhb0916/isparto/restore-isparto
Clone the repo
git clone --depth 1 https://github.com/BinaryHB0916/iSparto

Wrote 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.

agentmods badge for restore-isparto

README.md
[![agentmods](https://agentmods.dev/badge/commands/binaryhb0916/isparto/restore-isparto.svg)](https://agentmods.dev/commands/binaryhb0916/isparto/restore-isparto)
Your own site
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 452 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 5d ago against content hash 6c7838c95c35, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

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.

commands/restore-isparto.md · 34 lines

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.

  1. 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
  2. If the user did NOT provide a snapshot ID (just /restore-isparto):

    • Run bash ~/.isparto/lib/snapshot.sh list to 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
  3. 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
  4. 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 --uninstall for a full global uninstall
  5. 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

$ARGUMENTS

Changes

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.

  1. 5d ago First seen · 34 lines · 0 tokens per session scan A 6c7838c95c35

Subscribe to this mod's changes

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.