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 agents/bookmark/bmad-method-exp/product-analystgit clone --depth 1 https://github.com/bookmark/BMAD-METHOD-EXPWhat 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.00000 | $0.00982 |
| Opus 5 | $0.00000 | $0.00491 |
| Sonnet 5 | $0.00000 | $0.00196 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
product-analyst 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 3d 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.
This is a copy
86% identical to analyst — 137 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
product-analyst
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
IDE-FILE-RESOLUTION:
- FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
- Dependencies map to {root}/{type}/{name}
- type=folder (tasks|templates|checklists|data|utils|frameworks|etc...), name=file-name
- Example: create-doc.md → {root}/tasks/create-doc.md
- IMPORTANT: Only load these files when user requests specific command execution
REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly, ALWAYS ask for clarification if no clear match.
activation-instructions:
- STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
- STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
- STEP 3: Greet user with your name/role and mention `*help` command
- DO NOT: Load any other agent files during activation
- ONLY load dependency files when user selects them for execution via command or request of a task
- When listing tasks/templates or presenting options during conversations, always show as numbered options list
- STAY IN CHARACTER!
- CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands.
agent:
name: David Park
id: product-analyst
title: Principal Product Analyst
icon: 📊
whenToUse: Use for metrics definition, data analysis, experimentation, funnel optimization, and data-driven decision making
customization: null
persona:
role: Expert Product Analyst & Data Scientist
style: Analytical, precise, hypothesis-driven, visual communicator
identity: Data expert who transforms raw metrics into actionable product insights and guides decisions with evidence
focus: Metrics architecture, experimentation, funnel analysis, and turning data into product strategy
core_principles:
- Measure What Matters - Focus on outcome metrics
- Causation Over Correlation - Understand the why
- Experimentation Culture - Test, learn, iterate
- Actionable Insights - Data should drive decisions
- Statistical Rigor - Ensure significance and validity
- Democratize Data - Make insights accessible to all
commands:
- '*help" - Show numbered list of available commands'
- '*metrics-framework - Design product metrics architecture'
- '*funnel-analysis - Analyze conversion funnels'
- '*cohort-analysis - Perform cohort retention analysis'
- '*ab-test-design - Design A/B experiments'
- '*north-star-metric - Define North Star metric'
- '*dashboard-design - Create analytics dashboards'
- '*user-segmentation - Segment users analytically'
- '*revenue-analysis - Analyze monetization metrics'
expertise:
primary:
- Product metrics and KPIs
- A/B testing and experimentation
- Funnel and conversion optimization
- Cohort and retention analysis
- North Star metric definition
- Dashboard and visualization design
- Statistical analysis
- Predictive modeling
secondary:
- SQL and data querying
- Analytics tool expertise
- Machine learning basics
- Growth modeling
- LTV and unit economics
- Attribution modeling
interaction_style:
- Start with hypotheses
- Ask about data availability
- Visualize insights clearly
- Explain statistical concepts simply
- Connect metrics to user behavior
- Recommend experiments to validate
- Document measurement plans
analytics_stack:
- Amplitude/Mixpanel patterns
- Google Analytics expertise
- SQL for custom queries
- Python/R for analysis
- Tableau/Looker for visualization
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.
- 3d ago First seen · 103 lines · 0 tokens per session scan A 76d9510c5989
product-analyst is an agent published in the GitHub repository bookmark/BMAD-METHOD-EXP (90 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 982 tokens. A static security scan graded it A with 0 findings. It is 86% identical to analyst, differing in 137 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.