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/jikig-ai/soleur/code-to-prdnpx skills add jikig-ai/soleur --skill code-to-prdgit clone --depth 1 https://github.com/jikig-ai/soleurWrote 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/jikig-ai/soleur/code-to-prd)<a href="https://agentmods.dev/skills/jikig-ai/soleur/code-to-prd"><img src="https://agentmods.dev/badge/skills/jikig-ai/soleur/code-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.1 | $0.00050 | $0.01097 |
| Opus 5 | $0.00025 | $0.00549 |
| Sonnet 5 | $0.00010 | $0.00219 |
| Haiku 4.5 | $0.00005 | $0.00110 |
Grade A, and why
code-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 yesterday.
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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
10 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.
- references/banner-template.md 2.0 KB
- references/prd-template.md 2.2 KB
- scripts/code-to-prd.sh 21 KB runs code
- test/code-to-prd.test.sh 12 KB runs code
- test/fixture/.env.example 494 B
- test/fixture/app/about/page.tsx 254 B
- test/fixture/app/api/health/route.ts 309 B runs code
- test/fixture/app/page.tsx 326 B
- test/fixture/next.config.mjs 91 B runs code
- test/fixture/package.json 413 B
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.
- yesterday First seen · 59 lines · 50 tokens per session scan A 4147d7dc04a2
code-to-prd is a skill published in the GitHub repository jikig-ai/soleur (15 stars, last pushed yesterday), with no licence file. It adds 50 tokens to every session and 1,097 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
flow-parallel
Decompose and execute large changes, migrations, or multi-issue fixes in parallel with quality gates.
skill-parallel-agents
Decompose large tasks across parallel agents — use for migrations, multi-file refactors, or batch work.
skill-iterative-loop
Run tasks in a loop until goals are met — use for iterative refinement, polling, or convergence.
skill-debug
Debug issues methodically — use when stuck on errors, test failures, or unexpected behavior.
skill-issues
Track project blockers, bugs, and gaps across sessions — use when issues pile up or need triage.
skill-thought-partner
Brainstorm creatively with pattern spotting and paradox hunting — use for ideation and exploration.