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 Kemdirimakujuobi/skills --skill authoring-a-prdgit clone --depth 1 https://github.com/Kemdirimakujuobi/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/kemdirimakujuobi/skills/authoring-a-prd)<a href="https://agentmods.dev/skills/kemdirimakujuobi/skills/authoring-a-prd"><img src="https://agentmods.dev/badge/skills/kemdirimakujuobi/skills/authoring-a-prd/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/kemdirimakujuobi/skills/authoring-a-prd"><img src="https://agentmods.dev/badge/skills/kemdirimakujuobi/skills/authoring-a-prd.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.00181 | $0.02240 |
| Opus 5.5 | $0.00072 | $0.00896 |
| Sonnet 5.5 | $0.00036 | $0.00448 |
| Haiku 4.5 | $0.00018 | $0.00224 |
Grade A, and why
authoring-a-prd 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 13d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring a PRD
Most teams gate the build — starting-a-change → pre-push-review — but nothing gates how a
feature is described before that. PRDs get written ad hoc, drift in shape, and the backlog is seeded
by hand from memory. This skill is the entry gate: it produces a consistent, reviewable PRD, seeds
the tracker the same way every time, and hands the work to starting-a-change. The PRD is a proposal —
you never push, merge, or deploy; a human pulls every trigger.
The shape lives in the PRD template; the product truth lives in the sources the repo declares. This skill is only the procedure that binds them.
Configure for your repo
The skill expects to find these. AGENTS.md should say where each lives; the default is in brackets.
- PRD folder [
docs/prd/] and a PRD template in it [docs/prd/_template.md]. If the repo has none, copyTEMPLATE.mdfrom this skill's folder into place first. - Product context [
docs/prd/_context.md] — what the product is, the real user roles, the glossary (the terms PRDs most often get wrong), and where truth lives. - Sources of product truth — whichever the repo declares: a capabilities file that marks each capability as shipped, proposed, or unsupported; a per-feature reference with architecture, data model, and caveats; and the code itself. If none is declared, the code is the only source.
- Analytics event catalogue [
docs/analytics-events.md] — the events the product actually emits, and which analytics tool records them. If missing, name new events but flag them as new. - Decision records [
docs/decisions/YYYY-MM-DD-slug.md, templatedocs/decisions/_template.md]. - Issue tracker — Linear, GitHub Issues, Jira, or none; read from
AGENTS.md. Optional: a roadmap file [ROADMAP.md] if the repo keeps one.
Step 0 — Ground in the product
Before drafting anything, read the product context, then every source of truth the feature touches: the capabilities file entries, the feature-reference section, the relevant code paths, and the event catalogue.
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.
- 13d ago First seen · 145 lines · 181 tokens per session scan A 07e9273acc4b
authoring-a-prd is a skill published in the GitHub repository Kemdirimakujuobi/skills (9 stars, last pushed 13d ago), licensed MIT. It adds 181 tokens to every session and 2,240 once invoked, about $0.0007 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-15.
Other skills, from other repositories
product-discovery-and-framing
Frame product opportunities from user, business, technical, and market evidence into testable problem statements, priorities, risks, and success criteria. Use before solution design when the team is unsure what problem to solve or why it matters.
multi-agent-kanban
Coordinate multiple local agents through a durable board with owner, state, and evidence fields.
linear-sync
Linear integration for Mémoire — sync design issues, component specs, and project tracking between Linear and the Mémoire registry.
notion-sync
Notion integration for Mémoire — sync research insights, specs, and project context between Notion databases and the Mémoire registry.
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
factory-human-digest
Experimental workflow for summarizing work that still needs human judgment across configured pull requests, issues, feedback, errors, and delivery signals. Use for a human decision queue or bounded review.