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/killvxk/pm-skills-zh/competitive-analysisgit clone --depth 1 https://github.com/killvxk/pm-skills-zhWrote 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/killvxk/pm-skills-zh/competitive-analysis)<a href="https://agentmods.dev/commands/killvxk/pm-skills-zh/competitive-analysis"><img src="https://agentmods.dev/badge/commands/killvxk/pm-skills-zh/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.1 | $0.00022 | $0.00904 |
| Opus 5 | $0.00011 | $0.00452 |
| Sonnet 5 | $0.00004 | $0.00181 |
| Haiku 4.5 | $0.00002 | $0.00090 |
Grade A, and why
competitive-analysis 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 6d 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.
What it actually says
/competitive-analysis -- 竞争格局分析
调研并分析你的竞争格局。识别直接竞品与间接竞品，梳理定位，发现差异化机会。
调用方式
/competitive-analysis AI 驱动的项目管理工具
/competitive-analysis 我们的产品 vs Notion、Asana 和 Monday.com
/competitive-analysis [上传竞品列表或市场简报]
工作流程
第一步：理解竞争背景
询问用户：
- 你的产品是什么？它属于哪个品类？
- 有指定要分析的竞品吗？还是让我来识别？
- 分析的侧重点是什么？（功能对比、定位、定价、市场进入策略）
- 这份分析用于什么目的？（战略制定、销售赋能、融资路演、产品路线图）
第二步：识别竞品
应用 competitor-analysis 技能：
- 识别 5 个直接竞品（同品类、同目标买家）
- 识别 2-3 个间接竞品（不同方式、相同的待完成工作）
- 如有必要，注明新兴颠覆性玩家
- 通过网络调研获取最新信息
第三步：逐一分析竞品
针对每家竞品：
- 定位：他们如何描述自己、目标受众、核心信息
- 优势：做得好的地方、赢单的场景
- 劣势：不足之处、常见投诉
- 定价：定价模式及价格区间（如公开披露）
- 市场牵引力：融资情况、团队规模、客户基础信号
- 近期动向：新功能、合作伙伴、战略转型
第四步：生成竞品分析报告
## 竞品分析：[你的产品/市场]
**日期**：[今天]
**分析竞品数**：[数量]
### 市场概览
[2-3 句话描述市场动态、趋势及发展方向]
### 竞争格局
| 竞品 | 品类 | 目标客户 | 定位 | 优势 | 劣势 |
|------|------|----------|------|------|------|
### 功能对比矩阵
| 能力项 | 你的产品 | 竞品 A | 竞品 B | 竞品 C |
|--------|----------|--------|--------|--------|
### 定位地图
[2x2 矩阵，展示各竞品在关键维度上的定位]
### 差异化机会
1. **[机会]** — [为何具有防御性和价值]
2. ...
### 竞争威胁
1. **[威胁]** — [需关注的信号，建议应对策略]
2. ...
### 建议
- **持续强化**：[你的独特优势]
- **补齐短板**：[你缺少的基础功能]
- **选择忽略**：[不值得跟进的竞品动作]
保存为 markdown 格式。
第五步：提供后续建议
- "要我针对某个具体竞品制作销售对战卡吗？"
- "要我制定差异化定位，与头部竞品形成区隔吗？"
- "要我识别功能缺口，添加到路线图中吗？"
注意事项
- 竞品数据来源于网络调研——结果的时效性取决于可获取的信息源
- 区分"入场门槛"（参与竞争的必要条件）与"差异化因素"（赢得竞争的关键）
- 不要只罗列功能——要分析竞品为什么做出这些选择
- 定价情报需注明定价是公开的、按用量收费的，还是需联系销售获取
- 建议每季度更新一次分析——竞争格局变化很快
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.
- 6d ago First seen · 98 lines · 22 tokens per session scan A a6e7fa3e91df
competitive-analysis is a command published in the GitHub repository killvxk/pm-skills-zh (151 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 904 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.