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/vercel-labs/deepsec/claude-mdgit clone --depth 1 https://github.com/vercel-labs/deepsecWrote 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/vercel-labs/deepsec/claude-md)<a href="https://agentmods.dev/instructions/vercel-labs/deepsec/claude-md"><img src="https://agentmods.dev/badge/instructions/vercel-labs/deepsec/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.00411 | $0.00411 |
| Opus 5 | $0.00205 | $0.00205 |
| Sonnet 5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
deepsec 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
CLAUDE.md
Pointer file for Claude Code working in this repo. User-facing docs are in README.md; contributor docs in CONTRIBUTING.md. Read those first.
Repo shape
packages/
core/ Types, schemas, plugin contracts, config loader (defineConfig)
scanner/ Regex matchers + scanning engine
processor/ AI agent integration (Claude Agent SDK, Codex SDK), enrich, triage, revalidate
deepsec/ Publishable package: bundled CLI + the `deepsec/config` sub-export + the @vercel/sandbox executor
e2e/ End-to-end tests
Commands
pnpm install
pnpm test # all packages, including e2e
pnpm test:unit # excludes e2e
pnpm -r build # tsc across all workspaces (typecheck)
pnpm bundle # esbuild bundle for distribution
pnpm deepsec ... # the CLI (runs via tsx)
Patterns to keep in mind
- Plugin contracts live in
packages/core/src/plugin.ts. Internals route throughgetRegistry()fromdeepsec/configrather than calling organization-specific code directly. - The CLI auto-loads
deepsec.config.{ts,mjs,js,cjs}from cwd upward (viapackages/deepsec/src/load-config.ts, jiti). - New matchers go in
packages/scanner/src/matchers/and register inmatchers/index.ts. Org-specific matchers belong in a separate plugin package, not in this tree. - The AI prompt template lives in
packages/processor/src/index.ts. It is intentionally generic. Don't add organization-specific context there; usedata/<projectId>/INFO.mdorconfig.json:promptAppend.
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 · 42 lines · 411 tokens per session scan A 3bf7fd9f4adb
deepsec CLAUDE.md is an instructions file published in the GitHub repository vercel-labs/deepsec (7,903 stars, last pushed 8d ago), licensed Apache-2.0. It adds 411 tokens to every session, about $0.0021 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-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.