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 skills add Vibe-Marketer/plugins-and-skills --skill competitive-analysisgit clone --depth 1 https://github.com/Vibe-Marketer/plugins-and-skillsWrote 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/vibe-marketer/plugins-and-skills/competitive-analysis)<a href="https://agentmods.dev/skills/vibe-marketer/plugins-and-skills/competitive-analysis"><img src="https://agentmods.dev/badge/skills/vibe-marketer/plugins-and-skills/competitive-analysis.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.00043 | $0.01476 |
| Opus 5 | $0.00022 | $0.00738 |
| Sonnet 5 | $0.00009 | $0.00295 |
| Haiku 4.5 | $0.00004 | $0.00148 |
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 8d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<quick_start> Provide:
- Company/competitor name(s) to analyze
- Any URLs (sales pages, websites, marketing materials)
- Your own offer details (for comparison positioning)
I will research and deliver:
- Company overview and value proposition
- Feature/benefit breakdown
- Challenges they solve
- Key differentiating factors
- Direct competitor comparison
- Marketing messaging integration hooks </quick_start>
- Who to analyze? (Company name, product name, or competitor list)
- Available URLs? (Websites, sales pages, VSLs, marketing materials)
- Your offer? (Optional - helps position against competitors)
- Focus areas? (Optional - specific aspects to emphasize)
<critical_rules> NEVER fabricate, assume, or invent information. Use only data directly retrieved from sources. If no data exists for a section, state "No information found" - do not create alternatives. </critical_rules>
- Review all provided URLs and materials first (primary sources)
- Supplement with credible online research (secondary sources)
- Document sources for all claims internally
- Flag any unverifiable claims </research_phase>
<section_company_overview> Company Overview
Provide concise, powerful summary of:
- What the company offers (product, service, program)
- Who it serves (target audience)
- What problem it solves
- How it does this differently than competitors
- Unique mechanism, business model, or proprietary approach
Highlight improvements upon outdated industry norms. </section_company_overview>
<section_whats_included> What's Included
Break down core features/benefits/components:
- List 4-6 most compelling inclusions
- Focus on results-driven benefits, not just features
- Highlight exclusive, proprietary, or unique elements
- Note different tiers if applicable </section_whats_included>
<section_challenges> Challenges Solved
Identify 3+ core pain points addressed:
- Specific problems target audience struggles with
- Impact of these problems on business/life
- How the solution eliminates these pain points
Write from customer's perspective. </section_challenges>
<section_why_choose> Why Choose [Company]?
Highlight competitive advantages:
- How it differs from or beats alternatives
- Unique methodologies, frameworks, tools, support
- Why customers experience better outcomes here </section_why_choose>
<section_differentiators> Key Differentiating Factors
Outline most compelling standout reasons:
- Proprietary systems, AI-driven processes, exclusive access
- Industry-first methodologies, proven frameworks
- Measurable proof points (e.g., "10x response rates") </section_differentiators>
<section_results> Results & Success Stories
Only include if verified from sources.
Showcase real-world success:
- Who benefited (individual, business, industry)
- What problem they faced
- What results they achieved
Format: [Client Name] ([Company]) - Before: [Challenge]. After: [Result]. </section_results>
<section_credibility> Credibility & Social Proof
Only include if verified from sources.
List verifiable achievements:
- Press features (Forbes, Inc., etc.)
- Awards, certifications, rankings
- Customer success metrics, review scores, user base </section_credibility>
<section_competitors> Direct Competitors Analysis
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.
- 8d ago First seen · 222 lines · 43 tokens per session scan A 6518864b59a0
competitive-analysis is a skill published in the GitHub repository Vibe-Marketer/plugins-and-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 43 tokens to every session and 1,476 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…