Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add assafkip/kipi-system/plugin install kipi-coreWrote 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/assafkip/kipi-system/rca-check)<a href="https://agentmods.dev/commands/assafkip/kipi-system/rca-check"><img src="https://agentmods.dev/badge/commands/assafkip/kipi-system/rca-check.svg" alt="Measured on agentmods" 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.00013 | $0.00269 |
| Opus 5 | $0.00006 | $0.00134 |
| Sonnet 5 | $0.00003 | $0.00054 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
rca-check 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 8d 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.
What it actually says
Run the deterministic RCA lint on a document. The author passes a file path; if none is given, lint every RCA/premortem doc found.
Single file
python3 "${CLAUDE_PLUGIN_ROOT}/skills/rca/scripts/rca-lint.py" "$ARGUMENTS"
All RCA docs (when no path given)
found=0
for f in $(find . -type f \( -name 'rca-*.md' -o -name 'premortem-*.md' \) -not -path '*/.git/*' 2>/dev/null); do
found=1
python3 "${CLAUDE_PLUGIN_ROOT}/skills/rca/scripts/rca-lint.py" "$f" || true
done
[ "$found" = 0 ] && echo "no rca-*.md / premortem-*.md docs found"
Exit 0 means clean. Exit 2 lists exactly which required sections, cause-type tags, verification evidence, checkbox action items, or blameless rules are missing. Surface the report verbatim and fix per the template.
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.
- 8d ago First seen · 29 lines · 13 tokens per session scan A 7e43bd90e36f
rca-check is a command published in the GitHub repository assafkip/kipi-system (110 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 269 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.