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 instructions/plunderstruck/scip-query/claude-mdgit 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/instructions/plunderstruck/scip-query/claude-md)<a href="https://agentmods.dev/instructions/plunderstruck/scip-query/claude-md"><img src="https://agentmods.dev/badge/instructions/plunderstruck/scip-query/claude-md.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 | $0.00026 | $0.00026 |
| Opus 5 | $0.00013 | $0.00013 |
| Sonnet 5 | $0.00005 | $0.00005 |
| Haiku 4.5 | $0.00003 | $0.00003 |
Grade A, and why
scip-query CLAUDE.md 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 4d 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.
What it actually says
@AGENTS.md
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.
- 4d ago First seen · 4 lines · 26 tokens per session scan A bbadc8c991ad
scip-query CLAUDE.md is an instructions file published in the GitHub repository PlunderStruck/scip-query (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session, about $0.0001 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 instructions, from other repositories
mcpls copilot-instructions.md
Copilot instructions for bug-ops/mcpls, covering copilot instructions for mcpls, type safety, idiomatic rust, architecture and async.
mcpls rust-bridge.instructions.md
Instructions for bug-ops/mcpls, covering type safety, document state, diagnostics pipeline, concurrency and lock scope and file watcher.
leantoken AGENTS.md
AGENTS.md instructions for morluto/leantoken, covering repository guidance, architecture, development, change-specific validation and contributions.
mcpls mcp-tools.instructions.md
Instructions for bug-ops/mcpls, covering type safety, error handling and idiomatic dispatch.
mcpls rust-config.instructions.md
Instructions for bug-ops/mcpls, covering type safety and idiomatic config and msrv and dependencies.
mcpls tests.instructions.md
Instructions for bug-ops/mcpls, covering test design, correctness invariants to cover and idiomatic test code.