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 PlunderStruck/scip-query --skill scip-plangit 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-plan)<a href="https://agentmods.dev/skills/plunderstruck/scip-query/scip-plan"><img src="https://agentmods.dev/badge/skills/plunderstruck/scip-query/scip-plan.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.00052 | $0.01470 |
| Opus 5 | $0.00026 | $0.00735 |
| Sonnet 5 | $0.00010 | $0.00294 |
| Haiku 4.5 | $0.00005 | $0.00147 |
Grade A, and why
scip-plan 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 7d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SCIP Plan
Write a plan that another coding agent can execute without rediscovering the relevant system.
Command and question manual
| Command syntax | Question it answers |
|---|---|
scip-query search <text> |
Locate exact repository text, a runtime key, or a compiler symbol; use `scip-query search -- ` when the literal starts with a dash. |
scip-query outline <file> |
Locate compiler-owned constructs in a known file. |
scip-query entrypoints <text> |
Locate an external callable root when its entry surface is known. |
scip-query evidence --symbol <symbol> --edge <family> --direction <direction> --depth <n> --max-edges <n> |
Project explicitly selected typed relationships from one exact root. |
scip-query inspect --at <file:line> --view behavior |
Read connected behavior for a named implementation gap. |
scip-query code <selector> |
Read exact source only when syntax itself can change the decision. |
scip-query diff-impact |
Map changed symbols and downstream consumers after an edit. |
scip-query architecture |
Validate declared structural boundaries. |
scip-query health --full |
Run configured cleanup and quality detectors. |
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.
Choose a relationship deliberately
| Question | Evidence family | Direction |
|---|---|---|
| Who can call or reach this? | execution |
incoming |
| What can this call or reach? | execution |
outgoing |
| Where can this value come from? | dataflow |
incoming |
| Where can this value go? | dataflow |
outgoing |
| Which producer and consumer rendezvous? | runtime |
both |
| What resource is observed or changed? | state |
both |
| What occurs before or after this? | temporal |
both |
| What interface constrains this? | contract |
both |
| Are these observations the same entity? | identity |
both |
| What contains or owns this? | ownership |
both |
| What does this statically rely on? | dependencies |
outgoing |
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.
- 7d ago First seen · 87 lines · 52 tokens per session scan A 35d0a59bd7a8
scip-plan is a skill published in the GitHub repository PlunderStruck/scip-query (6 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 1,470 once invoked, about $0.0003 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
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…
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
cymbal
Tree-sitter indexed code navigator. Use the cymbal CLI — not Read, Grep, Glob, or Bash — for finding where symbols are defined, tracing callers and callees, locating interface implementations, understanding the impact of a change, and mapping imports across an existing codebase. Returns precise, token-efficient…
gograph
Go repository intelligence for Claude Code. Use when reading, navigating, editing, reviewing, or refactoring a Go codebase. Exposes 64 query, analysis, and workflow capabilities through the local gograph MCP server, including bounded first-call exploration, AST-aware call graphs, blast-radius analysis, impact, and…
change-review
Use when reviewing a set of changes before they merge — a PR, a branch diff, or the working-tree changes you just made — in a Repowise-indexed codebase (.repowise/ directory exists). Activates for "review this PR", "is this safe to merge", "what's the blast radius of these changes", "did I miss anything", or "what…
code-health
Use when the user asks about code health, code quality, complexity, technical debt, which files are risky or hard to maintain, what to refactor next, untested hotspots, or coverage gaps in a Repowise-indexed codebase (.repowise/ directory exists). Also use to get a before/after health read when planning or finishing a…