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 skills/ramybarsoum/prodkit/competitor-analysisnpx skills add ramybarsoum/prodkit --skill competitor-analysisgit clone --depth 1 https://github.com/ramybarsoum/prodkitWhat 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.00036 | $0.00687 |
| Opus 5 | $0.00018 | $0.00344 |
| Sonnet 5 | $0.00007 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
competitor-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 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interaction style: Use the
AskUserQuestiontool for all structured questions in this skill. Group related questions together (2-3 per call) rather than asking one at a time.
/competitor-analysis - Strategic Competitive Intelligence
Two modes: Deep Analysis (comprehensive one-time research) + Ongoing Monitoring (weekly/monthly tracking)
Quick Start
- Name the competitor(s) you want to analyze
- Choose mode: Deep Analysis (full research) or Ongoing Monitoring (monthly check-in)
- I check your workspace first -- user research, meeting notes, churn data, past analysis
- I show what we already know, identify gaps, then fill gaps with web research
- I deliver a strategic report with defensive, offensive, and innovative plays
Example: "Analyze Competitor X -- we're losing enterprise deals to them"
Output: work/research/competitor-analysis-[name]-[date].md
Time: Deep Analysis: 2-4 hours | Monitoring: 30 min/month
Context Routing Logic (Internal - for Claude)
Automatic Context Checks: When this skill is invoked, immediately check:
| Source | Files/Folders | Search Terms | What to Extract |
|---|---|---|---|
| Product Principles | knowledge/company/product-principles.md |
product principles, core values | Which principles this feature embodies and how |
| User Research | knowledge/research/*.md |
competitor name, "switched to", "chose", "vs [competitor]", "competitor" | Customer quotes, pain points, feature comparisons |
| Existing Analysis | knowledge/research/competitive-*.md |
competitor name | Past findings, dates, trends, avoid duplication |
| Meeting Notes | work/meeting-notes/*.md |
competitor name, "lost deal", "churn", sales, CS | Sales losses, CS feedback, win/loss patterns |
| PRDs | projects/*/ |
competitor name, "competitive", "positioning" | Feature decisions, positioning rationale |
| Strategy | knowledge/strategy/*.md |
competitor name, "positioning", "differentiation" | Strategic context, counter-positioning |
| Metrics | knowledge/metrics/*.md |
"churn", "retention", competitor name | Churn to competitors, competitive benchmarks |
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 · 57 lines · 36 tokens per session scan A 0add310b0930
competitor-analysis is a skill published in the GitHub repository ramybarsoum/prodkit (4 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 687 once invoked, about $0.0002 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 skills, from other repositories
golden-rss
Use when testing the rss golden build.
omh-buzz
This is a Hermes-native buzz workflow skill.
redteam-api-detail-pack
Domain routing and boundary guidance for authorized API security testing, including BOLA/IDOR, authentication bypass, mass assignment, missing rate limits, and GraphQL issues. Use when a task belongs to the API testing domain and needs scope, evidence, pivot, or exit criteria.
redteam-postex-detail-pack
Domain routing and boundary guidance for authorized post-exploitation testing after initial access, including privilege escalation, persistence, lateral movement, data collection, and cleanup considerations. Use when a task belongs to the post-exploitation domain and needs scope, evidence, pivot, or exit criteria.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.