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/viknesh20-20/claude-code-tool-kit/competitive-analysisnpx skills add viknesh20-20/claude-code-tool-kit --skill competitive-analysisgit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kitWrote 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/viknesh20-20/claude-code-tool-kit/competitive-analysis)<a href="https://agentmods.dev/skills/viknesh20-20/claude-code-tool-kit/competitive-analysis"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/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 | $0.00061 | $0.01661 |
| Opus 5 | $0.00030 | $0.00830 |
| Sonnet 5 | $0.00012 | $0.00332 |
| Haiku 4.5 | $0.00006 | $0.00166 |
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 4d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/competitive-analysis
Before designing a feature in a well-trodden domain, look at how 2–4 mature companies handle it. Faster than inventing. More robust than guessing. Cite every source — never copy product copy or terms-of-service language.
When to use
- Designing billing, dunning, refunds, plan changes, trials, onboarding.
- Designing RBAC, workspace management, team invitations.
- Designing notifications, digests, preferences.
- Designing API rate limits, pagination, idempotency, error formats.
- Designing search, filters, saved views.
- Designing data export, deletion, retention.
- Stuck on UX for a non-obvious flow (account merging, plan downgrade, account recovery).
When NOT to use
- The user's domain is unique enough that competitor patterns won't transfer (specialized B2B verticals, regulated industries with custom workflows).
- The user has already decided. Don't second-guess; just ship.
- Style and copy decisions — those are taste, not pattern.
Operating method
1. Confirm the question
Ask the user, in one round:
- What's the specific problem? Not "how does Stripe work" but "how should we handle a failed-payment retry schedule and the user-facing dunning emails?"
- What's our context? B2C / B2B / SMB / enterprise / specific vertical. Self-serve vs sales-led. Plan structure.
- What constraints are non-negotiable? Compliance, no-third-party-data, must-self-host, etc.
- Which competitors should I look at? If unsure, suggest 3–4 mature ones in the relevant space.
Don't research without these answers. Researching the wrong question wastes a few minutes; acting on the wrong research costs a quarter.
2. Pick competitors deliberately
Mature comparison sets by domain (suggest these as defaults; adjust per user):
| Domain | Suggested competitors |
|---|---|
| SaaS billing & dunning | Stripe, Recurly, Chargebee, Paddle |
| B2B SaaS workspace + RBAC | Linear, Notion, Slack, Asana |
| CRM | Salesforce, HubSpot, Pipedrive, Close |
| E-commerce checkout | Shopify, Stripe Checkout, BigCommerce, WooCommerce |
| Marketplace fees + payouts | Stripe Connect, Airbnb, Etsy, Uber |
| Customer support | Intercom, Zendesk, HelpScout, Front |
| Project management | Linear, Jira, Asana, Monday |
| ERP financials | NetSuite, SAP, Odoo, Microsoft Dynamics |
| Inventory | Shopify, NetSuite, Cin7, Brightpearl |
| Auth / SSO | Auth0, Clerk, WorkOS, Okta |
| Notifications / engagement | Customer.io, Braze, Iterable, Knock |
| Webhooks / events | Stripe, GitHub, Segment |
| Analytics | Mixpanel, Amplitude, PostHog, Segment |
| Search | Algolia, Elasticsearch, Typesense, Meilisearch |
| Status / incidents | StatusPage, Statuspal, Better Uptime |
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.
- 4d ago First seen · 152 lines · 61 tokens per session scan A 81cf4811a5bb
competitive-analysis is a skill published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 1,661 once invoked, about $0.0003 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
sales-qualify
Qualify a sales lead using BANT (Budget/Authority/Need/Timeline) and MEDDIC (Metrics/Economic Buyer/Decision Criteria/Decision Process/Identify Pain/Champion) frameworks against publicly available signals using OSINT only - no scraping of platforms whose ToS forbid it (LinkedIn §8.2, Glassdoor, G2, Capterra…
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing…
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
aidlc-portfolio
Coordinate multiple AI-DLC workflows across repositories and Git worktrees using an evidence-backed portfolio catalog and deterministic workspace tooling. Use when initializing an AI-DLC portfolio workspace, discovering organization or business context, registering projects and dependencies, creating child intents and…
seo-tech-audit
Judge the technical SEO facts produced by seo-crawl and return falsifiable findings + a health score. This is pure analysis — it does no network I/O and only reasons over the crawl JSON.
seo-content
Heuristic content/GEO-readiness analysis of the visible text from seo-crawl. No network. Judgments are heuristic (marked Estimated); raw counts are Measured.