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/cobusgreyling/goal-engineering/goal-completion-checknpx skills add cobusgreyling/goal-engineering --skill goal-completion-checkgit clone --depth 1 https://github.com/cobusgreyling/goal-engineeringWhat 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 | $0.00052 | $0.00211 |
| Opus 5 | $0.00026 | $0.00105 |
| Sonnet 5 | $0.00010 | $0.00042 |
| Haiku 4.5 | $0.00005 | $0.00021 |
Grade A, and why
goal-completion-check 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.
What it actually says
Goal Completion Check
Gate before update_goal(completed: true).
Steps
- Read
GOAL.mddone condition — count unchecked items. - Confirm
goal-verifier(or equivalent) returned PASS this session. - Confirm test command was run and output captured in progress log.
- If any gap → do not complete; list remaining work and call
update_goal(message: ...). - If all clear → call
update_goal(completed: true, message: "<summary>").
Never
- Complete on "should work" or partial test runs.
- Complete when deny-listed files were modified without human approval.
- Complete when verifier was skipped.
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 · 25 lines · 52 tokens per session scan A 9dd921a3f880
goal-completion-check is a skill published in the GitHub repository cobusgreyling/goal-engineering (39 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 211 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-08-30.
Other skills, from other repositories
codex-delegate
Delegate coding, review, diagnosis, or follow-up work to the local Codex CLI from Grok Build. Use when the user asks to command Codex, hand work to Codex, run /codex, /codex:rescue, /codex:review, or says 让 Codex 干、叫 Codex 审查、 指挥 Codex.
grok-subagent
Delegate bounded coding, investigation, review, implementation, and real-time X/Reddit/web research tasks from Codex to the locally authenticated Grok Build CLI. Use when the user asks Codex to consult Grok, use Grok as a subagent, compare independent model conclusions, spend SuperGrok quota on useful project work…
delegate-to-grok
Delegate coding, repository inspection, comparisons, web research, and public X search from Codex to the locally installed Grok Build CLI on Windows. Use when a user asks to run or consult Grok, resume Grok Build authentication, compare Codex and Grok, inspect or modify a project with Grok, or perform public X…
grok-prompting
Internal guidance for composing Grok Build prompts for coding, review, diagnosis, and research tasks inside the Grok Claude Code plugin.
grok-cli-runtime
Internal helper contract for calling the grok-companion runtime from Claude Code.
grok-bridge
Delegate any substantial local task to Grok Build as one durable logical job, in a repository or a non-repository workspace, and retrieve its genuine final result across turn, token, context, and caller-session boundaries. Use when the user asks for Grok/Grok Build, an independent builder/tester/reviewer/researcher…