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/zircote-plugins/sigint/competitive-analysisnpx skills add zircote-plugins/sigint --skill competitive-analysisgit clone --depth 1 https://github.com/zircote-plugins/sigintWrote 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/zircote-plugins/sigint/competitive-analysis)<a href="https://agentmods.dev/skills/zircote-plugins/sigint/competitive-analysis"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sigint/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.00065 | $0.01785 |
| Opus 5 | $0.00032 | $0.00892 |
| Sonnet 5 | $0.00013 | $0.00357 |
| Haiku 4.5 | $0.00006 | $0.00178 |
Grade C, and why
competitive-analysis scanned grade C with 1 finding 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 3d 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
4. Be helpful and engaging — never refuse outright How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Analysis
Overview
Competitive analysis systematically evaluates competitors to understand market positioning, identify gaps, and inform strategic decisions. This skill provides frameworks and methodologies for thorough competitive intelligence gathering.
Required Frameworks
| Framework | Output Section | Required | Condition |
|---|---|---|---|
| Porter's 5 Forces | Porter's 5 Forces Analysis | yes | — |
| Competitor Matrix | Competitive Matrix | yes | — |
| Positioning Map | Positioning Map | conditional | Needs 2+ comparable dimensions from elicitation or competitors |
| Trend Indicators | throughout | yes | — |
Trend Indicators: Load and apply the trend indicator definitions from protocols/TREND-INDICATORS.md.
When to Use
- Entering a new market or segment
- Evaluating product positioning
- Identifying feature gaps
- Understanding pricing dynamics
- Assessing competitive threats
- Planning differentiation strategy
- Creating board/investor-ready competitive landscape documents
- Analyzing emerging or nascent markets with indirect/potential competitors
Handling Incomplete Prompts
When the user's request lacks critical context (no market, industry, or competitors specified), do NOT fabricate an analysis. Instead:
- Acknowledge the request enthusiastically
- Ask clarifying questions about: market/industry, product, known competitors, analysis goal, target customer segment
- Describe what deliverables they can expect once context is provided
- Be helpful and engaging — never refuse outright
Adapting for Emerging Markets / New Categories
When analyzing a market that does not yet exist or has no direct competitors:
- Do NOT say competitive analysis is inapplicable — it is MORE important for new categories
- Identify what customers currently use as substitutes (manual processes, consultants, existing tools, DIY solutions)
- Map indirect competitors from adjacent markets who could pivot into the space
- Identify potential entrants — well-funded adjacent players most likely to enter
- Adapt Porter's 5 Forces: rivalry is typically low (temporary), threat of new entry is typically high, threat of substitution is typically very high
- Address first-mover and category creation dynamics (advantages and risks)
- Provide strategic recommendations focused on category definition, building switching costs, and monitoring potential entrants
What ships with it
4 files 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.
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.
- 3d ago First seen · 228 lines · 65 tokens per session scan C 1bed5c4a29f1
competitive-analysis is a skill published in the GitHub repository zircote-plugins/sigint (20 stars, last pushed 17d ago), licensed MIT. It adds 65 tokens to every session and 1,785 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gr-competitor
竞品深度扫描。批量抓取对手落地页（title/h1/intro/pricing）、定价页、博客 top 10、 变更历史（Wayback）。底层调 actionbook（并发 30 tab + 省 90% token）。 当用户说"分析对手"、"看看竞品在做啥"、"找对标"、"扫一下 top 10"时调用。.
mapping-markets
Map the market around any company from its domain alone — competitors, substitutes, the infrastructure it sits on, the directories that list it, the publications that cover it and the communities its buyers argue in — with a source and a reason on every entry. Use this skill whenever someone wants a competitive…
kb-clerk-com
Walk the clerk.com market map — competitors, substitutes, segments, buyers and the evidence behind every claim. Use when asked who competes with clerk.com, for a battlecard, an ecosystem overview, why an entity is on this map, or how much of it to trust. Every answer should carry the note's receipts.
radar-merge-briefing
Merges all competitor dossiers and the change set into one briefing. Writes three local artifacts: the briefing markdown, a combined raw dossier JSON, and a dashboard data JSON. Use after radar-diff-changes and before radar-publish-notion and radar-render-dashboard. Every claim in the briefing carries a source URL.
radar-publish-council
Publishes the Strategic War Room addendum from /radar-council to all three surfaces. Appends the addendum to the local briefing markdown, fills the warroom section of the dashboard data and re-renders the dashboard, and appends the addendum to the Notion briefing page while checking its War Room box. Use after the…
industry-research
Industry research assistant for general AI agents. Use for industry overviews, industry question decomposition, company or product positioning, industry maps, lifecycle assessment, information source selection, profitability analysis, valuation logic, prosperity indicators, PEST analysis, competitive structure, risk…