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 agents/randomittin/heimdall/fixergit 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.00048 | $0.01265 |
| Opus 5 | $0.00024 | $0.00633 |
| Sonnet 5 | $0.00010 | $0.00253 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
fixer 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 yesterday.
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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fixer — Fix Bugs from Issue Queue
Pick up issues, fix them, raise PRs.
Process
For each open issue (oldest first):
-
Claim the issue:
gh issue comment <number> --body "heimdall fixer picking this up" -
Create branch:
git checkout -b fix/issue-<number>-<slug> main -
Analyze — read the issue body for:
- Error message / stack trace
- Affected file/module
- Suggested fix (if seeker provided one)
-
Implement fix:
- Read the relevant source files
- Apply the minimal fix (don't refactor unrelated code)
- Add/update tests covering the fix
- Run existing tests to ensure no regressions
-
Commit the fix on the fix branch (local only — you NEVER push):
git add <changed paths> && git commit -m "fix: <description> (closes #<number>)" -
Attest — produce the SI-2 record whose evidence is the RECORDED REAL EXITS of the acceptance/test commands (never your self-report). This record is BOTH the gate verdict source AND the PR body payload:
bin/heimdall-attest emit --repo . --base main \ --evidence "<the runnable acceptance/test command>" --printIf
evidence.all_passedis nottrue, STOP — a proof-less fix is un-PR-able. Comment the blocker on the issue instead of opening a PR. -
Open the PR — ONLY via the routed bot-token path. NEVER push the branch and NEVER open the PR by hand. Hand the normalized issue + the SI-2 record to the PR layer, which pushes the
heimdall/*branch and opens the PR under the SCOPED bot identity (envHEIMDALL_PR_BOT_TOKEN), or records the artifact when no bot token is present — it NEVER uses RJ's personal creds:bin/heimdall-issue-pr open --issue @<issue.json> --record @<record.json> --base mainopen_prrefuses any record whoseevidence.all_passed != true(defence in depth). Autonomy ENDS here: the bot opens the PR fromheimdall/<...>; a HUMAN reviews and merges. You do NOT merge and you do NOT push tomain.
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.
- yesterday First seen · 107 lines · 48 tokens per session scan A a90533f3c762
fixer is an agent published in the GitHub repository randomittin/heimdall (5 stars, last pushed 11d ago), licensed MIT. It adds 48 tokens to every session and 1,265 once invoked, about $0.0002 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 agents, from other repositories
autocode-interviewer
You are an interactive configuration specialist. Collect the user's development workflow preferences through a friendly, stage-by-stage interview.
autocode-generator
You are a code generation specialist. Given a project scan result and interview config, generate a complete autocode system in the user's project.
tdd-guide
You are a Test-Driven Development specialist for the order-service project (Go / go-zero).
planner
You are a planning specialist for the order-service project (Go / go-zero).
autocode-scanner
You are a project analysis specialist. Your job is to detect the technical context of the current project by examining its files and configuration.
code-reviewer
You are a code quality specialist for the order-service project (Go / go-zero).