agentmods.dev

analyze-competition

analyze-competition is a skill for Claude Code from tomzx/agents. It costs 26 tokens per session (405 once invoked), scanned A, original, MIT.

A market-research workflow that compares the alternatives customers could use to solve a problem, including competing products, workarounds, and doing nothing.

In plain words
What is it for?
Use it to document competitors, compare their target customers and claimed jobs, map them across meaningful differences such as price or ease of use, and find positioning gaps.
Why use it?
It shows where existing options are strong or weak and helps identify customer needs that are poorly served.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

not rated 13repo +1 changed 22d ago A scan 26 tokens original MIT

Good fit Use it to document competitors, compare their target customers and claimed jobs, map them across meaningful differences such as price or ease of use, and find positioning gaps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tomzx/agents/analyze-competition
View source ↗ tomzx/agents tomzx.github.io
Install

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.

Any agent
npx skills add tomzx/agents --skill analyze-competition
Clone the repo
git clone --depth 1 https://github.com/tomzx/agents

Made for: Claude Code.

Wrote 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.

agentmods badge for analyze-competition

README.md
[![agentmods](https://agentmods.dev/badge/skills/tomzx/agents/analyze-competition/github.svg)](https://agentmods.dev/skills/tomzx/agents/analyze-competition)
Your own site
<a href="https://agentmods.dev/skills/tomzx/agents/analyze-competition"><img src="https://agentmods.dev/badge/skills/tomzx/agents/analyze-competition/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.

agentmods 80×15 button for analyze-competition

Your own site · 80×15
<a href="https://agentmods.dev/skills/tomzx/agents/analyze-competition"><img src="https://agentmods.dev/badge/skills/tomzx/agents/analyze-competition.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 405 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.00405
Opus 5.5 $0.00010 $0.00162
Sonnet 5.5 $0.00005 $0.00081
Haiku 4.5 $0.00003 $0.00040

Measured 22d ago against content hash 8cb94f175988, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

analyze-competition 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 22d 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.

skills/pdlc/skills/analyze-competition/SKILL.md · 47 lines

What it actually says

Analyze Competition

Maps who else addresses the problem, how they position, and where the gaps are. The output is positioning opportunities, not feature checklists. Pairs with research-market and feeds frame-opportunities.

Prerequisites

  • Apply the shared PDLC conventions in skills/pdlc/references/shared.md.
  • problems.md from discover-problems, or an explicit topic.

Steps

  1. Enumerate alternatives the target customer could use, including the current default and workarounds (the most common "competitor" is doing nothing).
  2. For each, capture positioning: who they target, the job they claim to do, their price/range, and their strongest and weakest points.
  3. Build a positioning map across two axes that matter to the customer (e.g., ease vs. power, price vs. completeness). Identify empty quadrants.
  4. Identify differentiation opportunities: where the problem is underserved, mis-served, or served for the wrong segment.
  5. Note moats and switching costs that affect viability, not just desirability.
  6. Write competitors.md to the initiative directory.

Output Format

Use the template at skills/pdlc/templates/initiatives/competitors.md. Carry the standard initiative frontmatter with phase: discover.

Outcome

If $OUTCOME_YAML is set, emit verdict: drafted.

Completion Checklist

  • Current default / do-nothing included as an alternative
  • Positioning map with two customer-meaningful axes
  • At least one differentiation opportunity identified and tied to a problem
  • Switching costs / moats noted

Next Step

Load frame-opportunities once discovery inputs are ready.

Changes

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.

  1. 22d ago Changed · +4 lines 8cb94f175988
  2. 24d ago Changed 3dae14741b9b
  3. 1mo ago First seen · 43 lines · 26 tokens per session scan A 0c2b237c46fa

Subscribe to this mod's changes

analyze-competition is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 405 once invoked, about $0.0001 per session on Opus 5.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-09-03.

Marketing and SEOResearch
Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens