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/ahostbr/kuroryuu-publicWrote 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/ahostbr/kuroryuu-public/prd-validator)<a href="https://agentmods.dev/agents/ahostbr/kuroryuu-public/prd-validator"><img src="https://agentmods.dev/badge/agents/ahostbr/kuroryuu-public/prd-validator/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/agents/ahostbr/kuroryuu-public/prd-validator"><img src="https://agentmods.dev/badge/agents/ahostbr/kuroryuu-public/prd-validator.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.00009 | $0.00484 |
| Opus 5 | $0.00005 | $0.00242 |
| Sonnet 5 | $0.00002 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
prd-validator 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 10d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 10d ago First seen · 106 lines · 9 tokens per session scan A cfa6a63845f6
prd-validator is an agent published in the GitHub repository ahostbr/kuroryuu-public (12 stars, last pushed 5mo ago), licensed AGPL-3.0. It adds 9 tokens to every session and 484 once invoked, about $0.0000 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-09-02.
Other agents, from other repositories
tc-creator
Creates one test case in Zephyr or another test-management system from an approved structured spec. Use for bulk TC creation by spawning one independent specialist per TC.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.
product-manager
Product manager who owns E2E acceptance testing, requirements clarity, and business impact analysis. Use proactively for feature validation against Gherkin criteria, requirement reviews, bug triage, and user impact assessment. MANDATORY reviewer after /smith.specify, during /smith.clarify, and owns E2E testing after…
jira-task-runner
Drive any tracker ticket end-to-end from a link — access preflight, defect-or-change classification, reproduction or test-first evidence, delegated fix/implementation, evidence comment, QA transition.
sprint-closeout-auditor
Sprint closeout validation specialist. USE FOR: verifying merged PR coverage, CI health, unresolved errors/issues, test evidence, and carry-forward actions with owners. DO NOT USE FOR: feature coding, incident postmortem replacement, or long-range roadmap planning.