prd_analyst

A requirements analyst for product requirements documents (PRDs), which describe what a product should do. It extracts organised requirements and compares them with designs and API contracts, the agreements that define how software parts communicate.

In plain words
What is it for?
Use it to turn PRDs into structured requirements and find gaps between the PRD, interface designs, and API definitions.
Why use it?
It helps reveal missing, unclear, or conflicting expectations between product, design, and engineering documents. Finding these mismatches early can prevent teams from building different interpretations of the same feature.

Agent

Install

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.

agentmods
npx agentmods add agents/zebbern/termstack/prd_analyst
Clone the repo
git clone --depth 1 https://github.com/zebbern/termstack
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,204 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00031 $0.01204
Opus 5 $0.00015 $0.00602
Sonnet 5 $0.00006 $0.00241
Haiku 4.5 $0.00003 $0.00120

Measured yesterday against content hash 909a8dbca1a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

prd_analyst 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 yesterday.

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.

.github/agents/prd_analyst.agent.md · 114 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. yesterday First seen · 114 lines · 31 tokens per session scan A 909a8dbca1a6

Subscribe to this mod's changes

prd_analyst is an agent published in the GitHub repository zebbern/termstack (5 stars, last pushed 4mo ago), with no licence file. It adds 31 tokens to every session and 1,204 once invoked, about $0.0002 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-31.