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 richkuo/rk-skills --skill app-prdgit clone --depth 1 https://github.com/richkuo/rk-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/richkuo/rk-skills/app-prd)<a href="https://agentmods.dev/skills/richkuo/rk-skills/app-prd"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/app-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/richkuo/rk-skills/app-prd"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/app-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.00098 | $0.01417 |
| Opus 5 | $0.00049 | $0.00709 |
| Sonnet 5 | $0.00020 | $0.00283 |
| Haiku 4.5 | $0.00010 | $0.00142 |
Grade A, and why
app-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 6d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
app-prd
Turn a raw idea dump into a complete, implementable PRD committed to the target repo. The PRD is the single source of truth every later stage (question refinement, issue filing, workflow execution) builds on — write it so a cold agent could implement from it plus nothing else.
Input
- An idea dump: features, pricing, constraints, platform choices — usually messy prose. Optionally a target repo (defaults to the current checkout).
- If no repo exists yet and the user named one, offer
gh repo create <name> --privatebefore proceeding.
Steps
1. Check repo state
git status, git log --oneline -3, git remote -v, git ls-remote origin. Three cases:
- Normal repo: proceed with the standard worktree + PR flow.
- Empty repo with remote (no commits anywhere): bootstrap first — create
main, one empty initial commit (git commit --allow-empty -m "Initial commit"+ attribution footer), push. A PR needs a base branch to exist; never put the PRD itself in the bootstrap commit. - No repo/remote: confirm repo creation with the user.
2. Draft PRD.md
Structure (adapt section names to the product, keep the skeleton):
- Header table — product name, repo, platforms, status (mark the MVP scope explicitly, e.g. "Draft v0.1 — MVP scope"), last-updated date.
- Product Overview — what it does, for whom, the emotional/business core in plain language.
- Goals — 3-5 bullets.
- Platforms & Technology — a table: each app surface, domains, payments, database, storage, email, auth. Record deferred infrastructure explicitly ("to be provisioned later; design compatible from day one").
- Feature sections — accounts, core domain objects, creation flows, privacy rules. Number every section (§4.2 style); later stages and issues cite these numbers.
- Pricing — exact rates in tables, worked examples labeled illustrative, discount rules with the user's own example numbers preserved.
- Lifecycle/operations sections — storage tiers, scheduling windows with computed buffers (show the arithmetic: base time + buffer = trigger point).
- Notifications — every trigger, plus the implied supporting set (invites, receipts, warnings) marked as implied.
- Per-platform parity section when there are multiple surfaces.
- Open Questions — numbered; see rule below.
- Out of Scope (MVP).
- Post-MVP Roadmap — everything the user flagged as later.
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.
- 6d ago Changed · +9 lines e57c592e1a77
- 10d ago First seen · 73 lines · 98 tokens per session scan A 85f11b4c66c4
app-prd is a skill published in the GitHub repository richkuo/rk-skills (49 stars, last pushed today), licensed MIT. It adds 98 tokens to every session and 1,417 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-30.
Other skills, from other repositories
contradiction-analysis
A structured way to analyze difficult problems by identifying competing forces, finding the main conflict, and deciding which side or issue has the greatest effect.
mass-line
A method for collecting feedback and facts from multiple people or sources, turning them into a plan, and checking the plan with those affected.
practice-cognition
A method for testing ideas in practice, learning from the results, and improving the next attempt through repeated cycles.
concentrate-forces
A decision-making method for situations where several tasks compete for limited time, attention, computing power, or budget.
protracted-strategy
A long-term planning method for difficult work that cannot be completed quickly, divided into stages with steady progress over time.
arming-thought
A Chinese-language routing guide built around checking facts before drawing conclusions. It helps select other methods for tasks such as investigation, decision-making, review, and long-term planning.