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 ALTEN-group/coding-pal --skill incident-recordgit clone --depth 1 https://github.com/ALTEN-group/coding-palWrote 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/alten-group/coding-pal/incident-record)<a href="https://agentmods.dev/skills/alten-group/coding-pal/incident-record"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/incident-record/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/alten-group/coding-pal/incident-record"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/incident-record.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.00091 | $0.00686 |
| Opus 5.5 | $0.00036 | $0.00274 |
| Sonnet 5.5 | $0.00018 | $0.00137 |
| Haiku 4.5 | $0.00009 | $0.00069 |
Grade A, and why
incident-record 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 4d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Record
Turn a production incident into a validated record that proves the factory's incident rules: mitigation precedes diagnosis, humans conclude the cause, the repair starts with a failing test, the review happens within five working days, and every loss hardens a control or says why not.
When to Use This Skill
- An incident was mitigated and the timeline needs to become
docs/incidents/<YYYY-MM-DD>-<slug>.md. - CI must gate an incident record on a pull request.
- The monthly retrospective needs time to restore for an incident.
- A defect, rollback, or near-miss raises the question: what reached production that a control should have caught?
Path resolution
Resolve references/ and scripts/ relative to this skill's install directory (the folder that contains this SKILL.md), not the consumer repository root or the current shell cwd. If the skill was installed under .agents/skills/incident-record/ or .claude/skills/incident-record/, use that base path.
Workflow
- Read
references/incident-record-contract.mdnow. It is the authoritative source for headings, fields, timestamps, and rules. - Draft the record from the timeline notes, alerts, deploy history, and diffs the user supplies. Use real timestamps and commit ids. Never invent them. Leave a question under
## Ambiguities & Open Questionsinstead of guessing. - Do not conclude the cause. Present the correlated evidence and a proposed cause, and leave
Concluded ByandRollback Decided Byfor the named humans to fill in. - Validate with the script from this skill's directory:
node scripts/validate-incident.mjs --file docs/incidents/2026-10-13-checkout-5xx.md --tests-dir tests
Use --stage draft while the Triage issue number is not known yet. CI runs the default final stage.
- Read the printed time to restore and compare it with the target of under 15 minutes.
- Hand the validated record to the
learn-signalsskill so each control hardening item becomes a Triage backlog issue, then put the issue number inTriage Issue.
What ships with it
4 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.
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.
- 4d ago First seen · 46 lines · 91 tokens per session scan A 962ff096ef12
incident-record is a skill published in the GitHub repository ALTEN-group/coding-pal (5 stars, last pushed 5d ago), licensed MIT. It adds 91 tokens to every session and 686 once invoked, about $0.0004 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-14.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.