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-integrity-auditgit 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-integrity-audit)<a href="https://agentmods.dev/skills/plunderstruck/scip-query/scip-integrity-audit"><img src="https://agentmods.dev/badge/skills/plunderstruck/scip-query/scip-integrity-audit/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-integrity-audit"><img src="https://agentmods.dev/badge/skills/plunderstruck/scip-query/scip-integrity-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 30 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00044 | $0.00975 |
| Opus 5 | $0.00022 | $0.00487 |
| Sonnet 5 | $0.00009 | $0.00195 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
scip-integrity-audit 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SCIP Integrity Audit
Load $scip-query for mechanics and $scip-explore when the live path is unknown. Ask “is this real?”: does the implementation produce the outcome its user or consumer relies on?
Use the implementation-integrity command guide to select a detector for a named concern. Its rows describe what each pattern can miss or misclassify; no detector replaces the live-path investigation below.
An integrity defect is a mismatch between promised behavior and the behavior the live implementation provides. Establish the promise from the task, public contract, consumers, and relevant tests—not a function name alone. A fallback is an alternative selected when another implementation fails or is unavailable; its use cannot support a stronger guarantee than it provides.
Do not attribute intentions such as cheating to an agent or author. Report the concrete shortcut, missing operation, unsupported claim, and consequence.
Establish promise and live path
State which input should produce which result, rejection, or durable effect. Record uncertainty when requirements are unclear; do not invent a stronger feature and call its absence a defect.
Trace the actual command/API/worker through selected implementations, configuration, effects, fallbacks, and consumers. Inventory plausible parallel implementations even with different names. An installed parser, new class, or unit test calling a helper does not prove production consumers use it.
Choose investigations below for actual evidence gaps. There is no mandatory all-detector battery or requirement to manufacture a finding.
Investigate the mechanism
| Concern | Investigation |
|---|---|
| Success without checking | Run valid and deliberately invalid cases through the public path with independent expected results. Inspect delegated/asynchronous failure before declaring a decorative checker. |
| Feature works only through fallback | Observe primary success and induced failure. Establish the selected path, result/effects, and whether degraded behavior is disclosed. |
| Parser assumes an imagined format | Feed the actual parser/version representative captured input or valid language examples. Verify the consuming traversal and output, not a node merely appearing somewhere. |
| Replacement beside old mechanisms | Trace relevant ingress/configuration variants. Compare cases distinguishing their guarantees; account for consumers and retirement. |
| Status or metric overstates evidence | Trace inputs and coverage to the supporting operation. Independently calculate distinguishing examples; test omissions, errors, and partial results. |
| Tests share implementation mistakes | Exercise a real consumer with independent expected results. Checking only a mocked value does not verify the feature. |
What ships with it
2 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 · -128 lines · -24 tokens per session aa1302b19014
- 9d ago First seen · 186 lines · 68 tokens per session scan A 6865dffe25d4
scip-integrity-audit is a skill published in the GitHub repository PlunderStruck/scip-query (6 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 975 once invoked, about $0.0002 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…
dd-triage-flaky-test
Load when investigating a specific flaky test. Gets history, failure pattern, and category, then recommends fix, quarantine, or escalate.
dd-unblock-pr
Load when investigating a failing PR CI pipeline or checking PR health. Attributes each CI failure as flaky, infra, or regression, proposes a targeted action, and reports code coverage.
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…
agent-inspect
Local evidence debugger and trajectory-test toolkit for TypeScript AI agents. Use when capturing framework-faithful traces, asserting TraceContract/TraceFacts, packaging Evidence v2, or inspecting local runs over read-only MCP (gettracefacts).
confirm-failures-are-causally-linked-to-the-task-before-reportin
When delegating a task affected by this skill, include.