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/brainbytes-dev/everything-claude-marketing/personagit clone --depth 1 https://github.com/brainbytes-dev/everything-claude-marketingWhat 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.00027 | $0.01896 |
| Opus 5 | $0.00014 | $0.00948 |
| Sonnet 5 | $0.00005 | $0.00379 |
| Haiku 4.5 | $0.00003 | $0.00190 |
Grade A, and why
persona 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/persona
Create a detailed, actionable buyer persona grounded in the Jobs-to-be-Done framework — not a fictional character sheet, but a strategic tool for decision-making.
What This Command Does
This command builds a comprehensive buyer persona that goes beyond surface-level demographics. Using the Jobs-to-be-Done (JTBD) framework, it identifies the functional, emotional, and social jobs your target buyer is trying to accomplish, along with the pain points, desired outcomes, and decision criteria that drive their purchasing behavior. The persona includes demographic and firmographic context, psychographic insights, media consumption habits, objection patterns, and a mapped buying journey with key influence points. The result is a living document that marketing, sales, product, and customer success teams can all use.
When to Use
- Launching a new product and defining your ideal customer profile
- Entering a new market segment or vertical
- Refining messaging that is not resonating with your target audience
- Aligning marketing and sales on who you are actually selling to
- Building content strategy and need to understand audience deeply
- Preparing for a brand refresh or repositioning
- Onboarding new marketing or sales team members who need customer context
- Creating ad targeting criteria and lookalike audiences
How It Works
- Gathers inputs — Asks about your product, market, existing customer data, and any hypotheses about your target buyer
- Defines the JTBD — Identifies the primary functional, emotional, and social jobs the buyer is hiring your product to do
- Builds demographics — Establishes role, seniority, company size, industry, and firmographic context
- Maps psychographics — Defines motivations, frustrations, values, and decision-making style
- Identifies pain points — Catalogs specific problems the buyer faces and how they currently solve them
- Charts the buying journey — Maps the stages from problem recognition through vendor selection
- Documents objections — Lists common objections and the underlying concerns behind them
- Profiles media habits — Identifies where the buyer consumes information, who they trust, and how they evaluate solutions
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 · 183 lines · 27 tokens per session scan A 63932e0dd554
persona is a command published in the GitHub repository brainbytes-dev/everything-claude-marketing (5 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 1,896 once invoked, about $0.0001 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.