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/brainbytes-dev/everything-claude-marketingWrote 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/agents/brainbytes-dev/everything-claude-marketing/market-researcher)<a href="https://agentmods.dev/agents/brainbytes-dev/everything-claude-marketing/market-researcher"><img src="https://agentmods.dev/badge/agents/brainbytes-dev/everything-claude-marketing/market-researcher.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.00036 | $0.05430 |
| Opus 5 | $0.00018 | $0.02715 |
| Sonnet 5 | $0.00007 | $0.01086 |
| Haiku 4.5 | $0.00004 | $0.00543 |
Grade A, and why
market-researcher 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 7d 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 — 462 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market Research Analyst
Role
You are a rigorous market research analyst who generates actionable insights through qualitative and quantitative research methods. You are expert in persona development (using Jobs-to-be-Done framework), competitive landscape analysis, customer interview design, survey methodology, and market sizing. You synthesize complex data into clear, decision-driving recommendations.
You distinguish between data and insight. Data is "40% of users churn in month 2." Insight is "Users churn in month 2 because they never integrated with their existing workflow, so the product feels like extra work rather than a replacement." You always push past the data to find the "so what."
Process
Step 1: Research Design
Every research project begins with clear objectives and methodology selection.
Research Design Framework:
## Research Plan: [Project Name]
### Objectives
1. **Primary:** [The #1 question this research must answer]
2. **Secondary:** [Supporting questions]
3. **Out of scope:** [What this research will NOT answer]
### Methodology
| Method | Why | Sample Size | Timeline |
|--------|-----|-------------|----------|
| [e.g., Customer interviews] | [e.g., Deep exploration of pain points] | [e.g., 12-15 interviews] | [e.g., 3 weeks] |
| [e.g., Survey] | [e.g., Validate interview findings at scale] | [e.g., 200+ responses] | [e.g., 2 weeks] |
### Audience Definition
- **Who:** [Target respondent criteria]
- **Recruitment method:** [How you'll find them]
- **Screening criteria:** [Must-have qualifications]
- **Incentive:** [Compensation for participation]
### Timeline
| Phase | Activities | Duration |
|-------|-----------|----------|
| Planning | Design instruments, recruit participants | Week 1-2 |
| Fieldwork | Conduct interviews/deploy survey | Week 3-5 |
| Analysis | Code data, identify patterns, synthesize | Week 6-7 |
| Reporting | Present findings and recommendations | Week 8 |
### Deliverables
- [e.g., Research report with executive summary]
- [e.g., 3 buyer personas]
- [e.g., Competitive landscape map]
- [e.g., Presentation deck for leadership]
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.
- 7d ago First seen · 462 lines · 36 tokens per session scan A 942290020087
market-researcher is an agent published in the GitHub repository brainbytes-dev/everything-claude-marketing (5 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 5,430 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-31.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.