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 bestdeejay-design/agent-skills --skill docs-productgit clone --depth 1 https://github.com/bestdeejay-design/agent-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/bestdeejay-design/agent-skills/docs-product)<a href="https://agentmods.dev/skills/bestdeejay-design/agent-skills/docs-product"><img src="https://agentmods.dev/badge/skills/bestdeejay-design/agent-skills/docs-product/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/bestdeejay-design/agent-skills/docs-product"><img src="https://agentmods.dev/badge/skills/bestdeejay-design/agent-skills/docs-product.svg" alt="Reviewed on agentmods" width="80" 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.00126 | $0.01088 |
| Opus 5 | $0.00063 | $0.00544 |
| Sonnet 5 | $0.00025 | $0.00218 |
| Haiku 4.5 | $0.00013 | $0.00109 |
Grade A, and why
docs-product 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 9d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Product — product documentation («why» & «what»)
Use this skill to write the product-facing documents: vision, requirements, roadmap, feature catalog. Written from an idea forward — before (or in parallel with) engineering docs.
When to use
- A project needs its product docs: VISION, PRD, ROADMAP, FEATURES.
- User asks for "продуктовая документация", "vision", "prd", "роадмап", "требования к продукту", "product requirements".
- Requirements must become the input for engineering docs.
Do NOT use
- For engineering docs (architecture, ADR, tests, dev guide, map) — that is
docs-project. - For the meta-guide (phases, levels L1/L2/L3, completeness checklist) —
docs-system.
Which docs belong here
| File | Purpose | When | Template |
|---|---|---|---|
docs/VISION.md |
Why the product exists: audience, problem, value, principles, scope, long-term success | Phase 1 — first, stays stable | templates/VISION.tmpl |
docs/PRD.md |
What we build: functional + non-functional requirements, priorities, acceptance criteria, success metrics, user stories | After VISION, before architecture | templates/PRD.tmpl |
docs/ROADMAP.md |
What ships when: milestones, value per milestone, proof (metrics) | Phase 2+, updated each milestone | templates/ROADMAP.tmpl |
docs/FEATURES.md |
Feature catalog + status (✅/📋) — the bridge to engineering | From requirements, kept current | templates/FEATURES.tmpl |
The golden chain: VISION → PRD → ROADMAP → FEATURES. Vision spawns requirements, requirements spawn the plan and the feature catalog. Nothing is written "from the end".
Order of writing
- VISION — can you state the product in 1–2 sentences? If not, stop and clarify before writing anything else.
- PRD — goals/non-goals, stories with priorities, functional + non-functional requirements, acceptance criteria, success metrics (a milestone without a metric is a wishlist).
- ROADMAP — order the PRD's milestones by value (not effort), each with a target date, features, and proof.
- FEATURES — the living status board of every feature, ✅/📋 only against reality. This doc hands the product requirements to the engineering side.
What ships with it
7 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.
- 9d ago First seen · 74 lines · 126 tokens per session scan A a381b2a9392e
docs-product is a skill published in the GitHub repository bestdeejay-design/agent-skills (5 stars, last pushed 2d ago), licensed MIT. It adds 126 tokens to every session and 1,088 once invoked, about $0.0006 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
workflow
Use when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits, high-confidence verification, or tasks explicitly asking to run a workflow. Claude Code uses native dynamic workflows; Codex, OpenCode, and Grok use…
skill-compiler
Automatic solved-to-skill compiler — detects novel task completions and autonomously drafts new SKILL.md files. Stolen from Hermes Agent's learning loop (NousResearch, 2026-05-11).
context-compactor
9-section context compression with analysis scratchpad. Adapted from Claude Code's /compact system (2026-03-31).
daemon-loop
Autonomous recurring agent tasks — converts workflows into persistent background daemons that run on intervals. Stolen from Boris Cherny's Claude Code /loop pattern (2026-03-31).
trade-journal-analyzer
Unified post-trade analytics: journal pattern extraction + drawdown classification. Absorbs: drawdown-classifier.
Deep Research Loop
Multi-step web research, compilation, and synthesis workflow. Scrapes multiple sources, cross-references claims, and produces a structured research brief.