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.
git clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWrote 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/evan043/claude-cli-advanced-starter-pack/research-competitor.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/research-competitor.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/research-competitor.template.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.1 | $0.00000 | $0.01146 |
| Opus 5 | $0.00000 | $0.00573 |
| Sonnet 5 | $0.00000 | $0.00229 |
| Haiku 4.5 | $0.00000 | $0.00115 |
Grade A, and why
research-competitor.template 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 7d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
description: Comprehensive 6-phase competitive intelligence analysis type: project complexity: high
/research-competitor
Comprehensive 6-phase competitive intelligence analysis for any product or market.
Usage
/research-competitor [product-name]
/research-competitor "Product Name" --domain "market domain"
/research-competitor --continue # Resume previous analysis
Overview
This command runs a structured 6-phase competitive analysis:
| Phase | Name | Est. Time | Output |
|---|---|---|---|
| 1 | Competitor Discovery | 5 min | Competitor list |
| 2 | Feature Extraction | 10 min | Feature inventory |
| 3 | Pricing Analysis | 5 min | Pricing comparison |
| 4 | Tech Stack Discovery | 5 min | Tech insights |
| 5 | Market Sentiment | 8 min | Review analysis |
| 6 | Feature Gap Analysis | 5 min | Gap matrix + priorities |
Total estimated time: ~38 minutes
Instructions
When this command is invoked:
Step 1: Gather Context
Ask the user (if not provided):
- What is the product/service being analyzed?
- What market domain does it operate in?
- Are there known competitors to include?
Step 2: Run Discovery Phase
Use WebSearch to find:
- "[product] alternatives"
- "[product] competitors"
- "best [domain] tools 2026"
Compile a list of 5-10 competitors with:
- Company name
- Website URL
- Brief description
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.
- 7d ago First seen · 196 lines · 0 tokens per session scan A 72bd56aefb40
research-competitor.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,146 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-30.
Other commands, from other repositories
worktree-cleanup
A command for removing a Git worktree, which is a separate working folder linked to the same repository, after its pull request is merged.
quick-commit
A quick Git command for committing and pushing a small code change. Git is the tool that records code versions and sends them to a shared repository.
security-review
A security review procedure based on CWE, a list of common software weaknesses, and STRIDE, a method for identifying threats to a system.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
security-scan
Run security audit on codebase.
test-suite
Run comprehensive test suite with coverage analysis.