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 manishiitg/coding-agent-loop --skill post-incident-review-actionsgit clone --depth 1 https://github.com/manishiitg/coding-agent-loopWrote 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/manishiitg/coding-agent-loop/post-incident-review-actions)<a href="https://agentmods.dev/skills/manishiitg/coding-agent-loop/post-incident-review-actions"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/post-incident-review-actions/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/manishiitg/coding-agent-loop/post-incident-review-actions"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/post-incident-review-actions.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.00025 | $0.00763 |
| Opus 5.5 | $0.00010 | $0.00305 |
| Sonnet 5.5 | $0.00005 | $0.00153 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
post-incident-review-actions 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 20d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-Incident Review and Actions
Outcome
Post-Incident Reviewer reconstructs a stabilized incident and proposes improvements. Improvement Follow-Through Coordinator tracks decisions, issue receipts and independent control evidence. A draft is not published; a closed issue is not verified improvement.
When to use
Use after verified stability or an approved near miss. Keep live mitigation in Incident to Verified Recovery. Both jobs use the same incident, service and environment. One Crew may carry both skills when access fits; validate each output.
Discovery and user direction
Builder inspects incident/recovery records, Crews, impact rules, sources, privacy, owners and issue/verification access. It proposes both jobs in chat. Selection creates no Crew, ticket, publication, reminder or schedule.
Required inputs
Record incident/service/environment, verified stability source, frozen evidence window, impact numerator and denominator, timeline, review owner and audience, sensitive-data rule, action owners/dates, verification criteria, issue and approval policy. Publication and recurrence are optional separate decisions.
Plan and AgentWorks tools
- Bind two Crew IDs and Workflow steps. Reviewer saves
post-incident-review/v1with exact sources, impact arithmetic, factor labels, unknowns and proposed actions. Runpython3 scripts/validate_handoff.py review <review.json>as a blocking step. Owner approval is a dated decision, separate from drafting. - Pass the validated review by checked alias. Coordinator saves
incident-improvement-register/v1, preserving exact action IDs. Runpython3 scripts/validate_handoff.py register <review.json> <register.json>before reporting. Pending review creates no issue. Accepted work needs decision and issue receipt; verified work needs later independent passing evidence. - Review source truth, privacy and next actions with owners. Issue creation, publication, notifications and changes require separately authorized routes and receipts.
What ships with it
12 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.
- examples/incident-improvement-pending.json 1.3 KB
- examples/incident-improvement-register.json 2.3 KB
- examples/invalid-improvement-register.json 2.0 KB
- examples/invalid-post-incident-review.json 4.1 KB
- examples/post-incident-draft.json 3.9 KB
- examples/post-incident-review.json 4.2 KB
- playbook.json 5.9 KB
- references/post-incident-workflow.md 2.1 KB
- references/team-and-handoffs.md 3.0 KB
- scripts/test_validate_handoff.py 4.2 KB runs code
- scripts/validate_handoff.py 14 KB runs code
- SETUP.json 3.0 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.
- 20d ago Changed · -13 tokens per session 11371ae7f6ad
- 1mo ago First seen · 52 lines · 38 tokens per session scan A 345a63c17650
post-incident-review-actions is a skill published in the GitHub repository manishiitg/coding-agent-loop (13 stars, last pushed 19d ago), licensed MIT. It adds 25 tokens to every session and 763 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
kungfu-agent-onboarding
Use when a user asks to understand, start, inspect, extend, or safely operate installed Kungfu; verify the installed pack, select one intent route, personalize the explanation, and propose one smallest safe next action.
machinist
Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, intake labels, direct runs, or managed queue.
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
goga-task-by-specifying
Interactive task formulation from a raw request.
goga-cell-go
Golang rules for implementing CODEMANIFEST contracts.
kano-backlog
Prioritize and refine a GitHub Issues backlog with the Kano model — categorize every open issue as Must-be, Performance, Attractive, Indifferent, or Reverse, apply Kano + priority labels back to GitHub automatically, and recommend the single best next issue to pick up. Use this whenever the user wants to triage…