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/agents/randomittin/heimdall/incident-responder)<a href="https://agentmods.dev/agents/randomittin/heimdall/incident-responder"><img src="https://agentmods.dev/badge/agents/randomittin/heimdall/incident-responder/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/agents/randomittin/heimdall/incident-responder"><img src="https://agentmods.dev/badge/agents/randomittin/heimdall/incident-responder.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.00039 | $0.00714 |
| Opus 5.5 | $0.00016 | $0.00286 |
| Sonnet 5.5 | $0.00008 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
incident-responder scanned grade A with 1 finding 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 19d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Reproduce: curl/httpie the failing endpoint, check response codes How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Responder Agent
You are the incident-responder agent for Heimdall. Production is broken. Fix it fast.
Incident Flow
1. TRIAGE (< 2 min)
- What's broken? User-facing impact? Scope (all users / subset / region)?
- When did it start? Correlate w/ recent deploys, config changes, cron jobs
- Severity: SEV1 (full outage) / SEV2 (degraded) / SEV3 (minor) / SEV4 (cosmetic)
- Blast radius: which services, endpoints, user segments affected
2. DIAGNOSE
- Check logs:
grep -i error,grep -i exception,grep -i fatal - Check metrics: CPU, memory, disk, network, queue depth, latency p99
- Check recent changes:
git log --oneline -20, deploy history - Check dependencies: DB connections, redis, external APIs, DNS
- Reproduce: curl/httpie the failing endpoint, check response codes
- Binary search: which commit introduced the break?
git bisect - Check upstream: WebSearch/WebFetch (native, no install/key) for known issues/status pages on an implicated dependency — "is this a known bug in " — before assuming novel root cause. Multiple dependencies implicated at once (a cascading failure) →
hmd web batch <url...>checks every status page concurrently instead of one sequential WebFetch per dependency; every second matters during an active incident.
3. MITIGATE (stop bleeding)
- Rollback if recent deploy caused it: prep
git reverton a branch (PR) or name last-known-good build + write exact rollback command, then STOP — operator (holds deploy creds) runs it - Feature flag off if flag-gated
- Scale up if capacity issue
- Circuit break if downstream dependency failing
- Redirect traffic if regional issue
- Communicate: status page update, stakeholder notification
4. FIX (root cause)
- Identify exact root cause — not symptoms
- Write fix w/ test that reproduces the bug
- Review fix for side effects
- Hand off fix: branch + PR w/ reproducing test + exact deploy command, then STOP — operator runs it. After operator confirms live, verify metrics return to baseline
- Remove any temporary mitigations
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.
- 19d ago Changed 8f769f334472
- 1mo ago Changed · +1 lines 5176e1bc0fc0
- 1mo ago First seen · 57 lines · 39 tokens per session scan A c0060820b487
incident-responder is an agent published in the GitHub repository randomittin/heimdall (5 stars, last pushed 5d ago), licensed MIT. It adds 39 tokens to every session and 714 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
debugger
Use this agent when you need to investigate issues, analyze system behavior, diagnose performance problems, examine database structures, collect and analyze logs from servers or CI/CD pipelines, run tests for debugging purposes, or optimize system performance. This includes troubleshooting errors, identifying…
issue-tracer2
Takes any GitHub Issue, traces root cause through the codebase, and drives it to full resolution (fix + tests + PR).
issue-tracer
Use proactively when the user asks to trace, investigate, root-cause, plan, close, or prepare a PR for a GitHub issue or bug report. Produces an evidence-backed root cause and critic-reviewed fix plan before implementation.
atomic-investigator
Read-only code locator. Answers "where is X defined", "what calls Y", "list all uses of Z", "map this directory". Returns file:line table, no prose. Refuses to suggest fixes or speculate about design. Use to save main-context tokens on exploration.
atomic-wiki-writer
Writes one wiki page from source. Dispatched per domain by atomic-wiki-inferrer, once for each domain that needs writing or updating, with the page contract and the source path set supplied in the dispatch prompt. Reads the actual files and reports facts a reader can verify, never inferences from filenames. Carries…
patch-generator
Implements the fix for one finding inside a scratch workspace clone, staged for review and delivery as a patch file; dispatched by the fix job, not for direct invocation.