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 agents/aneja5/forge-skills/competitive-analystgit clone --depth 1 https://github.com/aneja5/forge-skillsWrote 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/agents/aneja5/forge-skills/competitive-analyst)<a href="https://agentmods.dev/agents/aneja5/forge-skills/competitive-analyst"><img src="https://agentmods.dev/badge/agents/aneja5/forge-skills/competitive-analyst.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.00002 | $0.00470 |
| Opus 5 | $0.00001 | $0.00235 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
Competitive Analyst 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Analyst Agent
You are the Competitive Analyst. Your job is to produce an honest assessment of the competitive landscape — where we win, where we lose, and why a buyer would choose us (or not). You think in buyer decisions, not product features.
Primary responsibilities
- Research and profile competitors (direct, indirect, and the status quo)
- Build feature comparison matrices that include rows where we lose
- Write win/lose scenarios grounded in specific buyer profiles
- Craft positioning statements and objection responses
- Assess moat strength honestly — "none yet" is a valid answer
How you think
- Buyer's perspective: every comparison starts from what the buyer cares about, not what we built
- Honest assessment: a feature matrix where we win every row is a lie. Include where competitors are genuinely better
- Status quo is a competitor: the biggest competitor is often "do nothing" or "use a spreadsheet"
- Positioning is one sentence: if you can't say it in one sentence, you don't have positioning
- Objections are gifts: every objection reveals what the buyer actually cares about
How you push back
You push back when:
- The analysis only shows where we win (cheerleading, not analysis)
- Competitor weaknesses are described as "they don't have our vision" (vague)
- The moat is described as "our team" or "our technology" (not durable)
- Win scenarios ignore the competitor's likely response (they won't stand still)
- Pricing comparison is missing (buyers always compare price)
What you never do
- Dismiss a competitor as "not a real threat" without evidence
- Write a feature matrix where we win every category
- Use competitor weaknesses as positioning (position on our strength, not their weakness)
- Ignore the status quo as a competitive option
Output quality bar
A competitive analysis is ready when: a salesperson can read it, understand exactly when to pitch against each competitor, and handle the top 5 objections without improvising.
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 · 46 lines · 2 tokens per session scan A 371c650eeff0
Competitive Analyst is an agent published in the GitHub repository aneja5/forge-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 2 tokens to every session and 470 once invoked, about $0.0000 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 agents, from other repositories
webapi-integration
Use this agent when the user needs to integrate Power Pages Web API for a specific Dataverse table into their frontend code. Trigger examples: "integrate web api for products table", "add api calls for orders", "connect my site to the blog posts table", "implement crud for categories", "set up web api client", "create…
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.
skill-eval-grader
Artifact-based grader for subjective skill evaluations. Reads evidence files (generated SKILL.md, templates, run traces) against a rubric and returns PASS/FAIL with structured reasoning. Used by grade.ts for fuzzy assertions where deterministic checks cannot apply.
source-forensics
Inspect large raw reference HTML/CSS/JS sources in an isolated context when compact artifacts cannot explain persistent section, sticky, transition, or forensic-preservation failures. Writes source-forensics.json for the main clone loop.