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/infraspecdev/tesseractWrote 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/infraspecdev/tesseract/prd)<a href="https://agentmods.dev/commands/infraspecdev/tesseract/prd"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/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/infraspecdev/tesseract/prd"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/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.00086 | $0.00894 |
| Opus 5.5 | $0.00034 | $0.00358 |
| Sonnet 5.5 | $0.00017 | $0.00179 |
| Haiku 4.5 | $0.00009 | $0.00089 |
Grade A, and why
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 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/prd
Author a PRD interactively. Walks the user through the scaffold; invokes shield:story-coverage for story scaffolding; writes prd.md, prd.html, prd.meta.json.
Usage
/prd # interactive — prompts for everything
/prd <topic> # uses topic as seed for Problem / feature name
/prd --feature <name> # explicit feature folder
Paths
| Registry key | Resolved path |
|---|---|
prd |
{output_dir}/{feature}/prd.md |
prd_html |
{output_dir}/{feature}/outputs/prd.html |
prd_meta_json |
{output_dir}/{feature}/prd.meta.json |
prd.meta.json is the PRD metadata sidecar (status, sections present, linked plans). /plan later updates the linked_plans field when it generates a plan against this PRD.
What it does
- Reads
.shield.jsonforprd_template(custom team template path, optional) - Resolves feature folder —
--featureflag or current context - Detects prior lean PRD in the folder — if present, offers upgrade flow (multi-select of standard sections to add)
- Asks for PRD type — standard (20 sections) or lean (10 sections)
- Pre-populates from prior
/researchtranscript if present - Walks Section 1 (Header) — defers Section 2 (Terminologies) for now
- Walks Sections 3, 4 (Problem, Personas), then Section 5 (Architecture & flows — optional Mermaid), then Section 6 (Goals)
- Invokes
shield:story-coveragebetween Sections 6 and 8 — scaffolds expected stories (standard only — lean skips story-coverage) - Walks Section 7 (Metrics); for standard, also walks Section 8 (Stories — prompts each story for Type: new | enhancement | existing)
- Walks Sections 9..14 (Functional through Assumptions) (standard only)
- Invokes
shield:milestone-coveragebetween Sections 8 and 15 — scaffolds Milestones into §15 (or §8 for lean) - Walks Section 15 rollout-mechanics, then Sections 16..20 (standard only — lean walks §9 Open questions, §10 Out of scope)
- Builds Terminologies (§2) — copies from research-transcript glossary, proposes terms via LLM scan of drafted body, user confirms
- Merges custom template if configured
- Writes
prd.md,prd.html(rendered via Shield's renderer — includes auto-TOC + Mermaid rendering),prd.meta.json
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 · 66 lines · 86 tokens per session scan A b8fa9167b285
prd is a command published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 86 tokens to every session and 894 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 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.