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/status)<a href="https://agentmods.dev/commands/randomittin/heimdall/status"><img src="https://agentmods.dev/badge/commands/randomittin/heimdall/status/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/status"><img src="https://agentmods.dev/badge/commands/randomittin/heimdall/status.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.00019 | $0.00321 |
| Opus 5.5 | $0.00008 | $0.00128 |
| Sonnet 5.5 | $0.00004 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
status 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
Heimdall Status
Show the current Heimdall project state.
Instructions:
-
Check if
heimdall-state.jsonexists. If not, runheimdall-state initfirst. -
Run
heimdall-state statusto get the formatted summary. -
Additionally, read the full state file and present a rich status view:
═══════════════════════════════════════
Heimdall status
═══════════════════════════════════════
Project: <name or (unnamed)>
Phase: <idle|planning|implementing|reviewing|complete>
Level: <1|2|3> (<Guided|Checkpoint|Full Auto>)
Quality Gates:
Tests: <passing|failing>
Lint: <clean|dirty>
Reflection: <done|pending>
Dirty: <yes|no>
Active Agents: <count>
Sub-projects: <complete>/<total>
Conflicts: <count> (<unresolved> unresolved)
Maintainer: <enabled|disabled>
═══════════════════════════════════════
-
If there are active sub-projects, list them with their status.
-
If there are unresolved conflicts, mention them briefly.
-
If maintainer mode is enabled, show pending fixes and release queue status.
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 · 47 lines · 19 tokens per session scan A c557bd030932
status is a command published in the GitHub repository randomittin/heimdall (5 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 321 once invoked, about $0.0001 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.