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-research)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/biz-research"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/biz-research/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/christopherlouet/claude-base/biz-research"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/biz-research.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.00299 |
| Opus 5 | $0.00000 | $0.00150 |
| Sonnet 5 | $0.00000 | $0.00060 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
biz-research 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 9d 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.
What it actually says
RESEARCH Agent
Conducts structured user research to inform product decisions.
Research topic
$ARGUMENTS
Objective
Conduct methodical user research (framing, collection, analysis, reporting) that generates actionable insights to improve the product.
Workflow
- Frame the research (questions, hypotheses, success criteria)
- Choose the methods (interviews, user testing, surveys, analytics)
- Recruit the participants (criteria, quotas, channels, incentives)
- Conduct the interviews (structured guide, open-ended questions)
- Analyze the data (coding, themes, affinity mapping)
- Report the insights (findings, recommendations, open questions)
- Document in the insights repository
Expected output
Research report
- Executive summary, key findings, recommendations
- Methodology and limitations
- Detailed findings with evidence (verbatims)
- Short/medium-term recommendations
Related agents
| Agent | When to use it |
|---|---|
/biz:biz-personas |
Create/update personas |
/growth:growth-analytics |
Complement with quantitative data |
/growth:growth-ab-test |
Validate hypotheses |
/growth:growth-cro |
Improve the onboarding/conversion journey |
IMPORTANT: Research must answer precise questions, not just "understand better".
YOU MUST recruit participants representative of your target users.
NEVER conduct research without an action plan for the results.
Think hard about potential biases in recruitment and questions.
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.
- 9d ago First seen · 48 lines · 0 tokens per session scan A 1bbdb4e4d1fe
biz-research is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 299 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.
context-stats
Display context window usage and token statistics.
migrate
Generate and manage database migrations.
scaffold
Scaffold project components from templates.
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.