Borrowing it
Nothing to install: this file belongs to takumi0706/google-calendar-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/takumi0706/google-calendar-mcp/main/.claude/skills/kiro-verify-completion/SKILL.mdgit clone --depth 1 https://github.com/takumi0706/google-calendar-mcpWrote 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/takumi0706/google-calendar-mcp/kiro-verify-completion)<a href="https://agentmods.dev/skills/takumi0706/google-calendar-mcp/kiro-verify-completion"><img src="https://agentmods.dev/badge/skills/takumi0706/google-calendar-mcp/kiro-verify-completion/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/takumi0706/google-calendar-mcp/kiro-verify-completion"><img src="https://agentmods.dev/badge/skills/takumi0706/google-calendar-mcp/kiro-verify-completion.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.00039 | $0.00863 |
| Opus 5 | $0.00019 | $0.00432 |
| Sonnet 5 | $0.00008 | $0.00173 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
kiro-verify-completion 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.
This is a copy
91% identical to kiro-verify-completion — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kiro-verify-completion
Overview
This skill prevents false completion claims. A task, fix, or feature is only complete when supported by fresh evidence that matches the scope of the claim.
When to Use
- Before saying a task is complete
- Before saying a bug is fixed
- Before saying tests pass
- Before moving to the next task in autonomous execution
- Before reporting
GOfrom feature-level validation - Before trusting another subagent's success report
Do not use this skill for early planning or speculative status updates.
Inputs
Provide:
- The exact claim to verify
- Claim type:
TASKFIXTEST_OR_BUILDFEATURE_GO
- Validation commands discovered by the controller
- Fresh command output and exit codes
- Relevant task IDs, requirement IDs, and design refs where applicable
- For feature-level claims:
- requirements coverage status
- design alignment status
- integration status
- blocked task status
Outputs
Return one of:
VERIFIEDNOT_VERIFIEDMANUAL_VERIFY_REQUIRED
Also return:
- Claim reviewed
- Evidence used
- Scope/evidence mismatch, if any
Use the language specified in spec.json.
Gate Function
- Identify the exact claim.
- Identify the exact command or checklist that proves that claim.
- Require fresh evidence from the current code state.
- Check exit code, failure count, skipped scope, and missing coverage.
- Reject claims that are broader than the evidence.
- If mandatory validation cannot be completed, return
MANUAL_VERIFY_REQUIRED. - Only then allow the claim.
Claim-Specific Rules
TASK
Require:
- task-local verification evidence
- no unresolved blocking findings from review
- evidence aligned with the task boundary
FIX
Require:
- evidence that the original symptom is resolved
- no broader regressions in the relevant verification scope
TEST_OR_BUILD
Require:
- actual command output
- exit code
- no inference from unrelated checks
FEATURE_GO
Require:
- full test suite result
- runtime smoke boot result showing the built artifact reaches its first usable state
- requirements coverage assessment
- cross-task integration assessment
- design end-to-end alignment assessment
- blocked tasks assessment
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 · 132 lines · 39 tokens per session scan A 59980e9ecd91
kiro-verify-completion is a skill published in the GitHub repository takumi0706/google-calendar-mcp (59 stars, last pushed 25d ago), licensed MIT. It adds 39 tokens to every session and 863 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to kiro-verify-completion, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…