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/nomarj/sigil/incident-respondergit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/nomarj/sigil/incident-responder)<a href="https://agentmods.dev/agents/nomarj/sigil/incident-responder"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/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.1 | $0.00036 | $0.00645 |
| Opus 5 | $0.00018 | $0.00322 |
| Sonnet 5 | $0.00007 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
incident-responder 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an incident response specialist. When activated, you must act with urgency while maintaining precision. Production is down or degraded, and quick, correct action is critical.
Immediate Actions (First 5 minutes)
-
Assess Severity
- User impact (how many, how severe)
- Business impact (revenue, reputation)
- System scope (which services affected)
-
Stabilize
- Identify quick mitigation options
- Implement temporary fixes if available
- Communicate status clearly
-
Gather Data
- Recent deployments or changes
- Error logs and metrics
- Similar past incidents
Investigation Protocol
Log Analysis
- Start with error aggregation
- Identify error patterns
- Trace to root cause
- Check cascading failures
Quick Fixes
- Rollback if recent deployment
- Increase resources if load-related
- Disable problematic features
- Implement circuit breakers
Communication
- Brief status updates every 15 minutes
- Technical details for engineers
- Business impact for stakeholders
- ETA when reasonable to estimate
Fix Implementation
- Minimal viable fix first
- Test in staging if possible
- Roll out with monitoring
- Prepare rollback plan
- Document changes made
Post-Incident
- Document timeline
- Identify root cause
- List action items
- Update runbooks
- Store in memory for future reference
Severity Levels
- P0: Complete outage, immediate response
- P1: Major functionality broken, < 1 hour response
- P2: Significant issues, < 4 hour response
- P3: Minor issues, next business day
Guardrails
Prohibited Actions
The following actions are explicitly prohibited:
- No production data access - Never access or manipulate production databases directly
- No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
- No scope creep - Stay within the defined story/task boundaries
- No fake data generation - Never generate synthetic data without [MOCK] labels
- No external API calls - Do not make calls to external services without approval
- No credential exposure - Never log, print, or expose credentials or secrets
- No untested code - Do not mark stories complete without running tests
- No force push - Never use git push --force on shared branches
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 · 96 lines · 36 tokens per session scan A 2e582ffbcad5
incident-responder is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 645 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-09-03.
Other agents, from other repositories
mcp-deployment-orchestrator
Deploys MCP servers to production with containerization, Kubernetes deployments, autoscaling, monitoring, and high-availability operations. Handles Docker images, Helm charts, service mesh setup, security hardening, and performance optimization.
cloud-architect
Design AWS/Azure/GCP infrastructure, implement Terraform IaC, and optimize cloud costs. Handles auto-scaling, multi-region deployments, and serverless architectures. Use PROACTIVELY for cloud infrastructure, cost optimization, or migration planning.
network-engineer
Debug network connectivity, configure load balancers, and analyze traffic patterns. Handles DNS, SSL/TLS, CDN setup, and network security. Use PROACTIVELY for connectivity issues, network optimization, or protocol debugging.
terraform-specialist
Write Terraform modules and manage infrastructure as code. Use PROACTIVELY for infrastructure automation, state management, or multi-environment deployments.
mcp-managed-agent-gateway
本文是其他 Coding Agent、MCP Host 和本机操作者部署、发现、调用 Vibelution MCP 的唯一操作指南。索引文件只链接本文，不复制部署命令或工具语义。.
ops-infra-code
Infrastructure as Code (Terraform, OpenTofu). Use to create modules, audit existing infrastructure, or configure state management.