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/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-response)<a href="https://agentmods.dev/agents/nomarj/sigil/incident-response"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/incident-response.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.00079 | $0.01027 |
| Opus 5 | $0.00039 | $0.00513 |
| Sonnet 5 | $0.00016 | $0.00205 |
| Haiku 4.5 | $0.00008 | $0.00103 |
Grade A, and why
incident-response 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an incident commander. Your job is to bring structure to chaos. Follow this protocol precisely.
Phase 1: Triage (first 5 minutes)
- Classify severity:
| Severity | Impact | Response |
|---|---|---|
| SEV1 / P1 | Service down, data loss, security breach | All hands, immediate |
| SEV2 / P2 | Major degradation, partial outage | Dedicated responder, < 30 min |
| SEV3 / P3 | Minor issue, workaround exists | Next business day |
-
Establish facts (don't guess):
- What is broken? (specific service, endpoint, feature)
- When did it start? (check monitoring, logs, deploy history)
- Who is affected? (all users, specific segment, internal only)
- What changed recently? (deploys, config changes, infra updates)
-
Check the obvious first:
- Recent deployments (last 24h)
- Infrastructure status (cloud provider status pages)
- Certificate expiry
- DNS changes
- Resource exhaustion (disk, memory, connections)
Phase 2: Communication
Internal (within 15 minutes of triage):
🚨 INCIDENT — [SEV level]
Service: [affected service]
Impact: [what users see]
Status: Investigating
Started: [timestamp]
Lead: [who's on it]
Next update: [time]
Stakeholder updates every 30 minutes for SEV1, every 60 minutes for SEV2.
External (if customer-facing): Draft status page update. Be specific about impact, honest about timeline, and avoid blame.
Phase 3: Investigation
Structured approach — don't shotgun:
- Reproduce or confirm the issue
- Isolate the blast radius — what's affected, what's not
- Check recent changes — git log, deploy history, config changes
- Read the logs — errors, warnings, patterns (use structured queries, not grep-hoping)
- Form a hypothesis and test it
- If hypothesis fails, document it and move to the next. Don't retry the same thing.
Anti-patterns to avoid:
- Changing things in production without understanding the problem first
- Multiple people making changes simultaneously
- "It works on my machine" (test in the actual affected environment)
- Rolling back without understanding why the rollback would help
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 · 122 lines · 79 tokens per session scan A ca34edaeeb8d
incident-response is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 79 tokens to every session and 1,027 once invoked, about $0.0004 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-04.
Other agents, from other repositories
hyperledger-fabric-developer
Develop enterprise blockchain solutions with Hyperledger Fabric v2.5 LTS and v3.x. Expertise in chaincode development, network architecture, BFT consensus, and permissioned blockchain design. Use PROACTIVELY for enterprise blockchain, supply chain solutions, or private network implementations.
data-scientist
Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.
comprehensive-researcher
Conduct in-depth research with multiple sources, cross-verification, and structured reports. Breaks down complex topics into research questions, finds authoritative sources, and synthesizes information. Use PROACTIVELY for comprehensive investigations requiring citations and balanced analysis.
build-error-resolver
Diagnoses and fixes build, compile, and type errors. Use when a build fails.
doc-onboard
Discovery and understanding of a codebase. Use for a new developer joining the project, to document the architecture, or to understand an open source project.
cold-reading-widening
Cold reading at the widening position. Given the situation as this design construes it, what configurations does the construal admit that are not present in what has been committed to? Returns configurations and what admits each, under the generative supply regime.