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 skills/kryptobaseddev/cleo/ct-codebase-mappernpx skills add kryptobaseddev/cleo --skill ct-codebase-mappergit clone --depth 1 https://github.com/kryptobaseddev/cleoWrote 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/skills/kryptobaseddev/cleo/ct-codebase-mapper)<a href="https://agentmods.dev/skills/kryptobaseddev/cleo/ct-codebase-mapper"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/ct-codebase-mapper.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.00580 |
| Opus 5 | $0.00017 | $0.00290 |
| Sonnet 5 | $0.00007 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
ct-codebase-mapper 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.
What it actually says
Codebase Mapper
Structured codebase analysis for autonomous agent understanding.
Quick Start
| Goal | Command | Cost |
|---|---|---|
| Quick analysis | query admin map |
~500 tokens |
| Deep analysis + store | mutate admin map |
~800 tokens |
| Focus on one area | query admin map {focus: "concerns"} |
~300 tokens |
| CLI | cleo map / cleo map --store |
— |
Progressive Disclosure
Tier 0: Quick Analysis
cleo map
Returns structured CodebaseMapResult with stack, architecture, structure, conventions, testing, integrations, and concerns.
Tier 1: Store to Brain
cleo map --store
Same analysis, but stores patterns, learnings, and observations to brain.db. Tagged with source: 'codebase-map' for filtering.
Tier 2: Focused Analysis
cleo map --focus concerns
Focus areas: stack, architecture, structure, conventions, testing, integrations, concerns.
When to Use
- New project onboarding: Run
cleo map --storeto build brain.db context - Brownfield init:
cleo init --map-codebaseruns analysis during initialization - Before epic planning: Understand project structure before decomposing work
- Tech debt assessment:
query admin map {focus: "concerns"}for TODOs and large files
Output Structure
{
projectContext: ProjectContext, // From detectProjectType()
stack: StackAnalysis, // Languages, frameworks, deps
architecture: ArchAnalysis, // Layers, entry points, patterns
structure: StructureAnalysis, // Directory tree with annotations
conventions: ConventionAnalysis,// Naming, linting, formatting
testing: TestingAnalysis, // Framework, patterns, coverage
integrations: IntegrationAnalysis, // APIs, DBs, CI/CD
concerns: ConcernAnalysis, // TODOs, large files, complexity
analyzedAt: string
}
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 · 83 lines · 34 tokens per session scan A 91025e70bcef
ct-codebase-mapper is a skill published in the GitHub repository kryptobaseddev/cleo (160 stars, last pushed 15d ago), licensed MIT. It adds 34 tokens to every session and 580 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…