scan

scan is a skill for Claude Code from SienkLogic/plan-build-run. It costs 18 tokens per session (3,097 once invoked), scanned A, original, MIT.

A codebase analysis tool that maps an existing software project’s structure, architecture, conventions, and areas of concern.

In plain words
What is it for?
Use it to inspect how a project is organized, how its parts fit together, and where potential problems or inconsistencies may be.
Why use it?
It helps developers understand an unfamiliar or older codebase before making changes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; names the AskUserQuestion tool; mentions Claude Code.

Part of the pbr plugin — 44 skills, 71 commands, 18 agents, 3 hooks shipped together

Good fit Use it to inspect how a project is organized, how its parts fit together, and where potential problems or inconsistencies may be.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sienklogic/plan-build-run/scan
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.

Any agent
npx skills add SienkLogic/plan-build-run --skill scan
Clone the repo
git clone --depth 1 https://github.com/SienkLogic/plan-build-run

Made for: Claude Code.

Or install pbr, the plugin that ships this one along with the rest of its 44 skills, 71 commands, 18 agents, 3 hooks.

Wrote 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.

agentmods badge for scan

README.md
[![agentmods](https://agentmods.dev/badge/skills/sienklogic/plan-build-run/scan/github.svg)](https://agentmods.dev/skills/sienklogic/plan-build-run/scan)
Your own site
<a href="https://agentmods.dev/skills/sienklogic/plan-build-run/scan"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/scan/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.

agentmods 80×15 button for scan

Your own site · 80×15
<a href="https://agentmods.dev/skills/sienklogic/plan-build-run/scan"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,097 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00018 $0.03097
Opus 5 $0.00009 $0.01548
Sonnet 5 $0.00004 $0.00619
Haiku 4.5 $0.00002 $0.00310

Measured 6d ago against content hash f1e6f3358afb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

scan 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 6d 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.

plugins/pbr/skills/scan/SKILL.md · 353 lines

How it starts

The opening of the file, as written. The whole thing — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.

STOP — DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Using the Read tool on this SKILL.md file wastes ~7,600 tokens. Begin executing Step 1 immediately.

Step 0 — Immediate Output

Before ANY tool calls, display this banner:

╔══════════════════════════════════════════════════════════════╗
║  PLAN-BUILD-RUN ► SCANNING CODEBASE                          ║
╚══════════════════════════════════════════════════════════════╝

Then proceed to Step 1.

/pbr:map-codebase — Codebase Analysis

You are running the scan skill. Your job is to analyze an existing codebase and produce a comprehensive map of its structure, architecture, conventions, and concerns. This is the entry point for brownfield projects — codebases that already have code before Plan-Build-Run is introduced.

This skill spawns 4 parallel Task(subagent_type: "pbr:codebase-mapper") agents for analysis.


Context Budget

Reference: skills/shared/context-budget.md for the universal orchestrator rules. Reference: skills/shared/agent-type-resolution.md for agent type fallback when spawning Task() subagents.

Additionally for this skill:

  • Never analyze the codebase yourself — delegate ALL analysis to the 4 parallel codebase-mapper subagents
  • Minimize reading mapper outputs — read only frontmatter or first 20 lines of each output document
  • Delegate all file reading, pattern analysis, and architecture mapping to the codebase-mapper subagents

Core Principle

Understand before you change. Scanning a codebase is about building a mental model of what exists. Every file produced by this skill becomes context that the planner and executor use to make informed decisions. Accuracy matters more than speed.


Flow

Step 1: Load Init Context

Run the CLI to get scan metadata:

pbr-tools init map-codebase

Extract from init JSON: mapper_model, commit_docs, codebase_dir, existing_maps, has_maps, codebase_dir_exists, intel_enabled, has_intel_dir, depth_profile.

Read the full file on GitHub · 353 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 6d ago First seen · 353 lines · 18 tokens per session scan A f1e6f3358afb

Subscribe to this mod's changes

scan is a skill published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 3,097 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-09-03.