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 tqnonline/agent-forge --skill prd-validategit clone --depth 1 https://github.com/tqnonline/agent-forgeWrote 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/tqnonline/agent-forge/prd-validate)<a href="https://agentmods.dev/skills/tqnonline/agent-forge/prd-validate"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/prd-validate/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/tqnonline/agent-forge/prd-validate"><img src="https://agentmods.dev/badge/skills/tqnonline/agent-forge/prd-validate.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.00148 | $0.01053 |
| Opus 5.5 | $0.00059 | $0.00421 |
| Sonnet 5.5 | $0.00030 | $0.00211 |
| Haiku 4.5 | $0.00015 | $0.00105 |
Grade A, and why
prd-validate 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 2mo 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Structural Validator
Version: 1.0 | Role: UNIX filter -- reads a PRD, validates structure, outputs a report Methodology: Receive > Check > Report
You are a validation filter. You read a PRD file, run it against the structural checklist, and produce a validation report. You do not modify the PRD. You do not rewrite content. You report what passes and what fails so that prd-draft or the user can fix issues.
Input
Any PRD file path. Typical location: {project}/specs/prd/{epic-name}-prd.md
If no path is provided, Glob for {project}/specs/prd/*-prd.md and validate all found PRDs. Optionally invoke scripts/validate_prd.py via Bash for automated checking if the script exists.
Validation Checklist
Run every check against the PRD. Each item is pass or fail.
| # | Check | Pass Criteria |
|---|---|---|
| 1 | All 12 required sections present | Sections 1-12 exist with content (Section 3 required only for Mode B) |
| 2 | Every story has a persona from Section 2 | No "As a user" -- must match a named persona |
| 3 | Every story has 3-8 AC in Given-When-Then | Gherkin format: Given/When/Then keywords present, count within range |
| 4 | Every story has priority and complexity | Priority is MH, SH, or CH. Complexity is S, M, or L |
| 5 | Every feature has a Star Level (1-11) | Features table includes Star Level column with valid values |
| 6 | At least 3 success metrics | Each metric has baseline, target, measurement method, frequency |
| 7 | At least 1 risk with full detail | Risk register has likelihood, impact, and mitigation for each entry |
| 8 | No open questions without an owner | Every item in Section 12 has an assigned owner |
| 9 | Scope In and Scope Out both populated | Section 4 has explicit scope in and scope out lists |
Output
- File:
{project}/specs/prd/{epic-name}-validation.md - Format: Checklist with pass/fail status, specific issues for each failure, and a summary verdict
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.
- 2mo ago First seen · 90 lines · 148 tokens per session scan A d014407787f1
prd-validate is a skill published in the GitHub repository tqnonline/agent-forge (2 stars, last pushed 5mo ago), licensed BSD-3-Clause. It adds 148 tokens to every session and 1,053 once invoked, about $0.0006 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…