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.
git clone --depth 1 https://github.com/eddiebelaval/squireWrote 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/commands/eddiebelaval/squire/codebase-map)<a href="https://agentmods.dev/commands/eddiebelaval/squire/codebase-map"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/codebase-map/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/commands/eddiebelaval/squire/codebase-map"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/codebase-map.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.00000 | $0.02771 |
| Opus 5.5 | $0.00000 | $0.01108 |
| Sonnet 5.5 | $0.00000 | $0.00554 |
| Haiku 4.5 | $0.00000 | $0.00277 |
Grade A, and why
codebase-map 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/codebase-map - Interactive Codebase Health Visualization
Generate an interactive HTML codebase map that shows project health, architecture, protocol completion, and launch readiness. This is the standard artifact format for tracking block-level build progress across any project.
Arguments
/codebase-map [project-name] — Generates a codebase map for the specified project. If no argument, infer from current working directory.
What It Produces
A single self-contained HTML file with 6 tabs:
| Tab | Purpose |
|---|---|
| Overview | Project health dashboard — total blocks, green/yellow/planned counts, protocol completion bar, key highlights |
| Map | Interactive SVG architecture diagram with animated flow lines, traveling dots, hover-to-trace, completion bar (5 phases), stat counters, data flow description, database schema, file map, pre-flight launch checklist |
| Blocks | All blocks grouped by layer (Frontend, Backend, Database, External) with protocol dots (C/W/I/T/D) |
| Connections | SVG connection diagram + full connection list with flow status badges |
| Tasks | Auto-generated tasks grouped by priority (high/medium/low) |
| Assessment | Senior dev review with wins, fixes, next steps, copy-paste prompts, persistent checkboxes |
Data Model
Every codebase map is driven by three arrays embedded in the HTML:
BLOCKS
{
id: 'session', // Unique identifier
name: 'Session View', // Display name
layer: 'frontend', // frontend | backend | database | integration
phase: 'built', // planned | building | built
status: 'green', // green (4-5/5 protocol) | yellow (2-3/5) | none (0-1/5)
protocol: {
created: true, // Files exist
wired: true, // Connections declared (imports, API calls)
integrated: true, // Data flows end-to-end
tested: true, // Has test coverage
documented: true // Has docs/comments
}
}
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 · 287 lines · 0 tokens per session scan A 7dcfccab2a7c
codebase-map is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,771 tokens. 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 commands, from other repositories
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
paul:help
Show available PAUL commands and usage guide.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
architect
Generate architecture.md with system design decisions from foundation documents.
analizar-sesiones
Analizar sesiones de Claude en el equipo para extraer patrones de uso y generar recomendaciones de habilidades, plugins, agentes y reglas.
iniciar
Inicializar Don Cheli en un proyecto nuevo o existente.