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 w95/awesome-claude-corporate-skills --skill competitive-analysisgit clone --depth 1 https://github.com/w95/awesome-claude-corporate-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/w95/awesome-claude-corporate-skills/competitive-analysis)<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/competitive-analysis"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/competitive-analysis/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/competitive-analysis"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/competitive-analysis.svg" alt="Reviewed on agentmods" width="80" 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.00063 | $0.03786 |
| Opus 5 | $0.00032 | $0.01893 |
| Sonnet 5 | $0.00013 | $0.00757 |
| Haiku 4.5 | $0.00006 | $0.00379 |
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 12d 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
89% identical to competitive-analysis — 5 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Landscape Mapping
CRITICAL STANDARDS - APPLY TO EVERY ANALYSIS
Source File Primacy
When source files (Excel/CSV) are provided:
- Extract values DIRECTLY — Do not perform your own calculations; use the numbers as they appear
- Maintain consistency — When the same metric appears in multiple places, ensure identical values throughout
- Verify calculations — If the prompt asks you to calculate something, verify your result matches related data in the source
- Round only as shown — Use the same decimal precision as the source file
Prompt Fidelity
When the prompt specifies exact requirements, follow them verbatim:
Slide Titles & Section Names:
- If prompt says
"Overview and Competitive Scope" slide— use EXACTLY that title, not a paraphrase - If prompt says
within the "Segment Mix" section— use EXACTLY "Segment Mix" as the section header - Never substitute with creative alternatives (e.g., don't use "FY2024 Segment Contribution Analysis" when "Overview and Competitive Scope" was specified)
Chart vs Table:
- If prompt says
embedded chart— create an actual PowerPoint chart object, NOT a table - If prompt says
data labels must display— these go on chart elements (bars, slices, lines), not table cells - Tables and charts are NOT interchangeable — use exactly what's specified
Complete Data Series:
- If prompt lists 7 competitors, include ALL 7 — not 5 or 6
- If prompt shows data for years 2015-2025, include ALL years — not a subset
- If prompt specifies 6 series in a chart (Uber, Lyft, DiDi, Bolt, Grab, Gojek), include ALL 6 — not 4
Exact Values & Phrasing:
- If prompt says
Revenue: $43.98B (+18% YoY)— display exactly that format - If prompt says
surpasses DoorDash 4:1, Lyft 8:1— use those exact ratios, not "7.6x Lyft" - If prompt gives specific percentages (e.g., "Uber 30%, DiDi 35%"), use exactly those numbers
When in doubt: Re-read the prompt. If it specifies something explicitly, that's not a suggestion — it's a requirement.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 360 lines · 63 tokens per session scan A 1b32439dd6f2
competitive-analysis is a skill published in the GitHub repository w95/awesome-claude-corporate-skills (198 stars, last pushed 6mo ago), licensed MIT. It adds 63 tokens to every session and 3,786 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to competitive-analysis, differing in 5 lines, and is treated as a copy.
Other skills, from other repositories
design-por-referencia
Use when a landing page, marketing site, or hero section looks generic/AI-made ("cara de vibe coding") and needs a $10k-agency-level redesign, or when building a new landing from scratch. Triggers - "o site ficou com cara de IA", "quero uma landing premium", "redesenha a landing", "faz o site baseado em [site de…
lighthouse-95
Use when a website must score 95+ in every Lighthouse category (Performance, Accessibility, Best Practices, SEO), when scores are stuck below target, or when diagnosing poor FCP, LCP, TBT, or CLS on a deployed site.
seo-validate
SEO validator: meta/OG, Schema.org, hreflang, Core Web Vitals, crawlability. Triggers: SEO, meta tags, Schema.org, hreflang, LCP, INP, CLS, Core Web Vitals, sitemap, crawlability.
debug
Systematic debugging via logs, health checks, hypothesis-driven investigation. Triggers: debug, error, trace root cause, fix bug, reproduce symptom, investigation.
research-mastery
Hierarchical retrieval: KB → MCP/Context7 → web. Triggers: research, fact-check, verify, synthesize, cross-reference, multi-source, cite sources.
pr
Creates GitHub PR after pre-flight checks (lint/typecheck/tests), structured summary from commits. Triggers: pr, pull request, create PR, ready to merge.