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 skills/brainbytes-dev/everything-claude-marketing/competitive-positioningnpx skills add brainbytes-dev/everything-claude-marketing --skill competitive-positioninggit 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/skills/brainbytes-dev/everything-claude-marketing/competitive-positioning)<a href="https://agentmods.dev/skills/brainbytes-dev/everything-claude-marketing/competitive-positioning"><img src="https://agentmods.dev/badge/skills/brainbytes-dev/everything-claude-marketing/competitive-positioning.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 | $0.00023 | $0.02014 |
| Opus 5 | $0.00012 | $0.01007 |
| Sonnet 5 | $0.00005 | $0.00403 |
| Haiku 4.5 | $0.00002 | $0.00201 |
Grade A, and why
competitive-positioning 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.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Positioning
When to Activate
- Entering a new market and need to understand the competitive landscape
- A new competitor has emerged and is taking market share
- Sales team is losing deals to specific competitors and needs better positioning
- Refreshing competitive intelligence for annual planning
- Building sales enablement materials (battlecards, objection handling)
- Pricing decisions that require competitive context
- Evaluating potential partnerships or acquisitions in the competitive space
First Questions
- Who do your customers consider as alternatives? (Not who you think — who they actually compare you to.)
- Why do you win deals, and why do you lose them?
- What do customers say about competitors in reviews, forums, and sales calls?
- Which competitors are growing fastest, and why?
- Where do you overlap with competitors, and where are you genuinely different?
- Are there non-obvious competitors (spreadsheets, manual processes, "do nothing")?
- What competitive intelligence do you already have, and how current is it?
Competitive Landscape Mapping
Step 1: Identify Competitors
Map competitors in three tiers:
Direct competitors — Same product category, same target customer. They solve the same problem the same way.
Indirect competitors — Different product category, same customer need. They solve the same problem a different way.
Substitute competitors — What customers use instead of any purpose-built solution. Often the real competition (spreadsheets, email, manual processes, hiring an intern).
Step 2: Build Competitor Profiles
For each significant competitor, document:
Company: [Name]
Website: [URL]
Founded: [Year]
Funding/Revenue: [If available]
Headcount: [Approximate]
Target Market: [Who they sell to]
Core Product: [What they sell]
Positioning: [How they describe themselves — use their own words]
Key Strengths: [What they do well]
Key Weaknesses: [Where they fall short]
Pricing Model: [How they charge]
Recent Moves: [Product launches, funding, pivots, hires in last 12 months]
Win Rate Against: [% of deals won/lost vs this competitor, if known]
Common Objections: [What customers say when considering them over you]
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 · 223 lines · 23 tokens per session scan A b8331739883d
competitive-positioning is a skill 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 2,014 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…