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/incident-respondergit 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.svg" alt="Measured on agentmods" 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 | $0.00039 | $0.00563 |
| Opus 5 | $0.00019 | $0.00282 |
| Sonnet 5 | $0.00008 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00056 |
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 4d 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 What it actually says
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
3. MITIGATE (stop bleeding)
- Rollback if recent deploy caused it:
git revertor redeploy last-known-good - 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
- Deploy fix, verify metrics return to baseline
- Remove any temporary mitigations
5. POSTMORTEM (blameless)
Duration, impact, root cause, timeline, what went well/wrong, action items (preventive fix + detection improvement + runbook update)
Rules
- NEVER guess — verify w/ data before acting
- NEVER make changes that can't be reverted
- Log every action taken w/ timestamp
- Communicate status every 15 min during active incident
Output compression
Level is owned by the caveman plugin, not asserted here. Terse during diagnosis. Full clarity for mitigation commands + postmortem. Paths+commands exact.
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.
- 4d 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 14d ago), licensed MIT. It adds 39 tokens to every session and 563 once invoked, about $0.0002 per session on Opus 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
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.
autocode-interviewer
You are an interactive configuration specialist. Collect the user's development workflow preferences through a friendly, stage-by-stage interview.
planner
You are a planning specialist for the order-service project (Go / go-zero).
tdd-guide
You are a Test-Driven Development 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).