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/setrathexx/codex-engineering-workflow-pack/to-prdnpx skills add SetraTheXX/Codex-Engineering-Workflow-Pack --skill to-prdgit clone --depth 1 https://github.com/SetraTheXX/Codex-Engineering-Workflow-PackWrote 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/setrathexx/codex-engineering-workflow-pack/to-prd)<a href="https://agentmods.dev/skills/setrathexx/codex-engineering-workflow-pack/to-prd"><img src="https://agentmods.dev/badge/skills/setrathexx/codex-engineering-workflow-pack/to-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 | $0.00049 | $0.00949 |
| Opus 5 | $0.00024 | $0.00475 |
| Sonnet 5 | $0.00010 | $0.00190 |
| Haiku 4.5 | $0.00005 | $0.00095 |
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 4d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To PRD
Turn the current context into a product requirements document that can drive issues, prototypes, tests, and implementation.
Do not start a new interview by default. Synthesize what is already known, then ask only for critical missing product decisions.
Read First
Gather context from:
- current conversation,
- clarified plan from
grill-with-docsif present, docs/agents/domain.md,CONTEXT.md,- relevant ADRs under
docs/adr/, - existing plans, specs, and README files,
- relevant code only when needed to avoid stale assumptions.
If setup docs exist, read:
docs/agents/issue-tracker.mddocs/agents/test-commands.md
Output Location
Default to a local markdown PRD.
Recommended locations, in order:
docs/agents/prds/<slug>.mddocs/prds/<slug>.mddocs/<slug>-prd.md
If the repo already has a PRD convention, use it.
Before writing any file:
- propose the target path,
- summarize what will be written,
- ask for approval.
GitHub or remote issue publishing is optional and requires explicit user request.
Workflow
1. Identify Source Material
State what input the PRD is based on.
Examples:
- conversation context,
- clarified plan,
- existing issue,
- design note,
- prototype finding,
- repo docs.
If the source is too thin, ask the smallest question that unlocks the PRD.
2. Synthesize Product Intent
Write a short internal summary before drafting:
- problem,
- target users or actors,
- desired outcome,
- core behavior,
- constraints,
- known non-goals.
Use domain language from repo docs.
3. Check Implementation Reality
Do a light repo check when implementation assumptions matter.
Look for:
- existing modules or routes,
- similar features,
- test locations,
- API or CLI surfaces,
- constraints from ADRs.
Do not turn the PRD into a file-by-file implementation plan. Keep code paths out unless they are essential context.
4. Ask Only Critical Questions
Ask when a missing answer would make the PRD misleading.
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.
- 4d ago First seen · 198 lines · 49 tokens per session scan A 38a6f7fb2438
to-prd is a skill published in the GitHub repository SetraTheXX/Codex-Engineering-Workflow-Pack (1 stars, last pushed 4d ago), licensed MIT. It adds 49 tokens to every session and 949 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.
Other skills, from other repositories
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
hns-workflow-ci-loop
Unified CI watch + auto-fix loop skill. Polls gh pr checks after /moai sync PR creation, classifies required vs auxiliary failures, attempts safe automated patches (max 3 iterations), and escalates semantic failures to the user. Use for CI loop workflow — NOT for general loop iteration patterns (see…
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
moai-harness-learner
Harness learning subsystem coordinator. Produces Tier 4 auto-update proposal payloads consumed by the orchestrator (which surfaces them via AskUserQuestion) and orchestrates Apply/Rollback flows. Triggers when harness learning proposals are pending or learning lifecycle management is needed.
moai-workflow-thinking
Sequential Thinking MCP for structured step-by-step analysis via --deepthink flag. Separate from UltraThink which is Claude's native extended reasoning mode. Use for multi-step analysis or architecture decisions.