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 agentmods add skills/plunderstruck/scip-query/scip-root-causenpx skills add PlunderStruck/scip-query --skill scip-root-causegit clone --depth 1 https://github.com/PlunderStruck/scip-queryWrote 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/plunderstruck/scip-query/scip-root-cause)<a href="https://agentmods.dev/skills/plunderstruck/scip-query/scip-root-cause"><img src="https://agentmods.dev/badge/skills/plunderstruck/scip-query/scip-root-cause.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.00074 | $0.02489 |
| Opus 5 | $0.00037 | $0.01244 |
| Sonnet 5 | $0.00015 | $0.00498 |
| Haiku 4.5 | $0.00007 | $0.00249 |
Grade A, and why
scip-root-cause 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 2d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
scip-root-cause
Command and question manual
| Command syntax | Question it answers |
|---|---|
scip-query trace <symbol> |
Trace one bug mechanism: definition plus every reference of the symbol that broke the invariant. |
scip-query code <selector> |
Read the exact body at a fix site or a suspected latent instance. |
scip-query evidence --symbol <symbol> --edge dataflow --direction both --depth <n> --max-edges <n> |
Follow where a violated value comes from and where it goes. |
scip-query co-change <file> |
Find fix-site partners from git history that the user may have forgotten. |
scip-query system <scope> |
Define the owning system: its files, exports, and dependencies. |
scip-query surface <scope> |
See what consumers actually rely on from the owning system. |
scip-query similar <symbol> --full |
Hunt latent instances: callables that do the same work as a fixed symbol. |
scip-query refs <symbol> |
Hunt latent instances: every site that touches the invariant carrier. |
scip-query affected <symbol> |
Bound the blast radius before proposing any remedy above rung 1. |
These commands are controls, not a checklist. Use every capability needed by the task, but make each query answer a distinct question. There is no required sequence or query limit. Run a command's --help when you need a flag not shown in its template.
Use this skill to move from a family of related bugs to the design flaw that produces them, and to the least invasive remedy that eliminates the class. Ordinary debugging takes one failure to one minimal fix. $principal-maintainability-review finds structural smells without bug evidence. This skill starts from the evidence that patching has not worked, because the same kind of bug keeps coming back, and asks what the system's design gets wrong.
Terms
A bug family is a set of failures whose mechanisms violate the same invariant. What makes it a family rather than a coincidence is that one stated flaw derives every member, so fixing members one at a time treats symptoms of a shared cause.
What ships with it
1 file 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.
- 2d ago First seen · 161 lines · 74 tokens per session scan A 4eb9532141f1
scip-root-cause is a skill published in the GitHub repository PlunderStruck/scip-query (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 74 tokens to every session and 2,489 once invoked, about $0.0004 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-09-04.
Other skills, from other repositories
dead-code-cleanup
Use when the user asks about cleanup, removing unused code, refactoring, reducing bundle size, or identifying dead code in a Repowise-indexed codebase (.repowise/ directory exists). Also activates when discussing technical debt, code hygiene, or repository maintenance.
mcpls
Install, configure, and run the mcpls CLI — a Rust binary bridging MCP to LSP that gives an agent compiler-grade code intelligence (hover, definitions, references, diagnostics, rename). Use when setting up or registering mcpls as an MCP server, writing or debugging an mcpls.toml, choosing CLI flags or MCPLS…
codespaces
Build and query architecture-aware code search, dependency graphs, call flows, impact analysis, and belief maps for Python, TypeScript, TSX, Rust, C#, Java, Go, Ruby, and Ruby on Rails repositories. Use before non-trivial code changes to find module boundaries, blast radius, architecture violations, and the minimal…
frigg-first-code-search
Prefer Frigg MCP for indexed source. resulthandle + readmatch for proof.
jarvis-issues
Report bugs and request features for the jarvis MCP server via GitHub issues. Use when jarvis errors, an index fails, a limitation bites, or to request an improvement.
jarvis-setup
Install and configure jarvis, the local-first structural code intelligence. Use when onboarding, running setup.sh, registering the MCP server, or indexing a repo for the first time.