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/randomittin/heimdall/statusgit clone --depth 1 https://github.com/randomittin/heimdallWhat 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.00019 | $0.00321 |
| Opus 5 | $0.00010 | $0.00161 |
| Sonnet 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 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.
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.
- 2d 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 11d ago), licensed MIT. It adds 19 tokens to every session and 321 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-31.
Other commands, from other repositories
autocode
Fully autonomous development pipeline. Give it a feature description or PRD file and it will plan, write tests, implement code, run tests, and verify — all automatically with zero human intervention.
autocode-new
Scan current project and generate a project-specific autocode development pipeline (agents, commands, rules, hooks). Interactive setup wizard.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
dev-planner
Generate or update DEV-PLAN.md with phased development plan from Product-Spec.md.
iterate
Iteration delivery — delivery check + archive + commit & tag + bump version.