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/competitive-analysisgit 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.00023 | $0.01544 |
| Opus 5 | $0.00012 | $0.00772 |
| Sonnet 5 | $0.00005 | $0.00309 |
| Haiku 4.5 | $0.00002 | $0.00154 |
Grade A, and why
competitive-analysis 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/competitive-analysis
Analyze your competitive landscape across positioning, messaging, features, pricing, and marketing strategy. Get structured output as battlecards, comparison matrices, or strategic landscape maps.
What This Command Does
The /competitive-analysis command produces a thorough competitive assessment that helps you understand where you stand relative to competitors and how to differentiate. It evaluates competitors across multiple dimensions — how they position themselves, what they charge, how they market, and where their strengths and weaknesses lie. The output is structured for direct use in sales enablement, strategy planning, or investor communications.
The command delegates to the market-researcher and product-marketer agents. The market-researcher gathers and structures competitive intelligence while the product-marketer translates findings into positioning and messaging recommendations.
When to Use
- You are entering a new market and need to understand the competitive landscape
- Sales is losing deals to specific competitors and needs battlecards
- You are repositioning your product and need to map competitor positioning
- You want to identify market gaps and differentiation opportunities
- You are preparing investor materials and need competitive landscape context
- You are planning a product launch and need competitive messaging
- You want to audit competitor marketing tactics and channels
How It Works
- Competitor Profiling — Builds structured profiles covering company overview, target market, product capabilities, and market position
- Positioning Analysis — Maps how each competitor positions themselves — their core narrative, taglines, and claimed differentiators
- Feature Comparison — Creates a feature matrix comparing capabilities across competitors
- Pricing Analysis — Documents pricing models, tiers, and strategies
- Marketing Strategy Review — Evaluates competitor channels, content strategy, messaging themes, and campaign approaches
- SWOT Synthesis — Identifies strengths, weaknesses, opportunities, and threats for each competitor relative to you
- Battlecard Creation — Produces sales-ready battlecards with objection handling and win/loss talking points
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 · 173 lines · 23 tokens per session scan A ff0cde5aadef
competitive-analysis is a command published in the GitHub repository brainbytes-dev/everything-claude-marketing (5 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 1,544 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.