scan-codebase

A codebase command that scans a project and produces a map of its files, folders, languages, entry points, configuration, and broad architecture. It skips common generated or dependency folders such as node_modules and build output.

In plain words
What is it for?
Use it when starting work in an unknown repository or documenting its structure. The report includes a file tree, file-type statistics, language breakdown, project type, and likely architecture.
Why use it?
It gives a quick picture of an unfamiliar project without requiring you to inspect every folder yourself. This makes it easier to find important areas and understand how the project is organized.

Command

Install

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.

agentmods
npx agentmods add commands/rubencodeforges/codeforges-claude-plugin/scan-codebase
Clone the repo
git clone --depth 1 https://github.com/rubenCodeforges/codeforges-claude-plugin
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 154 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00154
Opus 5 $0.00006 $0.00077
Sonnet 5 $0.00002 $0.00031
Haiku 4.5 $0.00001 $0.00015

Measured yesterday against content hash fe121a1b961a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

scan-codebase 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.

commands/scan-codebase.md · 24 lines

What it actually says

Perform a comprehensive codebase scan by:

  1. Use bash tools to scan the project structure respecting .gitignore

  2. Exclude common directories: node_modules, .git, pycache, venv, dist, build

  3. Generate a hierarchical file tree

  4. Provide statistics:

    • Total files by type
    • Directory structure overview
    • Language breakdown
    • Key directories identified
  5. Identify patterns:

    • Project type (React, Django, Go, etc.)
    • Architecture style (MVC, microservices, etc.)
    • Key entry points
    • Configuration files

Present results as organized report with tree structure and statistics.

Changes

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.

  1. yesterday First seen · 24 lines · 12 tokens per session scan A fe121a1b961a

Subscribe to this mod's changes

scan-codebase is a command published in the GitHub repository rubenCodeforges/codeforges-claude-plugin (2 stars, last pushed 9mo ago), licensed MIT. It adds 12 tokens to every session and 154 once invoked, 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.