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.
git clone --depth 1 https://github.com/JobsHwang/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/commands/jobshwang/skills/to-prd)<a href="https://agentmods.dev/commands/jobshwang/skills/to-prd"><img src="https://agentmods.dev/badge/commands/jobshwang/skills/to-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/commands/jobshwang/skills/to-prd"><img src="https://agentmods.dev/badge/commands/jobshwang/skills/to-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.00026 | $0.00276 |
| Opus 5 | $0.00013 | $0.00138 |
| Sonnet 5 | $0.00005 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
to-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 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.
What it actually says
The user explicitly invoked /to-prd.
Invocation arguments: $ARGUMENTS
To PRD
Convert already-established product context into a durable, reviewable brief.
- Use the current conversation, a supplied artifact, or both as the source. Do not restart the interview.
- Inspect the repository only for relevant product facts, terminology, and existing document conventions.
- Preserve the user's language. Keep the document proportional to the change and use references/prd-template.md selectively.
- Capture why and what: outcome, users, scenarios, scope, non-goals, requirements, acceptance, constraints, assumptions, risks, and open questions.
- Do not prescribe modules, APIs, schemas, libraries, or implementation steps.
- If a material answer is still unknown, record it under Open Questions instead of automatically launching clarification.
Use an explicitly requested path or an established local convention. Otherwise write .scratch/<feature>/prd.md, choosing a short semantic feature slug. Never overwrite a conflicting artifact silently.
Report the written path, the key scope boundary, and any open questions. Suggest the next explicit action, usually to-spec, but do not invoke it.
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 · 23 lines · 26 tokens per session scan A 170bb2a45b42
to-prd is a command published in the GitHub repository JobsHwang/skills (2 stars, last pushed 6d ago), licensed MIT. It adds 26 tokens to every session and 276 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.