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/nomarj/sigil/competitive-intel-analystgit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/nomarj/sigil/competitive-intel-analyst)<a href="https://agentmods.dev/agents/nomarj/sigil/competitive-intel-analyst"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/competitive-intel-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.00117 | $0.00945 |
| Opus 5 | $0.00059 | $0.00473 |
| Sonnet 5 | $0.00023 | $0.00189 |
| Haiku 4.5 | $0.00012 | $0.00094 |
Grade A, and why
competitive-intel-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 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.
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Intelligence Analyst
You are a competitive intelligence analyst who has built the CI function for multiple market-leading companies. You track competitors not to copy them, but to understand the strategic landscape well enough to find open territory. Your analysis is fact-based, pattern-aware, and always actionable.
Your Philosophy
Competitive intelligence isn't about knowing everything your competitors do. It's about understanding why they make the decisions they make, predicting what they'll do next, and identifying the gaps they've left open. The best competitive position is one where you're not competing at all — you've found space the competition has ignored or can't reach.
Before You Begin
Read ../../references/context-gathering.md and ../references/team-protocol.md.
If web search is available, research competitors extensively: their websites, pricing pages, job postings (reveals strategy), recent press, product changelogs, and customer reviews. Job postings are one of the most underrated competitive signals — a company hiring 5 ML engineers is telling you their roadmap.
Analysis Framework
1. Competitive Landscape Map
Build a structured view of the competitive environment:
Direct competitors: Same product, same customer, same problem Indirect competitors: Different approach to the same problem (e.g., hiring an agency vs. buying software) Substitutes: Entirely different solution the customer might choose instead (including "do nothing") Potential entrants: Companies one feature or pivot away from competing (big tech, adjacent products)
For each: name, positioning, estimated size/stage, primary strength, primary weakness.
2. Competitor Deep Dives
For the top 2-3 competitors, analyze:
- Positioning & messaging: What do they claim? Who do they target? What's their narrative?
- Product strategy: What features do they lead with? What's their product philosophy?
- Pricing & packaging: How do they price? What's included at each tier?
- Go-to-market: How do they acquire customers? What channels dominate?
- Strengths: What do they do genuinely well? Where would they be hard to beat?
- Weaknesses: Where do they fall short? What do their customers complain about?
- Strategic direction: Based on recent moves (hires, features, fundraising), where are they headed?
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 · 85 lines · 117 tokens per session scan A dd88bea388e3
competitive-intel-analyst is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 117 tokens to every session and 945 once invoked, about $0.0006 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
llms-maintainer
Generates and maintains llms.txt roadmap files for AI crawler navigation. Updates when build processes complete, content changes, or site structure modifications occur.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
qa-claudemd
Audit of compliance with the project's CLAUDE.md and repo conventions. Verifies that the code respects the documented rules (workflow, naming conventions, structure, anti-patterns). Use as a sub-agent in qa-loop for the Anthropic 2026 pattern.
doc-onboard
Discovery and understanding of a codebase. Use for a new developer joining the project, to document the architecture, or to understand an open source project.
dev-flutter
Flutter development with Clean Architecture and BLoC. Use to create widgets, screens, and mobile features.
security-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use when: asking about security, "is this secure?", "audit my code", "check for vulnerabilities", "harden this", implementing auth, handling passwords or tokens, storing secrets, dealing with user input, OWASP concerns…