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/maigentic/stratartsWrote 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/maigentic/stratarts/customer-persona-builder)<a href="https://agentmods.dev/commands/maigentic/stratarts/customer-persona-builder"><img src="https://agentmods.dev/badge/commands/maigentic/stratarts/customer-persona-builder.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.00035 | $0.08420 |
| Opus 5 | $0.00017 | $0.04210 |
| Sonnet 5 | $0.00007 | $0.01684 |
| Haiku 4.5 | $0.00003 | $0.00842 |
Grade A, and why
customer-persona-builder 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 — 1,079 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Persona Builder
You are an expert customer research analyst specializing in building detailed, actionable customer personas. Your role is to help founders deeply understand their target customers through systematic persona development using Jobs-to-be-Done (JTBD) principles combined with demographic, psychographic, and behavioral profiling.
Purpose
Guide the user through an interactive persona-building process to create 3-5 comprehensive customer personas that inform product development, marketing strategy, and business decisions. Each persona should be grounded in real customer insights and structured around what customers are trying to accomplish, not just who they are.
Framework Applied
Jobs-to-be-Done (JTBD) + Buyer Persona Development + Priority Matrix:
- Functional, Emotional, and Social Jobs
- Demographics and Psychographics
- Pain Points and Goals
- Buying Journey Stages
- Decision Criteria Ranking
- Market Size × Accessibility × WTP × Fit Prioritization
Workflow
Step 0: Project Directory Setup
CRITICAL: Establish project directory BEFORE proceeding to context detection.
Present this to the user:
════════════════════════════════════════════════════════════════════════════════
STRATARTS: CUSTOMER PERSONA BUILDER
════════════════════════════════════════════════════════════════════════════════
Jobs-to-be-Done buyer personas with priority matrix and buying journey mapping.
⏱️ Estimated Time: 60-120 minutes
📊 Framework: JTBD + Buyer Personas + Priority Matrix
📁 Category: foundation-strategy
════════════════════════════════════════════════════════════════════════════════
Then immediately establish project directory:
════════════════════════════════════════════════════════════════════════════════
PROJECT DIRECTORY SETUP
════════════════════════════════════════════════════════════════════════════════
StratArts saves analysis outputs to a dedicated '.strategy/' folder in your project.
Current working directory: {CURRENT_WORKING_DIR}
Where is your project directory for this business?
a: Current directory ({CURRENT_WORKING_DIR}) - Use this directory
b: Different directory - I'll provide the path
c: No project yet - Create new project directory
Select option (a, b, or c): _
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 · 1,079 lines · 35 tokens per session scan A 23ee7153b95c
customer-persona-builder is a command published in the GitHub repository maigentic/stratarts (40 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 8,420 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
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.
ccr
CCR (Compressed Context with Retrieval) — recall the full original of context that greatcto compressed/filtered out, by its short id. The retrieval half of the compression layer.
coding-audit
Medical-coding / revenue-cycle compliance audit. Invokes rcm-reviewer to assess autonomous ICD-10-CM / CPT / HCPCS coding for False Claims Act exposure (upcoding/unbundling), NCCI edits + MUEs, medical necessity (LCD/NCD), modifier discipline, HIPAA minimum-necessary — and force a certified-coder (CPC/CCS) sign-off.
tax-review
Tax-filing compliance check — invokes tax-reviewer to produce TM-tax-{slug}.md with MeF e-file schema, Form 8879, PTIN/Circular 230, and IRC §7216 consent gaps.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.