file-incident

file-incident is a command for Claude Code from psreek-ai/codebase-mooc. It costs 26 tokens per session (344 once invoked), scanned A, original, no licence file.

A command for recording a post-mortem or incident report about curriculum processing. A post-mortem documents what failed and why.

In plain words
What is it for?
Use it after a curriculum-processing incident when you need to file the report for Pathologist review.
Why use it?
It turns a processing failure into a structured record that can be used to document the failure mode.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the codebase-mooc plugin — 3 skills, 6 commands, 9 agents, 3 hooks shipped together

Good fit Use it after a curriculum-processing incident when you need to file the report for Pathologist review.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/psreek-ai/codebase-mooc/file-incident
Install

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.

Clone the repo
git clone --depth 1 https://github.com/psreek-ai/codebase-mooc

Made for: Claude Code.

Or install codebase-mooc, the plugin that ships this one along with the rest of its 3 skills, 6 commands, 9 agents, 3 hooks.

Wrote 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.

agentmods badge for file-incident

README.md
[![agentmods](https://agentmods.dev/badge/commands/psreek-ai/codebase-mooc/file-incident/github.svg)](https://agentmods.dev/commands/psreek-ai/codebase-mooc/file-incident)
Your own site
<a href="https://agentmods.dev/commands/psreek-ai/codebase-mooc/file-incident"><img src="https://agentmods.dev/badge/commands/psreek-ai/codebase-mooc/file-incident/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.

agentmods 80×15 button for file-incident

Your own site · 80×15
<a href="https://agentmods.dev/commands/psreek-ai/codebase-mooc/file-incident"><img src="https://agentmods.dev/badge/commands/psreek-ai/codebase-mooc/file-incident.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 344 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.00344
Opus 5.5 $0.00010 $0.00138
Sonnet 5.5 $0.00005 $0.00069
Haiku 4.5 $0.00003 $0.00034

Measured 2mo ago against content hash 33bc1f38309e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

file-incident 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 2mo 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.

commands/file-incident.md · 44 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 2mo ago First seen · 44 lines · 26 tokens per session scan A 33bc1f38309e

Subscribe to this mod's changes

file-incident is a command published in the GitHub repository psreek-ai/codebase-mooc (1 stars, last pushed 7mo ago), with no licence file. It adds 26 tokens to every session and 344 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-08-31.

Related

file-incident compared with commands from other repositories

file-incident next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
file-incidentpsreek-ai/codebase-moocCommand17mo agononeA26Claude Code
repo-docstractorjuice/arckit-claudeCommand64d agononeA15Claude Code
data-flow-analysissigistry/marketplaceCommand3todayMITA11Claude Code
build-fixgalyarderlabs/galyarder-frameworkCommand2926d agoMITA20Claude Code
postmortemsigistry/marketplaceCommand3todayMITA11Claude Code
doctor-devpunt-labs/z-specCommand5yesterdayMITB5Claude Code
hotfixlugassawan/swe-workbenchCommand32d agoMITA32Claude Code