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 nimadorostkar/Claude-Skills-collection --skill competitive-analysisgit clone --depth 1 https://github.com/nimadorostkar/Claude-Skills-collectionWrote 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/nimadorostkar/claude-skills-collection/competitive-analysis)<a href="https://agentmods.dev/skills/nimadorostkar/claude-skills-collection/competitive-analysis"><img src="https://agentmods.dev/badge/skills/nimadorostkar/claude-skills-collection/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/nimadorostkar/claude-skills-collection/competitive-analysis"><img src="https://agentmods.dev/badge/skills/nimadorostkar/claude-skills-collection/competitive-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.01423 |
| Opus 5 | $0.00016 | $0.00711 |
| Sonnet 5 | $0.00007 | $0.00285 |
| Haiku 4.5 | $0.00003 | $0.00142 |
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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Analysis
Purpose
Understand what competitors actually do, as opposed to what they say, and turn that into a decision. A feature-comparison table is not an analysis; it is a table.
When to Use
- Entering a market or evaluating a new segment.
- Positioning or repositioning a product.
- Pricing decisions.
- Responding to a competitor's move.
Capabilities
- Evidence gathering: product, pricing, positioning, customers.
- Positioning-map construction.
- Pricing and packaging analysis.
- Identifying real differentiation versus claimed differentiation.
- Turning findings into a decision.
Inputs
- The competitors, including the non-obvious ones (the spreadsheet, the incumbent process, doing nothing).
- Your own product and position, honestly assessed.
- The decision this analysis informs.
Outputs
- What each competitor actually offers and to whom.
- Where the market is crowded and where it is not.
- A recommendation that changes something.
Workflow
- Define the competitive set honestly — Including the substitutes. For most B2B products, the largest competitor is a spreadsheet and the status quo, and they are usually left off the list.
- Gather evidence, not marketing — Sign up. Use the product. Read the documentation and the changelog — the changelog tells you what they actually build, as opposed to what they advertise. Read the reviews, especially the three-star ones, which are the honest ones.
- Map the positioning — Two axes that matter to buyers. Where is everyone? The empty quadrant is either an opportunity or a place people have tried and failed.
- Analyze the pricing structure, not the number — What do they charge for, and what does that reveal about who they think their customer is? Per-seat pricing and usage-based pricing target different buyers.
- Separate claimed differentiation from real — Everyone claims to be easy to use and to have great support. What is actually different, and is it something a buyer would pay for?
- Reach a conclusion — An analysis that ends in a table has not concluded anything.
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 · 131 lines · 33 tokens per session scan A e100aab17e74
competitive-analysis is a skill published in the GitHub repository nimadorostkar/Claude-Skills-collection (26 stars, last pushed 24d ago), licensed MIT. It adds 33 tokens to every session and 1,423 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-30.
Other skills, from other repositories
offensive-crypto-attacks
Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…
offensive-c2-frameworks
Command and Control framework deployment, configuration, and operational tradecraft for red team engagements. Covers Cobalt Strike (malleable C2 profiles, Beacon types HTTP/HTTPS/DNS/SMB, Beacon Object Files for in-memory execution, sleep and jitter tuning, named pipe pivoting), Sliver (implant generation across…
offensive-parameter-pollution
HTTP parameter pollution (HPP) checklist: duplicate parameter injection, backend vs frontend parsing differences, WAF bypass via HPP, server-side vs client-side HPP, and practical exploitation patterns. Use when testing web applications for parameter handling flaws.
offensive-wifi
Wireless / 802.11 attack methodology for red team engagements and wireless security assessments. Covers monitor-mode setup, WPA/WPA2-PSK handshake capture and PMKID attacks, WPA3 SAE downgrade and Dragonblood, WPA-Enterprise (EAP) attacks (MSCHAPv2 cracking, EAP-TLS cert theft, evil-twin RADIUS), Karma / Known Beacons…
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
seo
Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".