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/aakashg/pm-github-workflow-repo/competitor-scannpx skills add aakashg/pm-github-workflow-repo --skill competitor-scangit clone --depth 1 https://github.com/aakashg/pm-github-workflow-repoWrote 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/aakashg/pm-github-workflow-repo/competitor-scan)<a href="https://agentmods.dev/skills/aakashg/pm-github-workflow-repo/competitor-scan"><img src="https://agentmods.dev/badge/skills/aakashg/pm-github-workflow-repo/competitor-scan.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.1 | $0.00047 | $0.00646 |
| Opus 5 | $0.00023 | $0.00323 |
| Sonnet 5 | $0.00009 | $0.00129 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
competitor-scan 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 6d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitor Scan
Research the specified competitor. Use web search for current information. Focus on verifiable facts.
Process
- Search for website, pricing page, G2 profile, Capterra profile, recent news.
- If private or pre-revenue, note what is unavailable rather than guessing.
- Check user review sites (G2, Capterra, Reddit) for real sentiment.
- Compare to our product only if CLAUDE.md has company context loaded.
Output Format
## Competitor Analysis: [Company Name]
**Date:** [today]
**Sources:** [list every URL referenced]
### Overview
[What they do. Founded, funding, headcount if available. Customer segment.]
### Product
- Core features: [list]
- Recent launches (last 6 months): [list with dates]
- Pricing: [exact tiers and prices, or "not public" if unavailable]
### Strengths (3-5, evidence-backed)
1. [Strength] - Evidence: [specific review, metric, or feature]
### Weaknesses (3-5, evidence-backed)
1. [Weakness] - Evidence: [specific complaint, missing feature]
### User Sentiment
- G2 rating: [X.X/5, N reviews]
- Common praise: [top 2-3 themes]
- Common complaints: [top 2-3 themes]
### Relevance to Us
- Overlap: [where we compete]
- Features they have that we don't: [list]
- Features we have that they don't: [list]
Good vs Bad Output
GOOD: "Pricing: Pro tier $49/user/mo (pricing page, accessed 2026-05). G2: 4.4/5 across 212 reviews; top complaint: slow support." BAD: "They're pretty expensive and people seem to like them." (no source, no number, no date)
Edge Cases
Private company (no public pricing): Write "Pricing: not publicly available." Very new (few reviews): Note the count. "G2: 4.2/5 but only 12 reviews." Multiple products: Ask which product before proceeding. Cannot find info: Say what you looked for and where. No speculation.
Rules
- Cite every claim with a URL.
- Use actual pricing from the pricing page, not from blog posts.
- Save with this exact dated filename:
competitor-[name]-[YYYY-MM-DD].md(anywhere in the repo - the ignore rule keys off the date in the name, not the folder). - Saved that way, the file is git-ignored by default; drop the date and it is NOT protected. It can hold competitive detail you may not want public. To version a reviewed copy, use
git add -f <file>.
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.
- 6d ago First seen · 66 lines · 47 tokens per session scan A a6aa1229b578
competitor-scan is a skill published in the GitHub repository aakashg/pm-github-workflow-repo (2 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 646 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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.
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…
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…