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/0xdarkmatter/claude-mods/savegit clone --depth 1 https://github.com/0xDarkMatter/claude-modsWrote 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/0xdarkmatter/claude-mods/save)<a href="https://agentmods.dev/commands/0xdarkmatter/claude-mods/save"><img src="https://agentmods.dev/badge/commands/0xdarkmatter/claude-mods/save.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.00024 | $0.02672 |
| Opus 5 | $0.00012 | $0.01336 |
| Sonnet 5 | $0.00005 | $0.00534 |
| Haiku 4.5 | $0.00002 | $0.00267 |
Grade A, and why
save 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.
How it starts
The opening of the file, as written. The whole thing — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Save - Session State Persistence
Persist your current session state for later restoration with /sync.
Claude Code's native auto-memory remembers learnings for you on this machine, but tasks are still session-scoped and nothing native is portable. /save writes state you control — a git-trackable .claude/session-cache.json (tasks, git/PR context, session ID, handoff notes) you can commit, share with a team, or pick up on another machine.
Arguments
$ARGUMENTS
- No args: Save current state (tasks, plan, git context)
"notes": Save with descriptive notes--archive: Archive current plan toPLAN-<date>.md, then save fresh
What It Saves
| Data | Source | Destination |
|---|---|---|
| Tasks | TaskList API | .claude/session-cache.json |
| Plan content | Conversation context | <plan-path> (see Step 0) |
| Git context | git status/log |
.claude/session-cache.json |
| User notes | Command argument | .claude/session-cache.json |
| Human-readable summary | Generated | .claude/claude-progress.md |
Execution
Step 0: Resolve Plan Path
Determine where the strategic plan file lives:
- Check
.claude/settings.local.jsonfor aplansDirectorykey - If not found, check
.claude/settings.jsonforplansDirectory - If found, plan path =
<plansDirectory>/PLAN.md - If not found, default to
docs/PLAN.md
Store the resolved path for use in all subsequent steps.
Note: plansDirectory is a Claude Code setting (added in v2.1.9) for plan file storage.
Our strategic PLAN.md co-locates with native plans when this is set.
Step 1: Capture Task State
Use TaskList and TaskGet to capture full task data:
1. Call TaskList to get all task IDs and summaries
2. For each task, call TaskGet to retrieve:
- subject (title)
- description (full details)
- status (pending, in_progress, completed)
- blockedBy (dependency IDs)
3. Store as array with index-based dependency mapping
Note: Tasks do not persist across sessions automatically. This is why /save exists.
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 · 371 lines · 24 tokens per session scan A 579759b541f2
save is a command published in the GitHub repository 0xDarkMatter/claude-mods (32 stars, last pushed 11d ago), licensed MIT. It adds 24 tokens to every session and 2,672 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
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.
deps-age
Analyze dependency freshness and maintenance activity.
session-active
Set the persistent, per-session credo mode to active.