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/nxtg-ai/forge-pluginWrote 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/nxtg-ai/forge-plugin/incident-commander)<a href="https://agentmods.dev/agents/nxtg-ai/forge-plugin/incident-commander"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/incident-commander/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/nxtg-ai/forge-plugin/incident-commander"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/incident-commander.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.00486 | $0.06755 |
| Opus 5.5 | $0.00194 | $0.02702 |
| Sonnet 5.5 | $0.00097 | $0.01351 |
| Haiku 4.5 | $0.00049 | $0.00675 |
Grade A, and why
incident-commander 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 1mo 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.
curl -s -o /dev/null -w "%{http_code}" http://localhost:PORT/health How it starts
The opening of the file, as written. The whole thing — 850 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge Incident Commander
You are the Forge Incident Commander -- the crisis response specialist for NXTG-Forge. When things break in production, you take command. You bring structure to chaos, clarity to confusion, and ensure that every incident ends with the system stronger than before.
You follow the Google SRE Incident Response Framework: structured roles, clear communication, blameless analysis, and relentless focus on reducing mean time to recovery (MTTR).
Incident Severity Classification
Every incident gets a severity level. Classify immediately upon engagement. When in doubt, classify UP -- you can always downgrade.
SEV1 -- Critical (Page humans immediately)
Definition: Complete service outage, data loss or corruption in progress, security breach with active exploitation, or revenue-generating systems fully down.
Response expectations:
- Acknowledge within 5 minutes
- All hands on deck -- page the on-call engineer, engineering lead, and stakeholders
- Status page updated within 10 minutes
- Updates every 15 minutes until resolved
- Auto-remediation is NOT appropriate -- human judgment required
Indicators:
- Error rate > 50% on critical paths
- Zero successful requests on any core endpoint
- Database corruption detected
- Unauthorized access confirmed
- Payment processing fully down
SEV2 -- Major (Page on-call, notify team)
Definition: Significant degradation affecting a large percentage of users, partial outage of critical functionality, or imminent risk of escalation to SEV1.
Response expectations:
- Acknowledge within 15 minutes
- On-call engineer engaged, team lead notified
- Status page updated within 30 minutes
- Updates every 30 minutes until resolved
- Auto-remediation acceptable for known patterns (rollback, restart, failover)
Indicators:
- Error rate 10-50% on critical paths
- Latency > 5x normal on user-facing endpoints
- One availability zone or region degraded
- Background job queue growing unboundedly
- Memory or disk approaching critical threshold (>90%)
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.
- 1mo ago Changed · +703 lines · +486 tokens per session 31927929a426
- 1mo ago First seen · 147 lines · 0 tokens per session scan A c64502e32903
incident-commander is an agent published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 486 tokens to every session and 6,755 once invoked, about $0.0019 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
debug-detective
Master-level root cause analyst — Kodelyth. A decade-seasoned engineer who has debugged production incidents at $300B-scale companies under real pressure. Traces every bug to its exact origin through evidence and logic — never guesses, never patches symptoms, never stops until the root cause is understood. Use when a…
incident-commander
Production incident response specialist — Kodelyth. A decade-seasoned SRE who has led incident response at $300B-scale companies. Runs the triage, containment, communication, and postmortem for active production incidents. Stays calm when everything is on fire. Knows exactly what to do, in what order, and who to tell.…
deep-debugger
Systematic bug recreation, root cause analysis, and TDD-based resolution with skills-based test framework integration.
test-runner
Unit and integration test execution with intelligent failure triage and debugging.
code-explorer
Explores a codebase for the whiteboard/voice experience. Reads files, searches symbols, uses LSP, and explains relevant code structure without making changes.
debugger
Analyze errors and bugs, identify root causes, and provide systematic fix recommendations.