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-system-compressionnpx skills add PlunderStruck/scip-query --skill scip-system-compressiongit 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-system-compression)<a href="https://agentmods.dev/skills/plunderstruck/scip-query/scip-system-compression"><img src="https://agentmods.dev/badge/skills/plunderstruck/scip-query/scip-system-compression.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.00061 | $0.03573 |
| Opus 5 | $0.00030 | $0.01786 |
| Sonnet 5 | $0.00012 | $0.00715 |
| Haiku 4.5 | $0.00006 | $0.00357 |
Grade A, and why
scip-system-compression 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 yesterday.
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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SCIP System Compression
Command and question manual
| Command syntax | Question it answers |
|---|---|
scip-query system <scope> |
Map a module or directory: files, exported symbols, dependencies in and out. |
scip-query surface <scope> |
See which symbols consumers actually use from the scope. |
scip-query outline <file> |
Inventory one file before assigning its units to roles. |
scip-query trace <symbol> |
Prove a key symbol: definition plus every reference. |
scip-query call-graph <symbol> |
Prove a key symbol: callers and callees along its execution shape. |
scip-query affected <symbol> |
Measure blast radius before choosing a compression model. |
scip-query change-surface <file> |
Measure exports, consumers, and risk for a file a cluster will touch. |
scip-query similar --cross-file-only |
Signal: functions with overlapping callee sets across files. |
scip-query similar-files |
Signal: files with overlapping dependency profiles. |
scip-query similar-chains |
Signal: parallel end-to-end flows that diverge at a few points. |
scip-query extract-candidates |
Signal: large functions with isolated callee clusters. |
scip-query wrapper-candidates |
Signal: single-consumer indirection that a compression may absorb. |
scip-query passthrough-candidates |
Signal: pure forwarding functions. |
scip-query stale-abstractions |
Signal: types and classes with zero or one consumer. |
scip-query drift --architecture |
Signal: files deviating from sibling conventions and declared boundary violations. |
scip-query diff-impact |
Audit after each implemented cluster: changed symbols and downstream consumers. |
scip-query architecture |
Audit after each implemented cluster: declared boundaries still hold. |
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.
What ships with it
3 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.
- yesterday Changed · +219 lines · +9 tokens per session 7b1378bca86e
- 5d ago First seen · 34 lines · 52 tokens per session scan A 79f7069eaf3d
scip-system-compression is a skill published in the GitHub repository PlunderStruck/scip-query (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 61 tokens to every session and 3,573 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
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…
codebase-exploration
Use when exploring, understanding, or answering questions about a codebase that has Repowise indexed (a .repowise/ directory in the project root). Activates for "how does X work", "explain the architecture", "where is Y implemented", "what does this module do", or any task that needs an understanding of structure…
architectural-decisions
Use when encountering questions about WHY code is built a certain way, when about to make architectural changes (new patterns, restructuring, choosing between approaches), or when the user asks about design rationale in a Repowise-indexed codebase (.repowise/ directory exists). Also activates when commit messages or…
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…
pre-modification-check
Use before modifying, refactoring, or deleting files in a codebase that has Repowise indexed (indicated by a .repowise/ directory). Activates when Claude is about to edit code, especially shared utilities, core modules, or files the user didn't explicitly mention. Helps assess impact and avoid breaking things.
pre-modification-check
Use before modifying, refactoring, moving, or deleting files in a Repowise-indexed repository, especially shared utilities, core modules, public APIs, or files the user did not explicitly identify.