competitor-tracking

competitor-tracking is a skill for Claude Code, Codex from jonathimer/devmarketing-skills. It costs 93 tokens per session (1,921 once invoked), scanned A, original, MIT.

A framework for systematically researching competing developer tools, including their features, prices, messaging, content, funding, growth, and community opinions.

In plain words
What is it for?
Use it to identify direct and indirect competitors, monitor their activity, find market gaps, and prepare accurate sales or marketing comparison guides.
Why use it?
It helps teams understand their position, notice changes in the market, and avoid relying on incomplete competitor assumptions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to identify direct and indirect competitors, monitor their activity, find market gaps, and prepare accurate sales or marketing comparison guides.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jonathimer/devmarketing-skills/competitor-tracking
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 jonathimer/devmarketing-skills --skill competitor-tracking
Clone the repo
git clone --depth 1 https://github.com/jonathimer/devmarketing-skills

Made for: Claude Code, Codex.

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 competitor-tracking

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/jonathimer/devmarketing-skills/competitor-tracking"><img src="https://agentmods.dev/badge/skills/jonathimer/devmarketing-skills/competitor-tracking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,921 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.00093 $0.01921
Opus 5.5 $0.00037 $0.00768
Sonnet 5.5 $0.00019 $0.00384
Haiku 4.5 $0.00009 $0.00192

Measured 1mo ago against content hash a5b20eb7c375, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

competitor-tracking 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 1mo 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/competitor-tracking/SKILL.md · 314 lines

How it starts

The opening of the file, as written. The whole thing — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Competitor Tracking

Systematic framework for tracking competitors in the developer tools space, from identification through ongoing monitoring and battlecard creation.

Overview

Competitor tracking for developer tools requires monitoring multiple dimensions: product features, pricing, developer sentiment, content strategy, community growth, and funding/trajectory. Unlike consumer products, developer tools compete on technical merit, documentation quality, and community trust.

Effective competitor tracking helps you:

  • Understand your competitive positioning
  • Anticipate competitor moves
  • Arm sales and marketing with accurate battlecards
  • Identify market gaps and opportunities
  • Learn from competitor successes and failures

Competitor Identification

Types of Competitors

Direct Competitors:

  • Same category, same target developer
  • Solve the same core problem
  • Would appear in the same "best X tools" lists
  • Example: If you're a CI/CD tool, other CI/CD tools

Indirect Competitors:

  • Adjacent categories that overlap with your use case
  • Might be expanding into your space
  • Developers might use instead of your category
  • Example: GitHub Actions competing with standalone CI tools

DIY Alternatives:

  • Open source tools developers self-host
  • Custom scripts and internal tooling
  • "Just use bash scripts" or "build it yourself"
  • Often your biggest competitor by volume

Platform Alternatives:

  • Cloud provider native services (AWS, GCP, Azure equivalents)
  • All-in-one platforms that include your functionality
  • Enterprise suite solutions

Competitive Landscape Mapping

Create a competitive landscape document with:

  1. Competitor profiles - Company, product, target market, positioning
  2. Feature matrix - Core features compared across competitors
  3. Pricing comparison - Tiers, pricing model, enterprise pricing signals
  4. Strengths/weaknesses - Honest assessment of each competitor
  5. Trajectory - Funding, growth signals, strategic direction

Read the full file on GitHub · 314 lines

Files

What ships with it

1 file 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.

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. 1mo ago First seen · 314 lines · 93 tokens per session scan A a5b20eb7c375

Subscribe to this mod's changes

competitor-tracking is a skill published in the GitHub repository jonathimer/devmarketing-skills (87 stars, last pushed 7mo ago), licensed MIT. It adds 93 tokens to every session and 1,921 once invoked, about $0.0004 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-08-30.

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

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…

microsoft/vscode · 72 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

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.

microsoft/vscode · 53 tokens