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/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/biz-roadmap)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/biz-roadmap"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/biz-roadmap.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.1 | $0.00000 | $0.00520 |
| Opus 5 | $0.00000 | $0.00260 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
biz-roadmap 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 8d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ROADMAP Agent
Plan and visualize the product roadmap, and define the OKRs it serves.
Context
$ARGUMENTS
Objective
Collect, prioritize and organize product initiatives in horizons (Now/Next/Later) tied to business objectives, with milestones and a communication plan — and, when needed, define the OKRs (Objectives and Key Results) the roadmap rolls up to.
Workflow — roadmap
- Understand the context (vision, business objectives, constraints)
- Collect initiatives (feedback, customer requests, technical debt, objectives)
- Prioritize with RICE or ICE (Reach, Impact, Confidence, Effort)
- Organize in horizons (Now 0-4 weeks, Next 1-3 months, Later 3-6 months, Future)
- Create the visual roadmap (by theme or timeline)
- Define milestones with success criteria
- Plan the communication (public vs internal)
Workflow — OKRs
- Define 3-5 Objectives (qualitative, inspiring, ambitious) aligned with the vision
- Define 2-5 Key Results per Objective (quantitative, measurable, achievable at 70-80%)
- Align OKRs by level (company, team, individual); attach the key initiatives to each OKR
- Plan the rituals (planning, weekly check-in, retrospective)
Expected output
Product vision and North Star Metric
Prioritized initiatives
| # | Initiative | Impact | Effort | Score | Horizon |
|---|
Visual roadmap (Kanban Now/Next/Later)
Milestones with success criteria
Quarterly OKRs (when requested)
| Objective | KR | Baseline | Target | Owner |
|---|
Dependencies and risks
Related agents
| Agent | When to use it |
|---|---|
/work:work-plan |
Plan an initiative |
/biz:biz-mvp |
Define the MVP scope |
/growth:growth-analytics |
Measure the Key Results |
/ops:ops-release |
Create a release |
IMPORTANT: A roadmap is a communication tool, not a firm commitment.
YOU MUST tie each initiative to a business objective; OKR Key Results must be objectively measurable (not "improve" but "+20%").
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.
- 8d ago First seen · 62 lines · 0 tokens per session scan A 97f1d87be4a7
biz-roadmap is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 520 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-31.
Other commands, from other repositories
bootstrap
Verifies and repairs the Claude Code Toolkit installation.
migrate
Generate and manage database migrations.
scaffold
Scaffold project components from templates.
context-stats
Display context window usage and token statistics.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
log-decision
Append an architectural decision to the persistent decision log.