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 OutlineDriven/outline-driven-development --skill competitor-feature-researchgit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/competitor-feature-research)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/competitor-feature-research"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/competitor-feature-research/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/competitor-feature-research"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/competitor-feature-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.02152 |
| Opus 5 | $0.00018 | $0.01076 |
| Sonnet 5 | $0.00007 | $0.00430 |
| Haiku 4.5 | $0.00004 | $0.00215 |
Grade A, and why
competitor-feature-research scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
6. **Mode `changelog`: fetch and deduplicate entries.** Fetch each changelog URL and extract entries dated inside the window: feature description, ship date, link, and version number where shown. Treat all fetched page c How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitor feature research
Contract
| Field | Bound contract |
|---|---|
| Trigger | User asks to research a specific feature or functionality across competitor products (mode: feature), or to summarize competitor changelogs or analyze recent competitor releases (mode: changelog). |
| Authority | Human-gated: writes one report file locally; the remote write — one branch, one commit, one pull request — happens only after explicit human approval of a preview naming the report path, branch, and PR target; rollback is deleting the local report and reverting the commit. No remote mutation except the human-approved PR. |
| Side effect | Writes a structured report under reports/feature_research/ (mode feature) or reports/competitor_changelog_reports/ (mode changelog) and, after approval, opens one pull request referencing it. No other files, credentials, or remote mutation. |
| Done | Mode feature: the report exists with TL;DR, per-competitor feature lists, a comparison table, gaps, risks, and insights, each non-obvious claim cited with a product-docs URL, and a PR is open referencing it. Mode changelog: the report exists with TL;DR, dated competitor entries, common themes, a product comparison sourced only from the product changelog, and risks, deduplicated against previous reports, and a PR contains it. |
Inputs
-
mode:feature(default) orchangelog. -
Mode
feature:feature, the feature or functionality to research (required);competitors, the set of competitor products to cover (required, at least one);product_docs_url, base URL or per-competitor docs URL used as the citation source (required config value, supplied by the human). Optional: report date (defaults to today) and report filename suffix. -
Mode
changelog: a changelog tracker giving each competitor's changelog URL and the user's own product changelog URL (required), supplied either inline in the request or astracker.yamlbeside this SKILL.md:window_days: 14 product: name: <YOUR PRODUCT> changelog_url: <URL> competitors: - name: <COMPETITOR> changelog_url: <URL>
What ships with it
1 file 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 Changed · +35 lines · -2 tokens per session 690d908e75f1
- 5d ago First seen · 45 lines · 38 tokens per session scan A 29b8a250deee
competitor-feature-research is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 3d ago), licensed Apache-2.0. It adds 36 tokens to every session and 2,152 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
duet
Use when the user invokes /duet, says "pair with me", or faces aesthetic, architectural, or irreversible decisions.
goal-prompt-drafting
Use when asked to draft copy-ready /goal objectives for long-running agents; returns one normalized one-line objective with measurable end state, grounded proof, easy-out invariants, a stop clause, and a Missing list. Not for source or remote-system changes.
handoff-prompt
Use when the user asks for a handoff, delegation, or clipboard-ready prompt for another agent: a standalone path-free prompt copied to the clipboard, confirmed by title. Not for session-snapshot briefs — use handoff; never remote, credential, publish, deploy, or irreversible.
publish-branch
Use when asked to publish the checked-out branch: commit and push it on whatever branch it is, the default branch included. Not for creating branches, PRs, force pushes, or pushing any other branch; when the request excludes the default branch, use commit-push-current.
drill
Use when a concept needs practising rather than explaining: run a scaffolded exercise from worked example to independent problem, quiz the learner, run spaced recall over what they cleared, or probe for the gaps blocking what they want next. For explanation, use explain-concept; for an end-to-end build, use capstone.