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 skills/ulises-jeremias/agent-toolkit/prdnpx skills add ulises-jeremias/agent-toolkit --skill prdgit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/prd)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/prd"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/prd.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.1 | $0.00054 | $0.00633 |
| Opus 5 | $0.00027 | $0.00316 |
| Sonnet 5 | $0.00011 | $0.00127 |
| Haiku 4.5 | $0.00005 | $0.00063 |
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 2d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD — Product Requirements (WHAT)
Template: references/default-template.md — local reference, kept up to date with the standard structure.
Default guardrails (before any final content)
- Apply
output-handshake: confirm where the final PRD will be stored (path, Doc page, task, paste-only, etc.) and that a human will review. Engagements may store PRDs in different places; do not assume. - Then follow the steps below.
When to use
- A feature or product increment needs a shared agreement on scope, users, and acceptance.
- The team must trace work from PRD → implementation → tests.
- An engagement uses an Operations-style doc hub with linked requirements documents.
Instructions
- Open the PRD template (
references/default-template.md) and keep section headings aligned with it: Objective, User flow / Personas, Entities & use cases, Acceptance criteria, Edge cases, Integrations, Timeline, Approvals. - For discovery in an existing repository, delegate repository inspection to
assistant; citeAGENTS.mdand test/lint commands from the project. - Acceptance criteria must be testable and in English for work items/PRs (match
workflow-generic-project). - Link stakeholder approval to your engagement process (task lists, doc pages, or client sign-off). Do not invent sign-off if not agreed.
- For ticket updates, use the appropriate tool (
clickup-cli,jira-*, etc.) to post a short plan comment or attach links — do not paste the full document into a task; link the Doc or page when possible.
What not to do
- Do not copy the full text of an external template into this skill; use
references/default-template.mdas the local canonical reference. - Do not skip edge cases or integrations when the PRD is meant for handoff to a TRD.
References
output-handshake— destination and review (required first for final output)references/default-template.md— local PRD templatereferences/example-unified-api.md— PRD example for an API strategy initiativeworkflow-generic-project— delivery phases and ticket traceabilitytrd— next step for technical design from an approved PRDplanning— estimation and capacity before commitmentepic,user-story,task— downstream breakdownclickup-cli,jira-*— ticket / comment operations (per engagement)
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 47 lines · 54 tokens per session scan A 0d93a06db51f
prd is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 633 once invoked, about $0.0003 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-04.
Other skills, from other repositories
unity-bridge
Remote-control Unity Editor via file-based IPC — 65 tools covering scene management, GameObject/component CRUD, asset operations, prefab editing, script execution, profiling, light probes, screenshot, runtime query/invoke, package management, and more.
verify
Fact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.
expert
Base expert skill.
iblai-api-catalog-media
Manage an ibl.ai organization's catalog media resources via the Data Manager API — videos, images, documents, audio, and external links attached to a course, unit, or resource (item). Per-org, per-user CRUD plus search and by-item lookup, with multipart file upload. Use when attaching media to course/unit/resource…
iblai-api-agent-safety
Configure an ibl.ai agent's moderation and safety systems via the platform API — enable flags, system prompts and responses (saved through the agent settings endpoint) — and review or delete flagged-prompt moderation logs. Use when setting guardrails or auditing flagged content.
iblai-api-agent-skill
Manage an ibl.ai agent's skills via the platform API — browse the org skill catalog, assign/unassign skills to an agent, and create/edit/delete catalog skills. Requires a connected sandbox. Use when giving an agent reusable skill instructions.