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 yeaight7/agent-powerups --skill incident-readoutgit clone --depth 1 https://github.com/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/incident-readout)<a href="https://agentmods.dev/skills/yeaight7/agent-powerups/incident-readout"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/incident-readout/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/yeaight7/agent-powerups/incident-readout"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/incident-readout.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.00552 |
| Opus 5.5 | $0.00012 | $0.00221 |
| Sonnet 5.5 | $0.00006 | $0.00110 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
incident-readout 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 1mo 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
When a complex debugging session ends, produce an incident readout. This prevents knowledge loss and helps humans review the fix quickly. Keep it blameless: causes and prevention, not people.
When to Use
- A bug fix landed after a non-trivial debugging session
- An incident is resolved and needs a reviewable summary
- Session knowledge would otherwise be lost at handoff
Inputs
- The fix (diff or commits) and the debugging context from the session
- The related PR or issue, if one exists
Workflow
-
Reconstruct the facts from history — pull them from the repo rather than recalling them:
git log --oneline -10 # the fix commits git show <fix-commit> --stat # what the fix touched gh pr view <number> --json title,body,comments # if a PR exists -
Fill the readout structure. Output an incident readout document (or print to terminal) using this structure:
### 1. The Symptom What was reported? (1-2 sentences) ### 2. The Root Cause What was the actual underlying technical reason for the failure? Be highly specific about the exact line of code, assumption, or state that failed. ### 3. The Fix What did we change to fix it? Provide a high-level summary of the structural change, not just a diff. ### 4. Prevention How do we ensure this never happens again? (e.g., "Added test case X", "Refactored module Y to be strongly typed").
Output
- A four-section readout (Symptom / Root Cause / Fix / Prevention), as a document or terminal output
Verification
- Root cause names the specific line, assumption, or state — not a vague area
- Fix described structurally, not as a pasted diff
- Prevention is a concrete action, not "be more careful"
- Claims cross-checked against the actual commits/PR, not memory
Failure Modes
- Symptom-as-cause — restating the error message in the Root Cause section.
- Diff dumping — pasting the patch where a structural summary is needed.
- Empty prevention — "fixed it" without a regression test or structural guard.
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.
- 1mo ago First seen · 66 lines · 30 tokens per session scan A 3f187f0a1ad4
incident-readout is a skill published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 19d ago), licensed Apache-2.0. It adds 30 tokens to every session and 552 once invoked, about $0.0001 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-09-14.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
simplify-code
Sequential 3-lens cleanup of recent code changes.
node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol.
python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
hqe
Comprehensive codebase health auditing, remediation, and verification skill based on the canonical HQE Protocol v5.0.0.
adk-debug
Diagnoses misbehaving ADK agents by inspecting sessions, events, tool calls, and the exact request that reached the model. Covers the adk run CLI and the adk web dev server with its session, trace, and debug HTTP endpoints. Use when an agent returns the wrong answer, ignores a tool or swallows a tool error, hangs…