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/reflectgit 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.00018 | $0.00268 |
| Opus 5 | $0.00009 | $0.00134 |
| Sonnet 5 | $0.00004 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
reflect 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
Conflict Reflection Pass
Force a reflection pass over all unresolved conflicts in the conflict log.
Instructions:
- Get unresolved conflicts:
conflict-log unresolved
-
If no unresolved conflicts, report: "No unresolved conflicts. Reflection gate is clear."
-
For each unresolved conflict: a. Read the conflict details (skills involved, what they disagreed on, the resolution chosen) b. Re-evaluate the resolution in the current context:
- Is the original resolution still the best choice?
- Has anything changed that would alter the decision?
- Were there any downstream effects from this decision? c. If the resolution is still sound, explain briefly why and mark it reflected d. If the resolution needs revision:
- Explain what changed
- Propose the new approach
- Update the code if needed
- Log the revised resolution
-
After reviewing all conflicts:
conflict-log reflect-all
- Report summary: "Reflected on conflicts. confirmed, revised. Reflection gate is now clear."
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 · 39 lines · 18 tokens per session scan A 4725bfaae9be
reflect is a command published in the GitHub repository randomittin/heimdall (5 stars, last pushed 11d ago), licensed MIT. It adds 18 tokens to every session and 268 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.