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/level)<a href="https://agentmods.dev/commands/randomittin/heimdall/level"><img src="https://agentmods.dev/badge/commands/randomittin/heimdall/level/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/level"><img src="https://agentmods.dev/badge/commands/randomittin/heimdall/level.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.00044 | $0.00503 |
| Opus 5.5 | $0.00018 | $0.00201 |
| Sonnet 5.5 | $0.00009 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
level 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 1mo 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
Set Autonomy (deprecated alias of /hmd:autonomy)
/hmd:level was renamed to /hmd:autonomy. This alias still works for one release so muscle memory doesn't break; it will be removed a couple of releases later.
Instructions:
-
First, print exactly this one-line notice:
'/hmd:level' is now '/hmd:autonomy' — same behavior. Please switch. -
Then behave identically to
/hmd:autonomy $ARGUMENTS. Parse$ARGUMENTS:- If empty or missing: Show current setting from
heimdall-state get '.project.autonomy_level'and the descriptions below. Done. - If
+: Read current setting, increment by 1 (wrap 3→1). Use the result as the new setting. - If
-: Read current setting, decrement by 1 (wrap 1→3). Use the result as the new setting. - If 1, 2, or 3: Use directly as the new setting.
- If anything else: Show valid options and ask the user to choose.
- If empty or missing: Show current setting from
-
Update the state file (the on-disk key stays
.project.autonomy_level— do not rename it):
heimdall-state set '.project.autonomy_level' '<new_level>'
- Confirm with a compact status line:
◀ 1 Guided/◀ 2 Checkpoint ▶/3 Full Auto ▶- Show the active setting highlighted, with arrows indicating cycle direction
Valid settings:
- 1 (Guided): Asks before every action.
- 2 (Checkpoint): Runs on its own, pauses at major milestones.
- 3 (Full Auto): Runs until complete; only stops if blocked.
Going forward, use /hmd:autonomy (and /hmd:autonomy + / - to cycle).
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.
- 1mo ago First seen · 39 lines · 44 tokens per session scan A 08ba904fa2ed
level is a command published in the GitHub repository randomittin/heimdall (5 stars, last pushed 4d ago), licensed MIT. It adds 44 tokens to every session and 503 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
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.
atomic-plan
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.
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…
documentation
Bootstrap and maintain project documentation surfaces. Two modes: bootstrap (discover doc files, index them in CLAUDE.md) and authoring (scan for unindexed docs, match diff against indexed surfaces, walk stale/incomplete/missing items with Yes/Later/Remind/Skip).
watch-ci
Spawn a background Haiku-backed subagent to watch CI for the current branch (or specified target). Provider-agnostic — the subagent inspects project signals to identify the CI system (GitHub Actions, GitLab CI, CircleCI, etc.) and picks the right CLI. Returns immediately; reports back when CI reaches a terminal state.
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.