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/thiientv/godmode/completion-verificationnpx skills add thiientv/godmode --skill completion-verificationgit clone --depth 1 https://github.com/thiientv/godmodeWhat 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.00063 | $0.00373 |
| Opus 5 | $0.00032 | $0.00187 |
| Sonnet 5 | $0.00013 | $0.00075 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
completion-verification 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 3d 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
Completion Verification
No completion claim without fresh evidence that can falsify the claim.
Completion gate
- State the exact claim and its scope.
- Map each requirement to the smallest meaningful evidence: focused test, type check, build, package validation, browser flow, API response, screenshot, database state, static analysis, or independent review.
- Run the full relevant command now. Do not rely on an earlier transcript or another agent's report.
- Read the output and record exit status, counts, and failures.
- Compare what was exercised with what the claim covers.
- Report blocked checks, unavailable environments, unrelated failures, and residual risk explicitly.
Use evidence-map.md for multi-surface changes.
Evidence discipline
- A unit test does not prove deployment or a browser flow.
- A build does not prove user-visible behavior.
- A screenshot does not prove keyboard or data correctness.
- A reviewer report does not prove runtime behavior.
- One green path does not prove negative and boundary paths.
If a check fails, preserve the failure and hand it to
root-cause-debugging. Never weaken, delete, skip, or rewrite a check merely
to obtain green output.
Completion condition
Every in-scope acceptance item has a fresh result, every unavailable check is marked as a limit, and the final wording is no broader than the evidence.
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.
- 3d ago First seen · 45 lines · 63 tokens per session scan A 88ad16dba0d5
completion-verification is a skill published in the GitHub repository thiientv/godmode (93 stars, last pushed 7d ago), licensed MIT. It adds 63 tokens to every session and 373 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
agent-evaluation-reporting
Use when summarizing agent evaluations where autonomous, assisted, failed, timed-out, or invalid outcomes must remain distinct and comparable.
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
agent-workspace-linux
Use when a task needs an isolated hidden Linux desktop or workspace-owned browser: GUI app QA, web/browser/shopping automation, sandboxed app observation, or stale workspace cleanup. Routes agent-workspace-linux MCP tools on demand. Does NOT apply to host desktop/Chrome control, generic MCP setup, or pure code/file…
ss-component
Generate a new UI component following the StyleSeed design conventions.
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。.
map-review
Interactive 4-section code review using monitor, predictor, and evaluator agents plus the user and maintainer role reviewers on current changes. Use when reviewing a diff, PR, or staged work before merge. Do NOT use to plan or implement; use map-plan or map-efficient.