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 uthumany/uthy-legacy-os --skill prd-writergit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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/uthumany/uthy-legacy-os/prd-writer)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/prd-writer"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/prd-writer/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/uthumany/uthy-legacy-os/prd-writer"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/prd-writer.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.00036 | $0.01065 |
| Opus 5 | $0.00018 | $0.00532 |
| Sonnet 5 | $0.00007 | $0.00213 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
prd-writer 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 11d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Writer
Overview
A Product Requirements Document (PRD) is the source of truth for what you're building and why. It aligns engineering, design, QA, and stakeholders around a shared understanding. This skill helps you write PRDs that are clear, complete, and actionable — with enough context for good decisions and enough specificity for reliable execution.
When to Use
- You've validated a problem and solution through discovery
- You need to hand off a feature to engineering and design
- Multiple teams need to coordinate on a shared initiative
- You want to document decisions and context for future reference
- Don't use for: speculative ideas (PRD is for committed work), tiny changes (use a ticket), or trying to think through a problem (use a brief or spec doc first)
Instructions
1. Start with the Why
Problem Statement: What problem are we solving? (Reference the problem-statement skill) Evidence: Link to customer interviews, analytics, experiments Strategic Context: How does this align with OKRs or product strategy?
2. Define Scope
In scope: What's included? Be specific. Out of scope: What's explicitly NOT included? (Prevents scope creep) User stories: Brief list of what users can do after this ships
3. Detail the Requirements
For each feature or change:
- Description: What it does and why it exists
- User experience: How users interact with it
- Acceptance criteria: Given/When/Then format (see acceptance-criteria skill)
- Edge cases: Empty states, error states, permission states
- Analytics: What events to track
4. Define Success
North star: What outcome does this serve? Success metrics: How will we know it's working? (see metrics-framework) Counter-metrics: What should NOT degrade? Launch criteria: What must be true before we ship? Time to evaluation: When after launch will we measure success?
5. Add Logistics
Dependencies: What other work or teams does this depend on? Timeline: When does each phase ship? Risks: What could go wrong and what's the mitigation? Open questions: What decisions are still pending?
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.
- 11d ago First seen · 133 lines · 36 tokens per session scan A 5739b04ed091
prd-writer is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 1,065 once invoked, about $0.0002 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…