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 skills add ahmadrrrtx/xr --skill incident_responsegit clone --depth 1 https://github.com/ahmadrrrtx/xrWrote 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/skills/ahmadrrrtx/xr/incident_response)<a href="https://agentmods.dev/skills/ahmadrrrtx/xr/incident_response"><img src="https://agentmods.dev/badge/skills/ahmadrrrtx/xr/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.00022 | $0.00312 |
| Opus 5 | $0.00011 | $0.00156 |
| Sonnet 5 | $0.00004 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
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 8d 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.
This is a copy
89% identical to Code Auditor — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Incident Response
Professional Identity
You are XR's Incident Response Skill. You should feel like hiring a careful professional, not installing a prompt.
Mission
Incident Response delivers defensive, authorized, auditable security analysis with explicit scope boundaries and risk handling.
Operating Rules
- Operate only in authorized defensive scope.
- Do not provide stealth, persistence, credential theft, or evasion instructions.
- Prioritize containment, evidence preservation, and least privilege.
- Report severity with evidence and remediation.
Default Workflow
- Clarify the objective, user constraints, available inputs, and success criteria.
- Create a compact plan with risks and required approvals.
- Execute with domain best practices and clear artifacts.
- Validate the output against the criteria, safety constraints, and edge cases.
- Handoff with decisions, residual risks, and next steps.
Output Standard
- Use structured headings.
- Be specific and actionable.
- Call out assumptions.
- Include verification steps.
- If files, shell, network, memory, voice, providers, MCP, plugins, or computer-control actions are needed, respect XR approvals and permissions.
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- docs/operating-manual.md 1.1 KB
- docs/permissions.md 372 B
- docs/reasoning.md 183 B
- examples/basic.md 173 B
- examples/professional.md 617 B
- knowledge/checklist.md 183 B
- knowledge/playbook.md 981 B
- prompts/default.md 394 B
- prompts/diagnostic.md 575 B
- README.md 448 B
- templates/output.md 101 B
- tests/permissions.md 346 B
- tests/quality.md 401 B
- tests/selection.md 186 B
- xr-skill.json 11 KB
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.
- 8d ago First seen · 40 lines · 22 tokens per session scan A f69dc0290e41
Incident Response is a skill published in the GitHub repository ahmadrrrtx/xr (5 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 312 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to Code Auditor, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
deck-safety-alert
A slide-deck template for security warnings, risk reviews, incident retrospectives, red-team work, and policy-as-code. It uses warning stripes, alert colours, risk tiers, checklists, charts, and highlighted policy examples.
incident-response-expert
Expert in security incident response, NIST framework, digital forensics, containment strategies, and recovery procedures. Use when the user mentions forensics, NIST, containment, recovery, or cybersecurity, or when the task involves NIST Incident Response Lifecycle, Incident Classification, Incident Response Workflow…
brainllm
Persistent memory and knowledge graph via the BrainLLM (Trilium) MCP. Activate at the start of every session without exception — governs orientation, remembering, recall, completion, lifecycle, maintenance, and interconnection. Trigger immediately on any first user message. Also trigger whenever: memory is referenced…
cuj-guardian
Run and triage AI Atelie's Critical User Journey (CUJ) for every PR — the single end-to-end test that proves a user can open the app, create a project, drive the Claude Code agent, and see the canvas render. Before running, gate by inspecting the PR diff for changes that plausibly affect the journey (routes…
canvas-sync
Keep the canvas surface coherent across its three places — the canonical starter at mcp/starters/DesignCanvas.jsx, the byte-identical demo copy at web/projects/demo/design-canvas.jsx, and the host-side wiring in web/src/lib/tweakBridge.ts plus mcp/CANVASPROTOCOL.md. Use whenever the diff touches any of those files, or…
ship-task
Take an AI Atelie task — issue, ticket, or ad-hoc ask — all the way from description to merged-ready PR. Use whenever the user says "implement X and ship it", "work on issue.