goal-completion-check

A completion checklist for coding-agent goals. It checks the written requirements, verification result, and test record before a goal is marked finished.

In plain words
What is it for?
Use it before closing an implementation task to confirm that the verifier passed, tests ran, and the GOAL.md checklist is complete.
Why use it?
It prevents work from being marked complete based only on a belief that it should work. Missing checks or unfinished checklist items are surfaced first.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/cobusgreyling/goal-engineering/goal-completion-check
Any agent
npx skills add cobusgreyling/goal-engineering --skill goal-completion-check
Clone the repo
git clone --depth 1 https://github.com/cobusgreyling/goal-engineering

Made for: Claude Code, Codex.

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 211 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured yesterday against content hash 9dd921a3f880, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.grok/skills/goal-completion-check/SKILL.md · 25 lines

What it actually says

Goal Completion Check

Gate before update_goal(completed: true).

Steps

  1. Read GOAL.md done condition — count unchecked items.
  2. Confirm goal-verifier (or equivalent) returned PASS this session.
  3. Confirm test command was run and output captured in progress log.
  4. If any gap → do not complete; list remaining work and call update_goal(message: ...).
  5. 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.
Changes

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.

  1. yesterday First seen · 25 lines · 52 tokens per session scan A 9dd921a3f880

Subscribe to this mod's changes

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.

Related

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.

jinxlzc/grok-codex-plugin · 82 tokens

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…

Walvez/grok-subagent · 112 tokens

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…

Sunwood-ai-labs/delegate-to-grok-skill · 74 tokens

grok-prompting

Internal guidance for composing Grok Build prompts for coding, review, diagnosis, and research tasks inside the Grok Claude Code plugin.

davit-khaburdzania/grok-plugin-cc · 31 tokens

grok-cli-runtime

Internal helper contract for calling the grok-companion runtime from Claude Code.

davit-khaburdzania/grok-plugin-cc · 19 tokens

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…

conrad85/grok-bridge · 90 tokens