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 noordeen123/culprit --skill claude-code-skillgit clone --depth 1 https://github.com/noordeen123/culpritWrote 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/noordeen123/culprit/claude-code-skill)<a href="https://agentmods.dev/skills/noordeen123/culprit/claude-code-skill"><img src="https://agentmods.dev/badge/skills/noordeen123/culprit/claude-code-skill.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.00173 | $0.02428 |
| Opus 5 | $0.00086 | $0.01214 |
| Sonnet 5 | $0.00035 | $0.00486 |
| Haiku 4.5 | $0.00017 | $0.00243 |
Grade A, and why
rca 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.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RCA (Root Cause Analysis) + QA review
Runs the deterministic culprit engine to produce a structured analysis + markdown skeleton, then you write the "why it broke" / risk narrative by reading the actual diffs of the suspect commits.
Invoking culprit (<RCA>)
- Installed (
pip install culprit):rca(orculprit). - From a checkout, no install:
PYTHONPATH=/path/to/culprit python3 -m culprit.cli.
The examples below write <RCA> for whichever form you use, and --repo <REPO_PATH>
(omit it when running from inside the repo - it defaults to the current directory).
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 · 164 lines · 173 tokens per session scan A 70c51ff38a13
rca is a skill published in the GitHub repository noordeen123/culprit (6 stars, last pushed 12d ago), licensed MIT. It adds 173 tokens to every session and 2,428 once invoked, about $0.0009 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-31.
Other skills, from other repositories
printing-press-output-review
Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by the main printing-press skill at Phase 4.85 and printing-press-polish…
fix
Dispatch fix subagent for FIX-FIRST gaps from review, re-review, then diagnose unresolved failures after 2 loops.
test-driven-development
This skill should be used when implementing new features, fixing bugs, or writing new code. Enforces RED-GREEN-REFACTOR.
testing
This skill should be used when the user asks to "write tests", "fix failing tests", "improve test coverage", "add integration tests", "debug a flaky test", or reviews test quality. Provides behavior-focused testing patterns, coverage analysis, and detection of brittle test anti-patterns like implementation coupling…
pythinker-code-help
Answer Pythinker CLI usage, configuration, and troubleshooting questions. Use when user asks about Pythinker CLI installation, setup, configuration, slash commands, keyboard shortcuts, MCP integration, providers, environment variables, how something works internally, or any questions about Pythinker CLI itself.
diagnose-ci-failures
Diagnose failing CI, lint, typecheck, build, or test logs and propose or implement the smallest verified fix.