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 samkawsarani/sams-product-plugins --skill write-docgit 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-doc)<a href="https://agentmods.dev/skills/samkawsarani/sams-product-plugins/write-doc"><img src="https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/write-doc/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/samkawsarani/sams-product-plugins/write-doc"><img src="https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/write-doc.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.00092 | $0.01901 |
| Opus 5 | $0.00046 | $0.00950 |
| Sonnet 5 | $0.00018 | $0.00380 |
| Haiku 4.5 | $0.00009 | $0.00190 |
Grade A, and why
write-doc 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 8d 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 — 175 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
Product Documentation Generator
Generate comprehensive product documentation (PRDs, briefs, specs, user stories, decision docs) with full context from your knowledge base.
Modes
This skill supports two modes:
Auto-Generate Mode (default): Generates a complete first draft from templates and knowledge base context. Use when you want an immediate, comprehensive document.
- Triggered by:
/write-doc prd feature-name,/write-doc spec feature-name, or "generate a PRD for X"
Co-Authoring Mode: Guided, iterative document creation through structured conversation — context gathering, section-by-section refinement, and reader testing. Use when you want collaborative, high-quality writing.
- Triggered by:
/write-docwith collaborative intent, "co-author a doc", "help me write a spec", or "let's work on a PRD together" - See
references/coauthoring-workflow.mdfor the full co-authoring workflow
How to choose:
- Need a quick first draft? → Auto-generate
- Want to iterate and refine together? → Co-authoring
- Not sure? → Auto-generate first, then switch to co-authoring for refinement
Quick Start
Arguments: $ARGUMENTS
Parse $ARGUMENTS to determine:
- Document type: prd, brief, spec, user-stories, decision
- Subject name: The feature/project name
- Mode hint: If user language suggests collaboration ("help me write", "let's co-author", "work together on"), use co-authoring mode
If document type is not specified, ask the user which type they need.
How it works (auto-generate):
- Identify document type needed (or ask if ambiguous)
- Gather context from knowledge base and existing files
- Select appropriate template from assets/
- Generate complete first draft
- Present for review and iteration
What ships with it
6 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.
- 8d ago First seen · 175 lines · 92 tokens per session scan A 8b3a71374360
write-doc is a skill published in the GitHub repository samkawsarani/sams-product-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 1,901 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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…