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 commands/kesteva/soloflow/map-codebasegit clone --depth 1 https://github.com/kesteva/soloflowWhat 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.05155 |
| Opus 5 | $0.00017 | $0.02577 |
| Sonnet 5 | $0.00007 | $0.01031 |
| Haiku 4.5 | $0.00003 | $0.00515 |
Grade A, and why
map-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 2d 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 — 423 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/soloflow:map-codebase
Generates the three "shared-context" docs every SoloFlow agent expects to load
on entry to a new session: a project CLAUDE.md, an ARCHITECTURE.md, and a
CODE-PATTERNS.md. Additive and idempotent — only missing artifacts are
created; existing files are never overwritten or rewritten by this command.
This is the bootstrap counterpart to /soloflow:compound's C-bucket: compound
extends these files with sprint-derived learnings, but it assumes they already
exist. Run this once at project setup (init prompts you), and re-run any time
a missing artifact is added back to the project (e.g., a new subdirectory that
deserves its own scoped CLAUDE.md).
The command is read-mostly: it surveys the codebase via Glob/Grep/Read, asks the user to confirm what to generate, and writes the chosen artifacts.
Step 0: Sanity check
- Run
pwdvia Bash to capture the project root (used in commit messages and reported paths). - Run
git rev-parse --is-inside-work-treevia Bash. Capture whether the project is in a git repo (is_git). Not being in a repo is fine — the command still writes the artifacts, just skips Step 5's commit.
Step 0.4: Parse flags
Scan $ARGUMENTS for the three skip flags and build a skip_set (a set of artifact names this run will not generate, even if missing):
--skip-claudemd→ add"CLAUDE.md"toskip_set.--skip-architecture→ add"ARCHITECTURE.md"toskip_set.--skip-codepatterns→ add"CODE-PATTERNS.md"toskip_set.
Match flags by exact string; treat any token in $ARGUMENTS that begins with --skip- but is not one of the three above as an error: print map-codebase: unknown flag "{token}". Recognized flags: --skip-claudemd, --skip-architecture, --skip-codepatterns. and stop. Order is irrelevant; duplicates are tolerated.
If skip_set contains all three names, print map-codebase: all three artifacts skipped via flags — nothing to do. and stop.
If skip_set is non-empty, print one line summarizing what was excluded: Skipping (via flag): {comma-joined names from skip_set}. This makes the suppression visible in the run log.
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.
- 2d ago First seen · 423 lines · 0 tokens per session scan A fd8347331f7a
map-codebase is a command published in the GitHub repository kesteva/soloflow (41 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 5,155 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.