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-exploregit 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-explore)<a href="https://agentmods.dev/skills/plunderstruck/scip-query/scip-explore"><img src="https://agentmods.dev/badge/skills/plunderstruck/scip-query/scip-explore/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.
<a href="https://agentmods.dev/skills/plunderstruck/scip-query/scip-explore"><img src="https://agentmods.dev/badge/skills/plunderstruck/scip-query/scip-explore.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.00657 |
| Opus 5.5 | $0.00010 | $0.00263 |
| Sonnet 5.5 | $0.00005 | $0.00131 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
scip-explore 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 1mo 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SCIP Explore
Load $scip-query for mechanics when the question crosses code locations or module boundaries. Use ordinary search and file tools for a local lookup or implementation read.
A repository system is cooperating code and resources that turns an initiating input into observable results. Establish only the parts whose behavior could change the requested answer or edit. For substantial work, keep concise notes on established facts and remaining questions; a formal evidence ledger is not required.
Find the existing path
Start with locations named by the request or found through ordinary search. Use system --source when module structure is unknown, entrypoints when the initiating surface is unclear, and context <target> when existing reuse or impact candidates matter. Avoid repeating source through another command once its behavior is established.
When several implementations appear relevant, compare their entry surfaces, incoming execution, runtime connections and consumers. Path, recency and result order do not establish the live implementation. Keep distinct paths separate until routing or behavior resolves which serves the request.
Before planning new behavior, find a comparable working feature and the central path it uses. Identify the existing owners and extension points. Use $scip-plan to document this flow and the reuse decisions before implementation.
Resolve relationships and behavior
Choose the relationship that answers the next concrete question: incoming execution for callers; outgoing execution for callees; runtime for producer/consumer handoffs; dataflow for value transfer; dependencies for module reliance. Batch related roots. Use another family only when its meaning matches the missing fact. The command guide covers specialist choices.
Read implementations and relevant invocations with ordinary tools to verify predicates, arguments and effects. Preserve the decisions that matter: authorization, precedence, bounds, transformations, state writes, returned defaults, notifications, owner lifetime, concurrency, errors and recovery. Follow queued work to its consumer when completion depends on it.
What ships with it
5 files 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.
- 1mo ago Changed · -22 lines · -18 tokens per session 9fb1e41e69f7
- 1mo ago Changed · -22 lines · -58 tokens per session 0251c009fb87
- 1mo ago First seen · 79 lines · 100 tokens per session scan A fb1105094fba
scip-explore is a skill published in the GitHub repository PlunderStruck/scip-query (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 24 tokens to every session and 657 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.
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…
tilth
Use the tilth CLI for code reading, outlining, search, callers, blast-radius deps, and structural diffs. Activate when the user asks to explore a repo, find a symbol, trace callers, read a file, view a diff, or analyze impact. Prefer tilth over grep/cat/find/ls — one invocation returns AST-aware outlines, definitions…
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.
use-ivygrep
Gather focused local repository context with ivygrep before implementing, debugging, reviewing, or explaining code. Use for coding tasks involving unfamiliar paths, branch changes, stack traces, architectural relationships, callers, dependents, tests, configuration, or documentation. Prefer one bounded context pack…
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…