Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add yonatangross/orchestkit/plugin install orkWrote 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/commands/yonatangross/orchestkit/prd-to-goal)<a href="https://agentmods.dev/commands/yonatangross/orchestkit/prd-to-goal"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/prd-to-goal/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/commands/yonatangross/orchestkit/prd-to-goal"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/prd-to-goal.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.00055 | $0.03074 |
| Opus 5 | $0.00028 | $0.01537 |
| Sonnet 5 | $0.00011 | $0.00615 |
| Haiku 4.5 | $0.00006 | $0.00307 |
Grade A, and why
prd-to-goal scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl -sf $URL` returns 2xx How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-generated from skills/prd-to-goal/SKILL.md
Source: https://github.com/yonatangross/orchestkit
/ork:prd-to-goal — PRD → /goal Decomposition
Converts a PRD / issue / spec into a single copy-pasteable /goal line. The hard part of /goal is not running it — it is writing an until clause that is convergent (terminates), falsifiable (testable boolean), and observable (the agent can actually check it without subjective judgement). This skill makes that decomposition reproducible.
1. When to use
Use it when:
- You have a written PRD, GitHub issue, or spec and want to run
/goalagainst it. - Past
/goalruns drifted, looped, or burned tokens because theuntilclause was vague (until tests pass,until done,until design is good). - You need to justify the abort budget — turns, tokens, no-progress threshold.
Skip it when:
- One-shot bug fix where the failing test is the acceptance criterion. Just run
/goal until pnpm test -- auth.spec.ts passes. - No written PRD exists. Run
/ork:write-prdfirst — vibes do not decompose. - The work is destructive or irreversible (DB migrations, mass file deletes).
/goalretries; you do not want retries onDROP TABLE.
2. Inputs the skill accepts
| Input | How |
|---|---|
| Pasted PRD text | Provide as the argument, or paste into the chat after invoking. |
| GitHub issue | gh issue view <N> --json title,body,labels — the skill reads body. |
| Spec file | Path to a Markdown / text file; the skill Reads it. |
| ADR / design doc | Same as spec file. |
3. The decomposition algorithm
- Extract acceptance criteria. Pull every
MUST,SHOULD,Definition of Done,Acceptance Criteria, and checkbox-style line. If the doc has none, stop and tell the user to run/ork:write-prdfirst — there is nothing to converge on. - Map each criterion to an observable boolean. Each criterion must reduce to a single shell-checkable assertion. Examples of observable state:
test -f path/to/file(file exists)pnpm test -- pattern passes(test command exits 0)gh pr view <N> --json state | jq -r .state == "MERGED"wc -l < src/auth.tsreturns a number within boundpnpm lintexits 0curl -sf $URLreturns 2xx
- Reject non-observable criteria. Drop or rewrite criteria that depend on subjective judgement (
code is clean,design feels right,users are happy). Either find a proxy (lint exits 0,Lighthouse score > 90,NPS survey ID exists) or surface the criterion back to the user as out of scope for/goal. - Compose the
untilclause. AND-join the observable assertions in priority order — the cheapest, most likely-to-fail check first so the loop short-circuits early. Three to five assertions is the sweet spot; more than seven usually means the PRD is two PRDs. - Fold the budget INTO the same condition. Claude Code accepts one goal per
session, replace-on-set, and the bound is written inside that single condition
(
…, or stop after 15 turns). It is not a second command. Sensible turn caps:15for a single feature,30for a refactor,5for a bug fix.
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 · 211 lines · 55 tokens per session scan A e113cd8b50d4
prd-to-goal is a command published in the GitHub repository yonatangross/orchestkit (231 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 3,074 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
compact-prep
Ask the agent to prepare for conversation compaction by updating any relevant state and providing guidance for the compaction agent and to kick off the session there after.
reset-handoff
Reset the agent handoff system by cleaning up state files and logs.
bug
Reproduce then TDD-fix a ready-for-agent bug ticket in this checkout. Web bugs get a browser repro first.
pn-distill
Remove content, sections, and features that don't earn their place — information architecture reduction. Use when there's too much stuff on the page. For visual decoration reduction, use pn-quieter.
pn-bolder
Amplify a timid, safe, or generic design — more visual weight, stronger personality, clearer point-of-view. Use when the design is technically correct but forgettable.
distil-shadow
Decision-equivalence report — did compression preserve your agent's next action?