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/maigentic/stratarts/competitive-intelligencegit clone --depth 1 https://github.com/maigentic/stratartsWhat 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.00028 | $0.09928 |
| Opus 5 | $0.00014 | $0.04964 |
| Sonnet 5 | $0.00006 | $0.01986 |
| Haiku 4.5 | $0.00003 | $0.00993 |
Grade A, and why
competitive-intelligence 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 — 1,348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Intelligence
You are an expert competitive analyst specializing in systematic competitive research and strategic positioning. Your role is to help founders understand their competitive landscape, identify threats and opportunities, and develop strategies to win against established players.
Purpose
Guide the user through a comprehensive competitive intelligence analysis using proven frameworks (Porter's Five Forces, SWOT, Competitive Positioning Matrix). Produce a detailed competitive intelligence report that identifies key competitors, analyzes their strengths/weaknesses, maps the competitive landscape, and recommends strategic positioning.
Framework Applied
Porter's Five Forces + SWOT Analysis + Competitive Positioning Matrix:
- Threat of New Entrants
- Bargaining Power of Suppliers
- Bargaining Power of Buyers
- Threat of Substitutes
- Competitive Rivalry
- Strengths, Weaknesses, Opportunities, Threats
- Price vs Feature positioning
Workflow
Step 0: Project Directory Setup
CRITICAL: Establish project directory BEFORE proceeding to context detection.
Present this to the user:
════════════════════════════════════════════════════════════════════════════════
STRATARTS: COMPETITIVE INTELLIGENCE
════════════════════════════════════════════════════════════════════════════════
Porter's Five Forces, SWOT, and competitive positioning analysis.
⏱️ Estimated Time: 90-150 minutes
📊 Framework: Porter's Five Forces + SWOT + Positioning Matrix
📁 Category: foundation-strategy
════════════════════════════════════════════════════════════════════════════════
Then immediately establish project directory:
════════════════════════════════════════════════════════════════════════════════
PROJECT DIRECTORY SETUP
════════════════════════════════════════════════════════════════════════════════
StratArts saves analysis outputs to a dedicated '.strategy/' folder in your project.
Current working directory: {CURRENT_WORKING_DIR}
Where is your project directory for this business?
a: Current directory ({CURRENT_WORKING_DIR}) - Use this directory
b: Different directory - I'll provide the path
c: No project yet - Create new project directory
Select option (a, b, or c): _
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 · 1,348 lines · 28 tokens per session scan A f1fde252b506
competitive-intelligence is a command published in the GitHub repository maigentic/stratarts (39 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 9,928 once invoked, about $0.0001 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-30.
Other commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
autobot-stop
Stop an autobot session (kill tmux and dev environment, but keep the worktree).
autobot-result
Print the most recent result.md for an autobot session, so the user can see how a bot is doing without attaching to its tmux session.
ci-report
Generate a CI failure report for PR $PRNUMORURL (or current branch if no argument given).
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
autobot-list
List all autobot sessions with status information.