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.
git clone --depth 1 https://github.com/randomittin/heimdallWrote 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/randomittin/heimdall/save)<a href="https://agentmods.dev/commands/randomittin/heimdall/save"><img src="https://agentmods.dev/badge/commands/randomittin/heimdall/save/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/randomittin/heimdall/save"><img src="https://agentmods.dev/badge/commands/randomittin/heimdall/save.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.01726 |
| Opus 5.5 | $0.00022 | $0.00690 |
| Sonnet 5.5 | $0.00011 | $0.00345 |
| Haiku 4.5 | $0.00006 | $0.00173 |
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 8d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Save — Checkpoint Current State
Create or update ALL .planning/ state files so the next heimdall run resumes exactly where you left off.
What to save
Read the current state of the project and write/update these files:
1. .planning/STATE.md
Update with:
- Current phase: what phase are we in (planning, executing wave N, verifying, idle)
- What's done: list completed tasks/features with commit hashes
- What's in progress: currently active work
- What's next: queued tasks not yet started
- Blockers: anything preventing progress
- Decisions made: key architectural/design decisions from this session
- Key files changed: list of files modified in this session
2. .planning/CHECKPOINT.md (the handoff note — most important file)
Write a concise handoff note that another Claude session can read and immediately continue:
# Checkpoint — [timestamp]
## TL;DR
[One sentence: what was the task, how far did we get]
## Completed
- [x] Task 1 (commit abc1234)
- [x] Task 2 (commit def5678)
## In Progress
- [ ] Task 3 — started, file X partially edited
## Not Started
- [ ] Task 4
- [ ] Task 5
## Resume Instructions
[Exact next step: "Finish Task 3 (file X), run only src/auth/login.test.ts once, then proceed to Task 4; full sweep still pending"]
## Key Context
- [Decision 1: chose X over Y because Z]
- [File A imports from File B — don't break this]
- [User wants: specific preference]
## Tech Stack & Patterns
- [Stack: React 18 + TypeScript + Vite, etc.]
- [Pattern: services use singleton pattern, components use compound pattern]
- [Constraint: must support Node 18+, no ESM-only deps]
## Project Settings
- Parallelism: [max 10 / max 5 / sequential — what worked for this project]
- Model routing: [any overrides from defaults, e.g. "sonnet works fine for React components here"]
- Governance: [hierarchical / democratic / emergency last used]
- Test command: [exact command, e.g. "npm test", "pytest tests/", "cargo test"]
- Lint command: [exact command, e.g. "npx eslint src/", "ruff check ."]
- Build command: [exact command, e.g. "npm run build", "cargo build"]
- Deploy command: [if known]
- Directories to avoid: [e.g. "vendor/, generated/, dist/"]
- User preferences: [e.g. "prefers tabs over spaces", "wants detailed commit messages", "hates emojis in code"]
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.
- 8d ago Changed · +3 lines 8a005e282dcf
- 1mo ago First seen · 138 lines · 55 tokens per session scan A 3201f0ce2b46
save is a command published in the GitHub repository randomittin/heimdall (5 stars, last pushed 3d ago), licensed MIT. It adds 55 tokens to every session and 1,726 once invoked, about $0.0002 per session on Opus 5.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-31.
Other commands, from other repositories
report-issue-with-atomic
Open an issue against the atomic-claude repo itself (bugs/feature requests with the installed config, not the user's current project).
report-issue
Open a atomic GitHub issue via gh. Bug report or feature request — auto-detect from user's description.
atomic-help
Route a lost user to the right atomic verb, skill, agent, or binary subcommand. Bare invocation reads git state and recommends one next step. Topic keyword or freeform intent → focused pointer. tour → guided walkthrough of the system. Help router, not duplicated docs.
follow-up
Review and act on pending reminders. Bare invocation shows all reminders as an indexed list; cron-fired invocation (/follow-up due ) surfaces the specific reminder and waits for a response; /follow-up review lists stale project follow-up entries for per-item disposition (extend/close/promote/skip). Transport-aware…
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.