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 commands/fatihkan/badi/competitive-intelgit clone --depth 1 https://github.com/fatihkan/badiWrote 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/commands/fatihkan/badi/competitive-intel)<a href="https://agentmods.dev/commands/fatihkan/badi/competitive-intel"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/competitive-intel.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.00000 | $0.00916 |
| Opus 5 | $0.00000 | $0.00458 |
| Sonnet 5 | $0.00000 | $0.00183 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
competitive-intel 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive analysis command. Analyzes the market, competitors, and opportunities with a comprehensive competitive-intelligence framework.
Required Tools
- Read (existing data)
- Write (report writing)
- Grep (data scan)
- Glob (source discovery)
- Bash (data processing)
Procedure (6 Steps)
Step 1: Define the Frame
Get from the user:
- Product/Service: Name and short definition of what is being analyzed
- Market Category: Which sector, which niche?
- Target Market: Geographic and demographic target
- Known Competitors: The competitor list the user knows
- Analysis Purpose: Why is it being done? (new product launch, price update, strategy revision, etc.)
- Focus Area: The whole market or a specific segment?
Step 2: 3 Parallel Research Agents
Agent 1: Direct Competitor Analysis
- For each direct competitor:
- Product/service features and capability comparison
- Pricing model and price points
- Target customer profile
- Technical infrastructure and technology choices
- Marketing strategy and channels
- Brand positioning
- Customer reviews and satisfaction signals
- Known weak points
Agent 2: Near-Alternative and Indirect Competitor Analysis
- Open-source alternatives
- Solutions solving the same problem differently
- DIY alternatives
- Potential new entrants (expanding from adjacent markets)
- Substitute products and services
Agent 3: Market Context Analysis
- Market size and growth trend
- Recent funding and investment news
- M&A activity
- Regulatory changes
- Technology trends and their impact
- Customer behavior shifts
- Economic factors
Step 3: Comparison Matrix
Build a comprehensive comparison table:
| Criterion | Our Product | Comp A | Comp B | Comp C | Comp D |
|---|---|---|---|---|---|
| Price Range | |||||
| Target Customer | |||||
| Core Features | |||||
| Unique Value | |||||
| Strengths | |||||
| Weaknesses | |||||
| Market Share (est.) | |||||
| Technology | |||||
| Customer Support | |||||
| Integrations | |||||
| Mobile Experience | |||||
| Scalability |
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 · 164 lines · 0 tokens per session scan A 2b7f684a9006
competitive-intel is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 916 tokens. 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 commands, from other repositories
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
sonarqube
Analyze SonarCloud quality issues for a specific PR.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
scaffold
Interactive coach that asks 4-5 questions to determine whether you need an agent, command, skill, hook, or rule — then generates a ready-to-use template. Usage: /scaffold (no arguments — starts the coaching session).
investigate
Systematic root-cause debugging — find the cause before writing any fix.