Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/studioKjm/ai-harness-templatenpx agentmods add commands/studiokjm/ai-harness-template/incident-actionWrote 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/commands/studiokjm/ai-harness-template/incident-action)<a href="https://agentmods.dev/commands/studiokjm/ai-harness-template/incident-action"><img src="https://agentmods.dev/badge/commands/studiokjm/ai-harness-template/incident-action/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/commands/studiokjm/ai-harness-template/incident-action"><img src="https://agentmods.dev/badge/commands/studiokjm/ai-harness-template/incident-action.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.00016 | $0.01327 |
| Opus 5 | $0.00008 | $0.00664 |
| Sonnet 5 | $0.00003 | $0.00265 |
| Haiku 4.5 | $0.00002 | $0.00133 |
Grade A, and why
incident-action 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 9d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/incident-action — Manage Action Items
A postmortem without action items is just a story. Make the learning durable.
When to use
- During or after
/incident analyze— capture each follow-up - When a follow-up actually ships (or is decided not to ship)
- When converting a follow-up into a tracked task/story/ADR
Usage
/incident-action add <incident-id> \
--description "..." \
--owner NAME \
--due YYYY-MM-DD \
[--priority high|medium|low] \
[--action-id ID]
/incident-action resolve <incident-id> \
--action-id ID \
--status done|dropped|converted \
[--converted-to TASK_OR_STORY_OR_ADR_ID]
Action item format requirements
| Field | Required | Format |
|---|---|---|
| description | yes | Specific. "Add alert for X" not "improve monitoring" |
| owner | yes | One person, not a team |
| due_date | yes | YYYY-MM-DD. Realistic, not aspirational |
| priority | yes | high / medium / low (default: medium) |
| status | auto | open → in-progress → done/dropped/converted |
Status semantics
| Status | Meaning |
|---|---|
| open | Not started |
| in-progress | Being worked on |
| done | Fix shipped, verified |
| dropped | Decided not to do — must record reason in notes field |
| converted | Moved to longer-form artifact (task/story/ADR) — must specify --converted-to |
Instructions
Step 1 — Add action items during analyze
# After RCA reveals: alert was missing
python3 .harness/methodologies/incident-review/scripts/inc.py \
action add inc-2026-04-30-billing-outage \
--description "Add alert when DB connection pool > 80% for 5min" \
--owner "jimin" \
--due "2026-05-15" \
--priority high
# Process change action
python3 .harness/methodologies/incident-review/scripts/inc.py \
action add inc-2026-04-30-billing-outage \
--description "Update billing runbook with new failure mode" \
--owner "jimin" \
--due "2026-05-08" \
--priority medium
Step 2 — Update status as work progresses
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.
- 9d ago First seen · 155 lines · 16 tokens per session scan A 0de5e2bd780f
incident-action is a command published in the GitHub repository studioKjm/ai-harness-template (43 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 1,327 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.
project-principles
Define your project's non-negotiable principles, commitments, and boundaries.
set-tracker
Set the issue tracker for the current project.
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.
fire-todos
Capture, list, and manage todos during work sessions.
fire-execute-plan
Execute a single plan with segment-based routing, per-task atomic commits, and test enforcement.