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/jayrha/agentskills/competitive-analysisnpx skills add JayRHa/AgentSkills --skill competitive-analysisgit clone --depth 1 https://github.com/JayRHa/AgentSkillsWhat 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.00089 | $0.01810 |
| Opus 5 | $0.00044 | $0.00905 |
| Sonnet 5 | $0.00018 | $0.00362 |
| Haiku 4.5 | $0.00009 | $0.00181 |
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 2d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Analysis
Overview
Keywords: competitive analysis, competitor research, market positioning, SWOT, feature comparison, pricing analysis, battlecard, differentiation, market gap, positioning map, win/loss, moat, go-to-market.
This skill turns scattered impressions about "the competition" into a rigorous, decision-grade analysis. It covers the full arc: define scope, identify the right competitors, collect structured evidence, build comparison matrices, derive positioning, and produce concrete recommendations (where to compete, how to differentiate, what to fix).
Use it for product strategy, sales enablement (battlecards), fundraising decks, market-entry decisions, and quarterly competitive reviews. The goal is always a defensible conclusion backed by a traceable evidence trail — not vibes.
Bundled resources:
references/frameworks.md— Porter's Five Forces, SWOT, positioning maps, JTBD, value-curve, perceptual mapping, moat taxonomy, with when-to-use guidance.references/data-sources.md— where to find legitimate competitive intel, and the ethics/legal guardrails.scripts/compare_matrix.py— stdlib-only tool that ingests a competitor JSON/CSV and emits a weighted scored comparison matrix in Markdown.templates/competitive-analysis-report.md— fill-in report template.templates/battlecard.md— one-page sales battlecard template.examples/saas-pm-tool-analysis.md— a complete worked example.
Workflow
Follow these steps in order. Do not skip scoping — most weak analyses fail because the question was never sharpened.
-
Scope the question. Pin down the decision the analysis must serve (e.g., "Should we move upmarket?", "What do we say when a prospect mentions Asana?"). Write a one-sentence objective and name the audience (product, sales, exec, investor). The objective dictates which framework and depth you use.
-
Define the market and segment. State the category, the buyer, the geography, and the job-to-be-done. Ambiguity here makes every comparison apples-to-oranges. Capture this as the "Market Definition" block.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 114 lines · 89 tokens per session scan A bc10773502b8
competitive-analysis is a skill published in the GitHub repository JayRHa/AgentSkills (4 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 1,810 once invoked, about $0.0004 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
viral-tech-reel-editor
End-to-end viral tech reel production for Instagram Reels and TikTok using 2026 trend grammar — retention-first pacing, punch-ins, 3D cinematic AI-generated shots, motion design graphics, proof b-roll, trending SFX, karaoke captions (Georgian/English), safe-zone layout, and QA-gated 1080x1920 export. This skill should…
pricing-advisor
Describe your product and target customer, get a pricing strategy with three tiers and rationale.
growth-ideas
Describe your product or project and get three actionable growth ideas tailored to your stage.
social-media-posting
Create, adapt, and schedule social media content across platforms with platform-specific formatting, engagement hooks, and strategic posting cadence.
seo-optimization
Optimize a webpage for search engines by analyzing on-page elements, improving technical performance, and implementing structured data for maximum visibility.
marketing-skills-guide
Guide for marketing and growth skills including SEO, copywriting, CRO, email campaigns, paid ads, and product launch strategies.