Borrowing it
Nothing to install: this file belongs to cardstack/boxel. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cardstack/boxel/main/.claude/skills/incident-report/SKILL.mdgit clone --depth 1 https://github.com/cardstack/boxelWrote 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/cardstack/boxel/incident-report)<a href="https://agentmods.dev/skills/cardstack/boxel/incident-report"><img src="https://agentmods.dev/badge/skills/cardstack/boxel/incident-report/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/skills/cardstack/boxel/incident-report"><img src="https://agentmods.dev/badge/skills/cardstack/boxel/incident-report.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.00160 | $0.02323 |
| Opus 5.5 | $0.00064 | $0.00929 |
| Sonnet 5.5 | $0.00032 | $0.00465 |
| Haiku 4.5 | $0.00016 | $0.00232 |
Grade A, and why
incident-report 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 5d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident report
This skill keeps every boxel incident write-up in one recognizable house style and one honest voice, so a reader who has seen one report can read the next at a glance. It covers how to structure, word, and publish the report — not how to investigate. Gather the evidence first (see Step 0), then render it here.
The canonical examples — both built to the structure and tone below; new reports should look and read like these siblings (open in a browser signed in to the Cardstack org):
- 2026-07-15 staging 503 — https://claude.ai/code/artifact/97592f4d-372b-4727-8220-c3a32b96d001
- 2026-07-16 staging 504 — https://claude.ai/code/artifact/02f27e4b-ddbf-485e-a1fd-319eedd2dca1
Step 0 — investigate first; the report renders evidence, never assumptions
A report is only as good as what it's built on. Before writing a line, pin the facts with real data:
- Deployed-env access + logs → the
aws-accessskill (ALB/ECS/CloudWatch metrics, RDS, EFS) andtail-logs(Loki). - Slow/failed indexing or renders →
indexing-diagnostics. - Prerender pool saturation / sizing →
prerender-sizing.
Pin, with sources: the exact incident window, per-code error counts (503 vs 504 vs target-5xx — they mean different things), the peak/precursor spikes, target response times, the deploy/task-def timeline, the health-check + rollout config, and any git/PR/ticket that correlates. If a claim can't be backed by a metric, a log line, or config, either verify it or mark it explicitly as inferred. The "ruled out" section (below) is not optional — an incident report that only argues for one cause is weaker than one that also says what it isn't.
The deliverable
Default to an Artifact (via the Artifact tool) — it renders the house style directly. An incident report is meant to be read by the whole team, so its end state is shared with the "Cardstack" organization, not left private (see Publish & track). The palette and structure here are already decided; do not re-derive them.
What ships with it
1 file 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.
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.
- 5d ago First seen · 87 lines · 160 tokens per session scan A 6a4cc48156d5
incident-report is a skill published in the GitHub repository cardstack/boxel (27 stars, last pushed today), licensed MIT. It adds 160 tokens to every session and 2,323 once invoked, about $0.0006 per session on Opus 5.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-10-21.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.