Borrowing it
Nothing to install: this file belongs to zebbern/pocmap. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zebbern/pocmap/main/CLAUDE.mdgit clone --depth 1 https://github.com/zebbern/pocmapWrote 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/zebbern/pocmap/claude-md)<a href="https://agentmods.dev/instructions/zebbern/pocmap/claude-md"><img src="https://agentmods.dev/badge/instructions/zebbern/pocmap/claude-md/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/instructions/zebbern/pocmap/claude-md"><img src="https://agentmods.dev/badge/instructions/zebbern/pocmap/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.02315 | $0.02315 |
| Opus 5.5 | $0.00926 | $0.00926 |
| Sonnet 5.5 | $0.00463 | $0.00463 |
| Haiku 4.5 | $0.00231 | $0.00231 |
Grade A, and why
pocmap 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PocMap Conventions
PocMap is an AI-friendly CVE / PoC / exploit-discovery toolkit (CLI + MCP server + Python API).
This file covers how to develop the project. For how AI agents consume the MCP tools, see
.claude/skills/pocmap-agent/references/mcp_tools.md (canonical MCP/agent guide; also
.claude/skills/pocmap-agent/SKILL.md). AGENTS.md holds general agent guidelines, not the
MCP tool contract. For full usage/API docs, see README.md.
Knowledge Freshness & Research Preferences (IMPORTANT!)
Do not rely solely on your internal knowledge or training data when making implementation decisions. Your memory is frequently outdated.
Before implementing anything non-trivial (especially integrations, tools, SDKs, platforms, AI agents, or architectural patterns):
-
Actively look up the latest official documentation, release notes, changelogs, and recommended approaches.
-
Check whether newer versions, official solutions, or better patterns already exist that would change how the task should be approached.
-
Prefer using current best practices and existing tools over rebuilding something from scratch based on older knowledge.
-
If there is any uncertainty about the current recommended way to do something, ask clarifying questions instead of defaulting to what you remember.
Why this matters:
Defaulting to internal knowledge often leads to outdated implementations. For example, an agent might implement an older pattern for something like MCP or an AI agent integration simply because that is what it “knows,” without checking whether a newer release, official SDK, or simpler approach has become available. Always verify first.
Commands
- Install (PyPI):
pip install "pocmap[server]"(omit[server]for CLI-only) - Install (dev clone):
pip install -e ".[server,dev]"(pytest, mypy, ruff + the MCP SDK); docs site:pip install -e ".[server,docs]"thenpython scripts/generate_mcp_docs.py --check && mkdocs build --strict - Run CLI:
pocmap lookup CVE-2021-44228(orpython -m pocmap ...); full command list:python -m pocmap --help - Lint:
ruff check src/pocmap - Type check:
mypy src(strict mode is on inpyproject.toml) - Run MCP server:
uvx --from 'pocmap[server]' pocmap-mcpor installedpocmap-mcp/python -m pocmap.mcp_server(add--transport sse|http,--host,--port,--debug) - Tests:
pytestworks and is offline by default; see Testing below.
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.
- 1mo ago First seen · 115 lines · 2,315 tokens per session scan A ef344a33d0ee
pocmap CLAUDE.md is an instructions file published in the GitHub repository zebbern/pocmap (6 stars, last pushed 2mo ago), licensed MIT. It adds 2,315 tokens to every session, about $0.0093 per session on Opus 5.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
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.