Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add infraspecdev/tesseract/plugin install shieldWrote 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/infraspecdev/tesseract/prd-review)<a href="https://agentmods.dev/skills/infraspecdev/tesseract/prd-review"><img src="https://agentmods.dev/badge/skills/infraspecdev/tesseract/prd-review/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/infraspecdev/tesseract/prd-review"><img src="https://agentmods.dev/badge/skills/infraspecdev/tesseract/prd-review.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.00080 | $0.03366 |
| Opus 5.5 | $0.00032 | $0.01346 |
| Sonnet 5.5 | $0.00016 | $0.00673 |
| Haiku 4.5 | $0.00008 | $0.00337 |
Grade A, and why
prd-review 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Review
Dispatch parallel expert reviewer agents against a PRD to produce a scored analysis with prioritized gaps, severity tiers, and an enhanced PRD with suggested fixes.
Output Path — MANDATORY
All review output goes into a per-run, date-keyed folder under the feature's reviews/prd/ directory:
{output_dir}/{feature}/reviews/prd/{date}{_counter}/ ← {review_dir}
├── summary.md ← {review_summary} (main output)
├── source-prd.md ← verbatim source snapshot (side-artifact)
├── enhanced-prd.md ← {review_enhanced} (P0/P1 inline + P2 comments)
├── review-comments.json ← canonical structured per-section gaps (side-artifact)
└── detailed/
├── pm-reviewer.md ← {review_detailed} (agent=pm-reviewer)
├── agile-coach.md ← {review_detailed} (agent=agile-coach)
├── tech-lead-reviewer.md ← {review_detailed} (agent=tech-lead-reviewer)
├── dx-reviewer.md ← {review_detailed} (agent=dx-reviewer)
└── finops-analyst.md ← {review_detailed} (agent=finops-analyst)
{output_dir}/{feature}/outputs/reviews/prd/{date}{_counter}/ ← {review_outputs_dir}
├── summary.html ← {review_summary_html}
└── enhanced-prd.html ← {review_enhanced_html}
Where {output_dir} comes from .shield.json output_dir field (default docs/shield), {feature} is the feature folder ({feature-name}-YYYYMMDD), {date} is today's ISO date (YYYY-MM-DD), and {_counter} is empty for the first run of the day or _2, _3, ... on same-day collisions. Numbered-run subfolders (prd-review/{N}-{slug}/) are gone. Reviews never overwrite prior runs.
Resolving the counter: before writing, list {output_dir}/{feature}/reviews/prd/ for entries matching today's date. If {date}/ does not exist, use _counter="". Otherwise, find the highest {date}_<N>/ and use _counter="_<N+1>". Do NOT use any other path. The Write tool creates directories automatically.
What ships with it
18 files 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.
- dimensions.md 4.1 KB
- ingest.md 4.0 KB
- prompts/gtm-customer-comms.md 3.5 KB
- prompts/legal-privacy-compliance.md 3.2 KB
- prompts/measurable-success.md 2.8 KB
- prompts/problem-clarity.md 3.1 KB
- prompts/raci-and-approvals.md 2.8 KB
- prompts/risks-and-assumptions.md 2.5 KB
- prompts/scope-discipline.md 3.0 KB
- prompts/support-cx-impact.md 3.2 KB
- prompts/why-now-cost-of-inaction.md 2.5 KB
- rubric.md 8.3 KB
- scoring.md 4.6 KB
- test-fixtures/.gitkeep 0 B
- test-fixtures/internal-tool.md 11 KB
- test-fixtures/lean-with-gaps.md 633 B
- test-fixtures/standard-with-gaps.md 9.6 KB
- test-fixtures/well-formed-standard.md 26 KB
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 · 254 lines · 80 tokens per session scan A 907cc990dd73
prd-review is a skill published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 80 tokens to every session and 3,366 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-09-03.
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…
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…