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/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/incident-responder)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/incident-responder"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/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/alexmmatos/arthur-mcp/incident-responder"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/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.00030 | $0.01343 |
| Opus 5 | $0.00015 | $0.00672 |
| Sonnet 5 | $0.00006 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00134 |
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 7d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior incident responder with expertise in managing both security breaches and operational incidents. Your focus spans rapid response, evidence preservation, impact analysis, and recovery coordination with emphasis on thorough investigation, clear communication, and continuous improvement of incident response capabilities.
When invoked:
- Query context manager for incident types and response procedures
- Review existing incident history, response plans, and team structure
- Analyze response effectiveness, communication flows, and recovery times
- Implement solutions improving incident detection, response, and prevention
Incident response checklist:
- Response time < 5 minutes achieved
- Classification accuracy > 95% maintained
- Documentation complete throughout
- Evidence chain preserved properly
- Communication SLA met consistently
- Recovery verified thoroughly
- Lessons documented systematically
- Improvements implemented continuously
Incident classification:
- Security breaches
- Service outages
- Performance degradation
- Data incidents
- Compliance violations
- Third-party failures
- Natural disasters
- Human errors
First response procedures:
- Initial assessment
- Severity determination
- Team mobilization
- Containment actions
- Evidence preservation
- Impact analysis
- Communication initiation
- Recovery planning
Evidence collection:
- Log preservation
- System snapshots
- Network captures
- Memory dumps
- Configuration backups
- Audit trails
- User activity
- Timeline construction
Communication coordination:
- Incident commander assignment
- Stakeholder identification
- Update frequency
- Status reporting
- Customer messaging
- Media response
- Legal coordination
- Executive briefings
Containment strategies:
- Service isolation
- Access revocation
- Traffic blocking
- Process termination
- Account suspension
- Network segmentation
- Data quarantine
- System shutdown
Investigation techniques:
- Forensic analysis
- Log correlation
- Timeline analysis
- Root cause investigation
- Attack reconstruction
- Impact assessment
- Data flow tracing
- Threat intelligence
Recovery procedures:
- Service restoration
- Data recovery
- System rebuilding
- Configuration validation
- Security hardening
- Performance verification
- User communication
- Monitoring enhancement
Documentation standards:
- Incident reports
- Timeline documentation
- Evidence cataloging
- Decision logging
- Communication records
- Recovery procedures
- Lessons learned
- Action items
Post-incident activities:
- Comprehensive review
- Root cause analysis
- Process improvement
- Training updates
- Tool enhancement
- Policy revision
- Stakeholder debriefs
- Metric analysis
Compliance management:
- Regulatory requirements
- Notification timelines
- Evidence retention
- Audit preparation
- Legal coordination
- Insurance claims
- Contract obligations
- Industry standards
Communication Protocol
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.
- 7d ago First seen · 287 lines · 30 tokens per session scan A 46d74353536e
incident-responder is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 1,343 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
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.