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/deepscan-security/dscan/claude-mdgit clone --depth 1 https://github.com/DeepScan-Security/dscanWhat 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.00265 | $0.00265 |
| Opus 5 | $0.00133 | $0.00133 |
| Sonnet 5 | $0.00053 | $0.00053 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
dscan 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 28 lines · 265 tokens per session scan A 854660a2bf0c
dscan CLAUDE.md is an instructions file published in the GitHub repository DeepScan-Security/dscan (3 stars, last pushed 1mo ago), with no licence file. It adds 265 tokens to every session, about $0.0013 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
aguara CLAUDE.md
Instructions for garagon/aguara, covering claude.md, project status, build & test commands, single package test and single test function.
aguara AGENTS.md
Instructions for garagon/aguara, covering agents.md - aguara reference for ai agents, quick start, install, scan a directory and scan with ci defaults (fail on high+, no color).
medusa CLAUDE.md
Claude Code instructions for Pantheon-Security/medusa, covering medusa - medusa security scanning, critical: release gate — do not skip, 4. security hardening tests (must show: all pass), critical: bash sandbox and project overview.
SecureAI-Scan CLAUDE.md
Instructions for akanthed/SecureAI-Scan, covering claude.md, what this is, hard requirements (non-negotiable, apply to every change), 1. zero tolerance for false positives and commands.
ai-appsec AGENTS.md
Instructions for subodhkc/ai-appsec, covering agents.md — haiec agent security mcp (phase -1 → phase 18), 1. workspace layout, 2. architectural principles (apply to every phase), 3. hard constraints (never violate) and 4. phase discipline.
pkgxray CLAUDE.md
Instructions for adamsjack711-ux/pkgxray, covering project, rules, skills, getting started and commands.