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 skills add kazdenc/builder-skills --skill competitivegit clone --depth 1 https://github.com/kazdenc/builder-skillsWrote 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/skills/kazdenc/builder-skills/competitive)<a href="https://agentmods.dev/skills/kazdenc/builder-skills/competitive"><img src="https://agentmods.dev/badge/skills/kazdenc/builder-skills/competitive.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.00050 | $0.01018 |
| Opus 5 | $0.00025 | $0.00509 |
| Sonnet 5 | $0.00010 | $0.00204 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
competitive 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Analysis
Work through these five steps in order. Each builds on the previous one.
Step 1 — Identify Competitors
Sort every competitor into one of three buckets:
| Type | Definition | How to find them |
|---|---|---|
| Direct | Solves the same job with a similar product | Search the category name, check review sites, ask users "what else did you consider?" |
| Indirect | Solves the same job with a different approach | Ask "how did people do this before products like ours existed?" |
| Substitutes | Competes for the same budget, time, or attention | Ask "what would they do instead of solving this job at all?" |
Include "do nothing" as a substitute — it is always the strongest competitor.
List 3–7 competitors. More than that dilutes focus.
Step 2 — Feature Comparison Matrix
Build a table. Rows are capabilities that matter to the job. Columns are competitors. Score each cell.
| Capability | Us | Competitor A | Competitor B | Competitor C |
|------------------------|----|-------------|-------------|-------------|
| [capability 1] | .. | .. | .. | .. |
| [capability 2] | .. | .. | .. | .. |
| ... | | | | |
Scoring:
- Strong — does this well, customers recognize it as a strength
- Adequate — does it, no complaints, no praise
- Weak — does it poorly or partially
- Missing — doesn't do it at all
Pick capabilities from the user's perspective, not the feature list. "Quickly see what changed since yesterday" beats "activity feed" or "notification system."
Step 3 — Positioning Analysis
Plot competitors along the two dimensions that matter most for this market. Pick dimensions from the job, not from product attributes.
[Dimension A — high]
│
│ ○ Competitor B
│
[Dimension B — low] ───────┼──────── [Dimension B — high]
│
○ Competitor A │
│ ○ Competitor C
[Dimension A — low]
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 · 112 lines · 50 tokens per session scan A bb5db6cf4ebc
competitive is a skill published in the GitHub repository kazdenc/builder-skills (44 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 1,018 once invoked, about $0.0003 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 skills, from other repositories
commercial-opportunity-review
Review Product, offering, catalog, quote, and sale evidence for commercial opportunities.
demand-triage
Prepare classification, evidence gaps, and score inputs for product demand without crossing the funding boundary.
product-line-performance-review
Roll real Product evidence into a ProductLine review without changing the canonical reporting boundary.
stakeholder-brief
Prepare a concise owner or stakeholder brief with current decisions, evidence, bets, outcomes, roadmap, and provenance.
weekly-intelligence
Review cited market, competitor, customer, and delivery changes for one explicit business-product scope.
investment-preparation
Prepare an evidence-linked product investment packet while preserving the governed funding decision.