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-personas)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/biz-personas"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/biz-personas/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-personas"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/biz-personas.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.00339 |
| Opus 5 | $0.00000 | $0.00169 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
biz-personas 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 11d 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
PERSONAS Agent
Create detailed and actionable user personas to guide product decisions.
Context
$ARGUMENTS
Goal
Develop 3-5 personas based on real data (analytics, interviews, support) that serve as a reference for design, development, and marketing.
Workflow
- Collect data (analytics, CRM, surveys, interviews, support)
- Identify user patterns and segments
- Create profiles (identity, quote, goals, pain points, behaviors)
- Define Jobs-to-be-done for each persona
- Create the needs vs personas matrix
- Define product, UX, and marketing implications per persona
- Validate with data and the team
Expected output
Personas created (3-5 max)
| Persona | Segment | Main Jobs-to-be-done | LTV | Priority |
|---|
For each persona
- Identity, quote, profile, goals, pain points
- Behaviors, decision process, preferred channels
- Priority features and marketing messages
Related agents
| Agent | When to use it |
|---|---|
/biz:biz-research |
User research |
/biz:biz-competitor |
Market & competitive study |
/biz:biz-mvp |
Define the MVP for a persona |
/growth:growth-cro |
Onboarding/activation journey per persona |
IMPORTANT: Personas must be based on real data, not assumptions.
YOU MUST limit the number of personas (3-5 maximum).
NEVER create a persona without using it in decisions.
Think hard about jobs-to-be-done rather than demographic characteristics.
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.
- 11d ago First seen · 51 lines · 0 tokens per session scan A d29898c76e93
biz-personas 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 339 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.
context-stats
Display context window usage and token statistics.
scaffold
Scaffold project components from templates.
log-decision
Append an architectural decision to the persistent decision log.
update-docs
Scan for recently modified files and update corresponding documentation.