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 0xrafasec/ai-workflow --skill prdgit clone --depth 1 https://github.com/0xrafasec/ai-workflowWrote 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/0xrafasec/ai-workflow/prd)<a href="https://agentmods.dev/skills/0xrafasec/ai-workflow/prd"><img src="https://agentmods.dev/badge/skills/0xrafasec/ai-workflow/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/0xrafasec/ai-workflow/prd"><img src="https://agentmods.dev/badge/skills/0xrafasec/ai-workflow/prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00066 | $0.01038 |
| Opus 5.5 | $0.00026 | $0.00415 |
| Sonnet 5.5 | $0.00013 | $0.00208 |
| Haiku 4.5 | $0.00007 | $0.00104 |
Grade A, and why
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 1mo 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a Product Requirements Document for: $ARGUMENTS
Context Awareness
Before starting, check what already exists:
- Read
docs/directory structure if it exists - Read any existing PRD, README, or whitepaper — do not duplicate what's already written
- If a PRD already exists, ask the user if they want to revise it or start fresh
Process
1. Deep Interview
Use AskUserQuestion to interview the user. This is the most important step — the PRD quality depends entirely on how well you extract the user's thinking.
Start broad, then go deep:
- The problem — What problem are you solving? Who has this problem? How are they solving it today? What's broken about the current approach?
- The solution — What's your high-level approach? What makes it different from existing solutions? What's the core insight?
- Scope and boundaries — What does v1 include? What is explicitly out of scope? What are the non-negotiable requirements vs nice-to-haves?
- Users and stakeholders — Who are the primary users? Are there different user types with different needs? Who else cares about this (ops, security, compliance)?
- Success criteria — How do you know this works? What does success look like in 1 month? 6 months?
- Constraints — Technical constraints (language, platform, infra)? Business constraints (timeline, team size, budget)? Regulatory constraints?
- Risks — What could go wrong? What are the biggest unknowns? What keeps you up at night about this?
Interview rules:
- Don't ask obvious questions — if the user said "Rust CLI tool", don't ask "what language?"
- Dig into contradictions and tensions — "you said X but also Y, how do those reconcile?"
- Ask about the hard parts the user might not have thought through
- It's OK to push back or challenge assumptions — the goal is a solid PRD, not agreement
- Keep going until you have enough to write a comprehensive document. Don't rush.
2. Write the PRD
Write to docs/PRD.md (or docs/prd/<name>.md if this is a sub-feature PRD).
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.
- 1mo ago First seen · 112 lines · 66 tokens per session scan A cb9eb4a121a9
prd is a skill published in the GitHub repository 0xrafasec/ai-workflow (9 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 1,038 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…