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 cckyros/goal-acceptance --skill can-complete-goalgit clone --depth 1 https://github.com/cckyros/goal-acceptanceWrote 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/cckyros/goal-acceptance/can-complete-goal)<a href="https://agentmods.dev/skills/cckyros/goal-acceptance/can-complete-goal"><img src="https://agentmods.dev/badge/skills/cckyros/goal-acceptance/can-complete-goal/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/cckyros/goal-acceptance/can-complete-goal"><img src="https://agentmods.dev/badge/skills/cckyros/goal-acceptance/can-complete-goal.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.00027 | $0.00335 |
| Opus 5 | $0.00014 | $0.00168 |
| Sonnet 5 | $0.00005 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
can-complete-goal 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 12d 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.
What it actually says
Before concluding a goal, call this to verify that all required
acceptance criteria are formally passed. Returns { allowed, reason? }:
- allowed: true — all required criteria are formally passed
- allowed: false — one or more required criteria are unresolved or self-claimed
Blocking Conditions
| Criterion State | Blocks completion? |
|---|---|
passed + selfClaimed=false |
No — formal pass |
passed + selfClaimed=true |
Yes — needs confirm_criterion |
failed |
Yes |
blocked |
Yes |
pending |
Yes |
in_progress |
Yes |
not_run |
Yes (required only) |
Self-Claimed Blocking
When role=agent (default), validate_criterion with passed marks the
criterion as selfClaimed=true. The completion gate treats self-claimed
required criteria as unresolved — they must be confirmed by an independent
reviewer via confirm_criterion before the goal can complete.
This prevents the agent from declaring "done" based on its own self-assessment without independent verification.
Do Not Declare Complete
Do not tell the user the task is complete until this check returns
allowed: true. If it returns allowed: false, read the reason field
and address each blocking criterion.
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.
- 12d ago First seen · 40 lines · 27 tokens per session scan A f1a43831be3a
can-complete-goal is a skill published in the GitHub repository cckyros/goal-acceptance (3 stars, last pushed 15d ago), licensed MIT. It adds 27 tokens to every session and 335 once invoked, about $0.0001 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-31.
Other skills, from other repositories
dsh-web-skin-developer
Build a new skin for the dsh-web skin collection (DSH Web GUI) and publish it into the Skin Center — the first-level settings section — scaffold with scripts/dsh-skin-new, author the v2 skin.json manifest plus skin.css token remap (pure asset directory, no package.json, no build step), validate with scripts/dsh-skin…
manage-taskboard
Manage work in the native DeepSeek Harness Taskboard with exact task ids and optimistic versions. Use when an Agent must inspect project work, claim an eligible todo, record progress or blockers, verify an implementation, submit it for human review, or release its own claim; also use when a human asks how to accept…
yao-ocr
OCR text recognition expert. ALWAYS invoke this skill when you need to extract text from images or PDFs — including invoices, receipts, ID cards, bank cards, business licenses, tables, handwritten documents, or any visual text content.
yao-workspace
Workspace file I/O expert. ALWAYS invoke this skill when you need to list workspaces, read or write files in a workspace on a remote node, or browse workspace directories. Use this for cross-node file operations — for local sandbox files, use standard filesystem tools instead.
figma-code-connect
Creates and maintains Figma Code Connect template files that map Figma components to code snippets. Use when the user mentions Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.ts or .figma.js files.
agentdebug
Use AgentDebugX for trajectory diagnosis only when the user explicitly asks to use AgentDebug, AgentDebugX, or the agentdebug skill. Do not invoke for generic debugging, diagnosis, inspection, or trajectory-review requests.