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 commands/michelkerkmeester/skilled-agent-harness_spec-driven-loops/goal-opencodegit clone --depth 1 https://github.com/MichelKerkmeester/skilled-agent-harness_spec-driven-loopsWrote 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/michelkerkmeester/skilled-agent-harness_spec-driven-loops/goal-opencode)<a href="https://agentmods.dev/commands/michelkerkmeester/skilled-agent-harness_spec-driven-loops/goal-opencode"><img src="https://agentmods.dev/badge/commands/michelkerkmeester/skilled-agent-harness_spec-driven-loops/goal-opencode.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.00006 | $0.01449 |
| Opus 5 | $0.00003 | $0.00724 |
| Sonnet 5 | $0.00001 | $0.00290 |
| Haiku 4.5 | $0.00001 | $0.00145 |
Grade A, and why
goal-opencode 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 2d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/goal-opencode
Thin root router for the session goal plugin.
1. PURPOSE
Manage the passive session goal through the opencode-goal plugin. /goal-opencode is a state-free router: it resolves the requested action from $ARGUMENTS and dispatches to the opencode_goal / opencode_goal_status plugin tools, which own all goal state and session resolution.
2. ARGUMENT ROUTING
Resolve routing inputs from the command arguments $ARGUMENTS:
QUERY= the full$ARGUMENTSstring, trimmed.ARGS_PRESENT= true whenQUERYis non-empty.FIRST= the first whitespace-delimited token ofQUERY, lowercased.REST=QUERYwith the leadingFIRSTtoken removed, trimmed.
Bind routing to these resolved ARGS_PRESENT, QUERY, FIRST, and REST values.
3. CONTRACT
Inputs: $ARGUMENTS — set <objective> [--budget N] | show | history | doctor | health | clear | complete | pause [reason] | resume
Outputs: STATUS=<OK|FAIL> ACTION=<set|clear|complete|pause|resume|history|doctor|health|show>
This command is state-free. It never reads or writes .opencode/skills/.state/goal directly.
- Empty arguments or
showroute toopencode_goal_status. set <objective> --budget Nroutes toopencode_goalwithaction: "set",objectivewith the budget suffix removed, andtokenBudget: N.set <objective>routes toopencode_goalwithaction: "set"andobjective: REST.- Bare text routes to
opencode_goalwithaction: "set"andobjective: QUERY. history,doctor, andhealthroute to read-onlyopencode_goalactions.historyreturnsarchive_countandarchive_N_*fields.doctor/healthreturnactive_state_file_count,archive_file_count, log byte sizes,last_sweep_at, andorphan_candidate_count.clear,complete,resume, andpause [reason]route toopencode_goal.- Any other non-empty
QUERYis treated as bare goal text and routes toopencode_goalwithaction: "set"andobjective: QUERY.
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.
- 2d ago First seen · 101 lines · 6 tokens per session scan A 9481473d44a9
goal-opencode is a command published in the GitHub repository MichelKerkmeester/skilled-agent-harness_spec-driven-loops (34 stars, last pushed today), licensed MIT. It adds 6 tokens to every session and 1,449 once invoked, about $0.0000 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-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.