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 orlando-japan/claude-code-setting --skill goal-driven-executiongit clone --depth 1 https://github.com/orlando-japan/claude-code-settingWrote 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/orlando-japan/claude-code-setting/goal-driven-execution)<a href="https://agentmods.dev/skills/orlando-japan/claude-code-setting/goal-driven-execution"><img src="https://agentmods.dev/badge/skills/orlando-japan/claude-code-setting/goal-driven-execution/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/orlando-japan/claude-code-setting/goal-driven-execution"><img src="https://agentmods.dev/badge/skills/orlando-japan/claude-code-setting/goal-driven-execution.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.00033 | $0.00570 |
| Opus 5.5 | $0.00013 | $0.00228 |
| Sonnet 5.5 | $0.00007 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
goal-driven-execution 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 1mo 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.
- "…when `curl -X POST /api/user` with a missing name returns 400 with `{error: 'name required'}`." How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal-driven execution
Most "done" declarations are premature because the definition of done was vague. This skill forces a concrete check up front.
Protocol
Step 1 — Write the verification before the code.
Phrase it as: "I will know this is done when <command> produces <output>."
Examples:
- "…when
pnpm test path/to/user.test.tsexits 0 and shows 'handles empty input' passing." - "…when visiting http://localhost:3000/settings as a logged-out user redirects to /login with
?return_to=/settings." - "…when
curl -X POST /api/userwith a missing name returns 400 with{error: 'name required'}." - "…when
git log --oneline -5shows 5 commits all tagged with[auth-v2]."
If you can't state a verification, the task isn't clear enough — ask the user before coding.
Step 2 — Code.
Step 3 — Run the exact verification you wrote.
Not a proxy, not "the type checker is happy," not "it compiled." The literal command from step 1.
Step 4 — If it fails, iterate. Diagnose the gap, fix, re-run. Don't declare done with "it should work now."
Step 5 — If it passes, state it explicitly with the command and its output in the message back to the user. This gives the user evidence, not a claim.
For UI work
The verification must include actually opening a browser and exercising the feature:
- Golden path: the main user flow, click-through.
- At least one edge case: empty state, error state, or boundary input.
If you can't run a browser in the current environment, say so explicitly. Claiming success on unverified UI is the worst outcome.
For bug fixes
- Verification = the reproduction command fails before the fix and passes after.
- No reproduction = no fix, it's a guess.
- Reproduce first, fix second, confirm third.
Anti-patterns
- "Tests should pass now." Run them.
- "Based on my analysis it works." Evidence over analysis.
- Type check as verification. Type check is necessary, not sufficient.
- Declaring done when you hit the first green. Run the full verification list, not just the one test you touched.
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.
- 1mo ago First seen · 60 lines · 33 tokens per session scan A 7ae2fe9c24fd
goal-driven-execution is a skill published in the GitHub repository orlando-japan/claude-code-setting (2 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 570 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
Effective Memory
The essential habits for an AI agent with memory — session bookends, learning triggers, verification, safety, and the operational discipline that turns raw recall into compounding intelligence. Keyword-matched after installation.
parallel-yak-implementation
Use when multiple independent leaf yaks are ready to implement and can be worked on concurrently with separate agents in worktrees.
openspec-plus-tdd
MANDATORY skill that activates whenever code is written to implement an OpenSpec change task. Triggers: openspec-plus-apply is active, /opsx-apply is running, the user is implementing tasks from an OpenSpec change, an implementer subagent dispatched by openspec-plus-apply is starting work, or the user invokes phrases…
verify-before-done
Proves work with tests, diffs, and logs before sign-off.
PlanGate TDD Evidence Review
A checker for TDD evidence. TDD, or test-driven development, means writing a failing test before the implementation, making it pass, and then improving the code; this checker verifies records of those stages.