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/samkawsarani/sams-product-plugins/write-dev-docsnpx skills add samkawsarani/sams-product-plugins --skill write-dev-docsgit clone --depth 1 https://github.com/samkawsarani/sams-product-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/samkawsarani/sams-product-plugins/write-dev-docs)<a href="https://agentmods.dev/skills/samkawsarani/sams-product-plugins/write-dev-docs"><img src="https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/write-dev-docs.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 | $0.00091 | $0.01904 |
| Opus 5 | $0.00046 | $0.00952 |
| Sonnet 5 | $0.00018 | $0.00381 |
| Haiku 4.5 | $0.00009 | $0.00190 |
Grade A, and why
write-dev-docs 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 4d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Check
Before starting, check optional dependencies:
- qmd (optional): Run
command -v qmd.- If available: Use
qmd queryfor semantic search across knowledge bases — this gives the best results. - If missing: Fall back to
GrepandGlobfor keyword search. Note to the user thatqmdwould improve search quality, but proceed without it.
- If available: Use
Developer Documentation Generator
Generate Stripe-quality developer documentation — API references, integration guides, code recipes, and Postman collections — from any input source.
Quick Start
Arguments: $ARGUMENTS
Parse $ARGUMENTS to determine:
- Doc type: api-reference, guide, recipe, postman
- Subject name: The resource, feature, or API being documented
- Additional context: Language preferences, audience level, specific endpoints
If doc type is not specified, ask the user which type they need.
Triggers:
/write-dev-docs api-reference payments— API reference for payments resource/write-dev-docs guide getting-started— Integration quickstart guide/write-dev-docs recipe create-payment— Multi-language code recipe/write-dev-docs postman payments-api— Exportable Postman collection- "Write API docs for..." / "Create a developer guide for..." / "Generate code samples for..."
Scope — this skill is for:
- API endpoint documentation (REST)
- Developer integration guides and tutorials
- Multi-language code samples and recipes
- Postman/API client collections
NOT for:
- PM documents (PRDs, specs, briefs) → use
write-doc - UX copy or UI text → use
write-ux-copy - SDK source code or library implementation
- Internal architecture docs
Doc Types
| Type | Command | Output | Audience | Reference |
|---|---|---|---|---|
| API Reference | api-reference [resource] |
Endpoint-by-endpoint reference with params, responses, errors | Developers integrating the API | references/api-reference-format.md |
| Integration Guide | guide [name] |
Step-by-step tutorial from zero to working code | Developers new to the platform | references/guide-format.md |
| Code Recipe | recipe [use-case] |
Multi-language copy-paste snippets (cURL, Node.js, Python) | Developers building specific features | references/code-recipe-format.md |
| Postman Collection | postman [api-name] |
Exportable Postman v2.1 JSON with test scripts | Developers testing and exploring the API | references/postman-format.md |
What ships with it
9 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.
- assets/api-reference-template.md 13 KB
- assets/code-recipe-template.md 4.4 KB
- assets/guide-template.md 5.3 KB
- assets/postman-collection-template.json 11 KB
- references/api-reference-format.md 6.3 KB
- references/code-recipe-format.md 5.8 KB
- references/guide-format.md 5.3 KB
- references/postman-format.md 6.5 KB
- references/quality-checklist.md 2.2 KB
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.
- 4d ago First seen · 163 lines · 91 tokens per session scan A eda4f376e125
write-dev-docs is a skill published in the GitHub repository samkawsarani/sams-product-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 91 tokens to every session and 1,904 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…