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 melodic-software/claude-code-plugins/plugin install planningWrote 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/melodic-software/claude-code-plugins/draft-goal-condition)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/draft-goal-condition"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/draft-goal-condition/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/melodic-software/claude-code-plugins/draft-goal-condition"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/draft-goal-condition.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.00211 | $0.02666 |
| Opus 5.5 | $0.00084 | $0.01066 |
| Sonnet 5.5 | $0.00042 | $0.00533 |
| Haiku 4.5 | $0.00021 | $0.00267 |
Grade A, and why
draft-goal-condition 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 27d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Variables
Arguments: $ARGUMENTS. The natural-language intent for the autonomous run, plus any constraints or bounds the user volunteers.
Purpose
Turn a stated intent into a paste-ready /goal <condition> string that conforms to the shape the official Claude Code docs prescribe and provably fits the documented character limit. A language model cannot reliably count characters, so length conformance is decided by a deterministic counter, not by estimation.
The /goal contract, its condition shape and its character limit, can change between Claude Code versions. This skill therefore reads the current official docs at authoring time and never bakes those values into its own text. The number you see in a doc today is not a constant to memorize.
Step 0. Lever fit (is /goal even the right tool?)
/goal starts the next turn when the previous one finishes and stops when a fresh evaluator model confirms a completion condition holds. Before authoring, confirm that fits the intent. If it does not, route instead of drafting:
- Interval-driven ("every 5 minutes", "poll until") →
/loop(a time interval starts each turn), not/goal. - Cloud / sessionless / scheduled ("nightly", "each morning", runs with no session open) → routines /
/schedule. Routines were labeled a research preview onhttps://code.claude.com/docs/en/routinesas of 2026-09-02; re-read that label during the Step 1 fetch before recommending them. - Custom per-turn logic across all sessions (deterministic script check, settings-scoped) → a prompt-based Stop hook.
- More agents than one conversation can coordinate (or the orchestration is worth codifying as a rerunnable script) → a dynamic workflow. Unlike the rows above, this one is not exclusive of
/goal: a workflow decides how a single task fans out,/goaldecides when to stop turning, and the two compose. The goal sets the hard completion requirement while the workflow performs the parallel work. Route away from drafting only when the intent wants the fan-out and no across-turn completion condition; when it wants both, draft the condition here and say the workflow rides alongside it. - One-shot (a single prompt with no across-turn continuation) → just prompt; no goal.
- Multi-window / multi-ticket ("keep several sessions going", work that will not finish in one context window, a decomposed backlog) → when
work-itemsis installed: already-decomposed backlog / existing tickets →/work-items:work(or the work-loop); undecomposed plan or intent →/work-items:decomposethen/work-items:work. Whenwork-itemsis not installed, tell the user to install it. Or proceed to draft only if they insist on one-session completion./goalkeeps one session turning; a single goal-pursuing window relies on auto-compaction and spends most of its life degraded, while decomposed items each get a fresh window. Advisory routing default, not a prohibition. Proceed to draft when the intent is genuinely one-session completion.
What ships with it
1 file 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.
- 27d ago Changed 86125f26d983
- 1mo ago Changed · -11 tokens per session 89d7ce600aa8
- 1mo ago First seen · 102 lines · 222 tokens per session scan A 375d4da1d7f5
draft-goal-condition is a skill published in the GitHub repository melodic-software/claude-code-plugins (26 stars, last pushed today), licensed MIT. It adds 211 tokens to every session and 2,666 once invoked, about $0.0008 per session on Opus 5.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-03.
Other skills, from other repositories
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
parallel-worker
Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.
optimize-local-search
For NP-hard optimization: TSP, scheduling, assignment problems. Uses greedy construction + local improvement (2-opt, hill climbing).
solve-constraint-puzzle
For constraint satisfaction: Sudoku, scheduling, N-queens, logic puzzles, SAT-like problems, assignment problems. Uses propagate-then-search pattern.
test-with-examples
For example-driven development: test cases as specifications, input/output pairs, documentation through examples.
validate-before-process
For input validation: check format and constraints before processing, fail fast with clear errors, defensive parsing.