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/thrashr888/agentkernel/snapshotsgit clone --depth 1 https://github.com/thrashr888/agentkernelWhat 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.00000 | $0.00522 |
| Opus 5 | $0.00000 | $0.00261 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
snapshots 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 2d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agentkernel snapshot
Save and restore sandbox state. Snapshots capture the full filesystem of a running or stopped sandbox using docker commit.
Subcommands
| Command | Description |
|---|---|
snapshot take <SANDBOX> [--name NAME] |
Take a snapshot of a sandbox |
snapshot list |
List all snapshots |
snapshot delete <NAME> |
Delete a snapshot (removes image + metadata) |
snapshot restore <NAME> [--as NAME] [-B BACKEND] |
Restore a sandbox from a snapshot |
Examples
Take a snapshot
# Auto-generated name (sandbox-YYYYMMDD)
agentkernel snapshot take my-sandbox
# Custom name
agentkernel snapshot take my-sandbox --name before-upgrade
List snapshots
$ agentkernel snapshot list
NAME SANDBOX BACKEND CREATED
before-upgrade my-sandbox docker 2026-02-01T12:00:00+00:00
daily-backup dev-env docker 2026-02-01T18:00:00+00:00
Restore a snapshot
# Restore with default name (original-restored)
agentkernel snapshot restore before-upgrade
# Restore with a custom name
agentkernel snapshot restore before-upgrade --as my-sandbox-v2
# Restore with a specific backend
agentkernel snapshot restore before-upgrade --as restored -B docker
Delete a snapshot
agentkernel snapshot delete before-upgrade
How It Works
snapshot takerunsdocker commiton the sandbox container, saving the filesystem as a tagged Docker image (agentkernel-snap:<name>)- Metadata (sandbox name, backend, resources, base image) is saved to
~/.local/share/agentkernel/snapshots/<name>.json snapshot restorecreates a new sandbox using the committed image and the original resource settings
Storage
- Snapshot metadata:
~/.local/share/agentkernel/snapshots/*.json - Snapshot images: Docker images tagged as
agentkernel-snap:<name> - Use
images list --allto see snapshot images and their disk usage
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.
- 2d ago First seen · 71 lines · 0 tokens per session scan A 36e718245d93
snapshots is a command published in the GitHub repository thrashr888/agentkernel (58 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 522 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
diagnose
Run sivtr doctor to check the environment, then investigate any failing checks.
test-changed
Run the full quality gate on only the files changed since branching from main.
test_mcp
Test all rust-docs-testing tools found in @rust-docs-mcp/src/service.rs.
update_mcp_tools_list
Read the rust-docs-mcp/src/service.rs module and ensure that the README.md and the rust-docs-mcp/install.sh files have up to date lists of the tools available in the MCP.
review
You are an expert code reviewer. Your job is to review code changes and provide actionable feedback.
speckit.git.feature
Create a feature branch with sequential or timestamp numbering.