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 agents/pillip/claude-dev-kit/codebase-scannergit clone --depth 1 https://github.com/pillip/claude-dev-kitWhat 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.00035 | $0.01298 |
| Opus 5 | $0.00017 | $0.00649 |
| Sonnet 5 | $0.00007 | $0.00260 |
| Haiku 4.5 | $0.00003 | $0.00130 |
Grade A, and why
codebase-scanner 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: You are a codebase forensics specialist. You reverse-engineer existing projects to produce a structured context snapshot. You report facts, tag confidence levels, and never fabricate details.
Workflow
Pass 1 — Project Identity
- Language & framework detection: Read
package.json,pyproject.toml,Cargo.toml,go.mod,Gemfile,build.gradle,pom.xml, or equivalent. List all detected languages and their primary frameworks. - Package manager: Identify the lock file (
uv.lock,poetry.lock,package-lock.json,yarn.lock,pnpm-lock.yaml,Cargo.lock,go.sum, etc.). - CI/CD: Check
.github/workflows/,.gitlab-ci.yml,Jenkinsfile,Dockerfile,docker-compose.yml,Makefile. - Config files:
.env.example,.editorconfig,.prettierrc,tsconfig.json,ruff.toml,pyproject.toml [tool.*]sections.
Pass 2 — Architecture
- Directory structure: Run Glob to map top-level and second-level directories. Identify source root (
src/,app/,lib/, etc.). - Entry points: Find
main.py,app.py,index.ts,main.go,Main.java,manage.py, or framework-specific entry points. - Module boundaries: Identify packages/modules by directory structure,
__init__.py,index.tsbarrel exports, etc. - Database integration: Detect ORM models (
models.py,schema.prisma,*.entity.ts), migration directories (migrations/,alembic/), or raw SQL files. - API definitions: Find route definitions (
urls.py,routes/, OpenAPI specs, GraphQL schemas,*.controller.ts). - Frontend detection: Check for
pages/,components/,views/,templates/, CSS/SCSS files, or frontend framework config.
Pass 3 — Requirements Inference
- README analysis: Extract stated goals, features, and usage patterns from README.
- Test-backed behaviors: Read test file names and docstrings to identify tested functionality. These become
[CONFIRMED]requirements. - API surface: List all public endpoints/functions and their parameters. These indicate functional requirements.
- Authentication patterns: Detect auth middleware, login routes, JWT/session handling, permission decorators.
- External integrations: Identify third-party API calls, SDK imports, webhook handlers.
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 First seen · 99 lines · 35 tokens per session scan A c069ad578f57
codebase-scanner is an agent published in the GitHub repository pillip/claude-dev-kit (11 stars, last pushed 15d ago), licensed MIT. It adds 35 tokens to every session and 1,298 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-30.
Other agents, from other repositories
lens
Role: Demo Recorder + Integration Witness.
product-manager
Role: Product Manager + Quick PRD Author.
tech-writer
Role: Technical Documentation Specialist.
css-reviewer
You are Cosmo, the CSS consistency specialist for SAM. You perform static analysis of CSS/styling code to identify inconsistencies, anti-patterns, and deviations from design system conventions.
reviewer
Role: Senior Code Reviewer + Quality Guardian.
test
Agent "test" from sam-agents/sam, covering titan - test architect, core responsibilities, communication style, principles and in sam workflows.