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 devantler-tech/agent-plugins --skill product-documentationgit clone --depth 1 https://github.com/devantler-tech/agent-pluginsWrote 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/devantler-tech/agent-plugins/product-documentation)<a href="https://agentmods.dev/skills/devantler-tech/agent-plugins/product-documentation"><img src="https://agentmods.dev/badge/skills/devantler-tech/agent-plugins/product-documentation/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/devantler-tech/agent-plugins/product-documentation"><img src="https://agentmods.dev/badge/skills/devantler-tech/agent-plugins/product-documentation.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.00051 | $0.01073 |
| Opus 5.5 | $0.00020 | $0.00429 |
| Sonnet 5.5 | $0.00010 | $0.00215 |
| Haiku 4.5 | $0.00005 | $0.00107 |
Grade A, and why
product-documentation 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 yesterday.
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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product documentation
Help a user achieve a real result with the product. A successful build proves the site can be generated; it does not prove the instructions work or the public site is available.
Establish the reader and the contract
Identify the next useful user journey from the request, existing documentation and product interfaces. Separate a newcomer trying the product from an operator installing it and a developer integrating it. Ask only when a missing decision would change the work materially; use the repository's conventions for routine choices.
Read the relevant commands, schemas, configuration defaults, release artifacts and existing guides before describing their behavior. Distinguish released behavior from default-branch development, opt-in features and controlled experimental evidence. Preserve old installation identifiers until their migration actually ships. Never fill a gap with a plausible-looking command or a maturity claim.
Keep one canonical reference for each contract. Link to existing detailed guides or generate reference from the actual interface when the repository supports it; do not maintain a second copied API manual.
Organize around the user's need
Use the Diataxis framework to choose a page's purpose, without forcing every product into identical navigation:
| Need | Content to provide |
|---|---|
| Learn by doing | A small tutorial with prerequisites, ordered steps, observable results and cleanup |
| Complete a task | A focused guide starting from the user's existing situation, including consequential choices and recovery |
| Look up an interface | Accurate fields, defaults, accepted values, constraints and examples, tied to a version |
| Understand a design | Explanations of responsibilities, concepts and tradeoffs, linked from the relevant tasks |
Give the home page a short product explanation and clear routes to a first result and common tasks. Choose concrete navigation labels from what users do or look up. Keep troubleshooting near the failing task: symptom, likely cause, a diagnostic step, a correction and the result that confirms recovery.
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.
- yesterday First seen · 98 lines · 51 tokens per session scan A 9ed70c928eab
product-documentation is a skill published in the GitHub repository devantler-tech/agent-plugins (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 51 tokens to every session and 1,073 once invoked, about $0.0002 per session on Opus 5.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-10-16.
Other skills, from other repositories
technical-documentation
Audit, write, and improve developer documentation using Google's Developer Documentation Style Guide and Technical Writing courses. Use this skill for any documentation work, even when the user names no style guide: "audit our docs", "review this README", "write a README", "getting started guide", "how-to or…
visual-explainer
Generate self-contained HTML pages that visually explain technical material — systems, code changes, plans, data. Use when the user asks for any diagram or visual explanation, when they want a slide deck or a longform document (user guide, how-to, reference page), when another skill needs one rendered, or proactively…
reflect-solution
Summarize WHAT WAS SHIPPED in a Claude Code session as a self-contained HTML slide deck — the elevator pitch (problem, solution, decisions, artifacts, verification, gaps), not a play-by-play of tool calls or debugging detours. Defaults to the current in-context session; optionally accepts a session ID or JSONL path.…
researcher
Use when asked to create research documents, generate PDFs, make one-pagers, or create cheatsheets. Triggers: "research document", "generate PDF", "one-pager", "cheatsheet", "distinctive design". Provides HTML/Markdown/PDF with Terminal, Editorial, Corporate, Industrial, Fresh aesthetic presets.
docx
This skill should be activated when the user asks to create a Word document, report, memo, letter, proposal, whitepaper, or anything involving .docx output. Also triggers when the user says 'write a report', 'create a document', 'make a Word file', 'draft a proposal', 'generate a whitepaper', or mentions .docx.…
xlsx
This skill should be activated when the user asks to create, edit, read, or analyze Excel spreadsheet files (.xlsx, .xlsm, .csv, .tsv). Triggers for: building financial models, creating data tables, formatting spreadsheets, adding formulas, cleaning tabular data, converting between tabular formats. Also triggers when…