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 agentmods add agents/vshidlovsky/prd-agents-framework/prd-smell-patternsgit clone --depth 1 https://github.com/vshidlovsky/prd-agents-frameworkWrote 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/agents/vshidlovsky/prd-agents-framework/prd-smell-patterns)<a href="https://agentmods.dev/agents/vshidlovsky/prd-agents-framework/prd-smell-patterns"><img src="https://agentmods.dev/badge/agents/vshidlovsky/prd-agents-framework/prd-smell-patterns.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02140 |
| Opus 5 | $0.00000 | $0.01070 |
| Sonnet 5 | $0.00000 | $0.00428 |
| Haiku 4.5 | $0.00000 | $0.00214 |
Grade A, and why
prd-smell-patterns 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 5d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requirements Smell Patterns
Canonical list of anti-patterns in requirements. Used by the PRD reviewer and its sub-agents when evaluating FR and AC quality.
Linguistic Smells
Source: Femmer et al., TU Munich, 2017 — adapted for PRD review.
- Vague verb: "handle", "manage", "process", "support", "deal with" — require a concrete verb (display, send, reject, store, calculate)
- Loophole: "if possible", "as appropriate", "when feasible", "as needed", "where applicable" — gives dev permission to skip
- Ambiguous pronoun: "it", "they", "this" without clear antecedent in same sentence
- Passive voice hiding actor: "is validated", "is shown" — WHO does it? The system, the API, the user?
- Open-ended list: "etc.", "and so on", "such as" used as substitute for a complete list
- Superlative/comparative: "fastest", "better", "optimal" — unmeasurable without baseline
- Incomplete conditional: "if X then Y" without specifying what happens when X is false
- Subjective language: "user-friendly", "intuitive", "clean", "simple", "seamless" — not testable
- Temporal comparison: "today the code does X", "currently", "legacy", "old implementation", "supersedes", "existing code", "key differences from current behavior", "this replaces the old" — the PRD describes WHAT TO BUILD, not what exists or what changed. If old artifacts need cleanup, that's a separate chore ticket, not PRD content.
- Implementation delegation: "via someFunction()", "using utilityName", "formatted by formatTime", "whatever X returns", "as returned by" — delegates the requirement to current code instead of defining expected behavior. Replace with the observable output (format, thresholds, concrete examples). This includes feature-layer utility function names (
getAvatarColor,formatPhone,parseAmount) — any function defined insrc/features/*/utils/,src/utils/, or shared utility modules that is not a public DS component prop or documented Web/Browser API. Describe the behavior observably and let the Component Mapping or implementation tickets resolve the utility. - Under-specified render: a display requirement that names a format but not its determinant — "locale-aware date" without a timezone, "formatted amount" without currency/minor-unit handling, "the list of X" without an ordering rule. The text reads as decided, so it draws no clarifying question, but two implementations will show different things to the customer. Require the determinant, not a longer format name.
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.
- 5d ago First seen · 37 lines · 0 tokens per session scan A fc1017647609
prd-smell-patterns is an agent published in the GitHub repository vshidlovsky/prd-agents-framework (4 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,140 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 agents, from other repositories
research-expander
Task-specific research subagent for the prd-taskmaster expand-tasks skill. Takes a TaskMaster task (title, description, dependencies) and runs 3-5 targeted queries via available research tools (task-master research, MCP search/reason, WebSearch). Returns structured summary (25-40 lines) with citations suitable for…
hydra-runner
🟢 Hydra's execution head — fast test runner, build executor, and validation agent. Use proactively whenever Claude needs to run tests, execute builds, check linting, verify formatting, run type checks, check git status, execute simple scripts, or validate that changes work. Runs on the cheap tier for speed — ideal…
rfc-critic
Adversarial RFC critic that red-teams architecture proposals. Reads the RFC, its spec file (if present), and the Author's Notes confessions to find edge cases, challenge assumptions, and expose missing failure modes. Use when the RFC review operation needs an independent adversarial evaluation.
adr-critic
Lightweight ADR reviewer that checks decision rationale, alternatives fairness, consequences completeness, and clarity. Reads Author's Notes as prioritized attack vectors. Use when the ADR review operation needs a quick quality check.
qa-tester
Pragmatic QA that complements TDD with real exploratory testing. Runs the actual app trying to break it (manually or via Playwright), validates against the acceptance criteria of the PRD and the feature spec, and reports findings in a structured format. Invoked between phases or before marking a feature as done. Does…
task-finder
Scan an ops project across 7 lenses (goal gaps, stale state, research, content, follow-through, hygiene, directions). Updates backlog.