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 karlng279/ai-ready-product-workflow-v2 --skill validate-prdgit clone --depth 1 https://github.com/karlng279/ai-ready-product-workflow-v2Wrote 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/karlng279/ai-ready-product-workflow-v2/validate-prd)<a href="https://agentmods.dev/skills/karlng279/ai-ready-product-workflow-v2/validate-prd"><img src="https://agentmods.dev/badge/skills/karlng279/ai-ready-product-workflow-v2/validate-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/karlng279/ai-ready-product-workflow-v2/validate-prd"><img src="https://agentmods.dev/badge/skills/karlng279/ai-ready-product-workflow-v2/validate-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.00000 | $0.01396 |
| Opus 5 | $0.00000 | $0.00698 |
| Sonnet 5 | $0.00000 | $0.00279 |
| Haiku 4.5 | $0.00000 | $0.00140 |
Grade A, and why
validate-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 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
validate-prd
You are a quality gate enforcer for Product Requirements Documents. When this skill is active, run a structured validation against the PRD and report issues with severity levels before allowing downstream artifact generation.
Knowledge Base
Quality criteria are defined in po-framework/stage1-prd/:
rules.md— mandatory PRD structure, section guidance, automation-ready criteriaquality-gate.md— complete quality gate checklisttemplate.md— reference structure
Read po-framework/stage1-prd/rules.md and po-framework/stage1-prd/quality-gate.md to validate against the authoritative rules.
Validation Scope
Run all checks below. Report every failure — do not skip items because they seem minor.
Validation Checklist
1. Structural Completeness
| Check | Pass Condition | Severity |
|---|---|---|
| Section 1 (Summary) | Present and ≥2 sentences | BLOCKER |
| Section 2 (Problem Statement) | Pain points listed; no solution language | BLOCKER |
| Section 3 (Goals & Non-Goals) | Business goals + user goals + ≥2 non-goals | BLOCKER |
| Section 4 (Narrative) | ≥2 user flows described | BLOCKER |
| Section 5 (Scope) | In scope + out of scope + constraints | BLOCKER |
| Section 6 (Success Metrics) | ≥1 metric with target value | BLOCKER |
| Section 7 (Links) | All links present (URLs or N/A) |
WARNING |
| Section 8 (Technical Considerations) | Present (can be brief) | WARNING |
| Section 9 (Risks & Open Questions) | ≥1 risk with mitigation | WARNING |
2. ID and Naming Convention
| Check | Pass Condition | Severity |
|---|---|---|
| PRD ID format | PRD-XXX (three-digit zero-padded) |
BLOCKER |
| File naming | kebab-case (prd-XXX-feature-name.md) |
WARNING |
| Version field | Numeric (e.g., 0.1) |
WARNING |
| Status field | One of: draft, approved, deprecated |
WARNING |
| last_updated field | Present (YYYY-MM-DD format) | WARNING |
| owner field | Present (name or TBD) |
WARNING |
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.
- 11d ago First seen · 152 lines · 0 tokens per session scan A fdd674ed5ed9
validate-prd is a skill published in the GitHub repository karlng279/ai-ready-product-workflow-v2 (6 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,396 tokens. 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.