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 skills add rengwu/iudex --skill to-prdgit clone --depth 1 https://github.com/rengwu/iudexWrote 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/rengwu/iudex/to-prd)<a href="https://agentmods.dev/skills/rengwu/iudex/to-prd"><img src="https://agentmods.dev/badge/skills/rengwu/iudex/to-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/skills/rengwu/iudex/to-prd"><img src="https://agentmods.dev/badge/skills/rengwu/iudex/to-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.00048 | $0.01460 |
| Opus 5 | $0.00024 | $0.00730 |
| Sonnet 5 | $0.00010 | $0.00292 |
| Haiku 4.5 | $0.00005 | $0.00146 |
Grade A, and why
to-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 9d 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
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.
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.
- 9d ago First seen · 114 lines · 48 tokens per session scan A e4e3e1b02206
to-prd is a skill published in the GitHub repository rengwu/iudex (15 stars, last pushed 2mo ago), with no licence file. It adds 48 tokens to every session and 1,460 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-30.
Other skills, from other repositories
b3os-team-inbox
A team message-bus client for sending, receiving, and recalling messages between AI teammates. It also supports replying to a specific message thread and sending final reports to the team lead.
b3os-task-loop
A task-tracking work loop that keeps individual, scheduled, and waiting tasks moving until they are completed, blocked, or awaiting approval.
factory-handoff
Hand one exact agent-ready ticket to the central Factory runtime over the configured SSH forced-command boundary. Use when an operator asks to hand off an existing ticket or a prose request instead of implementing it in the current session.
b3os-task-mgmt
A deprecated compatibility stub that points users to b3os-task-loop, the newer source for task boards, execution mode, handoffs, continuation checks, review waiting, and scheduled work.
ticket-spec
Turn a raw Linear Triage ticket into a fully specified ai:agent-ready one by exploring the codebase. Use when specifying, refining, or promoting tickets, or when asked why a ticket isn't dispatchable.
setup
Configure or diagnose Hames in the current project when the user invokes /setup.