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 Dankosik/go-service-template-rest --skill go-verification-before-completiongit clone --depth 1 https://github.com/Dankosik/go-service-template-restWrote 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/dankosik/go-service-template-rest/go-verification-before-completion)<a href="https://agentmods.dev/skills/dankosik/go-service-template-rest/go-verification-before-completion"><img src="https://agentmods.dev/badge/skills/dankosik/go-service-template-rest/go-verification-before-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/dankosik/go-service-template-rest/go-verification-before-completion"><img src="https://agentmods.dev/badge/skills/dankosik/go-service-template-rest/go-verification-before-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.00028 | $0.00429 |
| Opus 5 | $0.00014 | $0.00215 |
| Sonnet 5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
go-verification-before-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 4d 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
Go Verification Before Completion
An evidence boundary is the behavior a proof would fail on. An empirical claim cannot be wider than that boundary. Local development acceptance is a separate sufficiency decision owned by the Evidence Contract, not a claim that every production path has been observed.
claim -> observable -> command or procedure -> result -> exercised scope -> gap
An Implemented task handoff claims code production, not verified behavior, and does not trigger this method. For a ledger, use this method at final validation after all planned code is assembled; Implementation owns bounded feedback during coding.
Apply the shared Evidence Contract. Select only its local criterion and genuinely explicit additions. This skill and its references do not create new gates or authorize test infrastructure. For a verification claim, name the observable whose absence or incorrectness would make the selected proof fail. Record the exact command or procedure, relevant preconditions, result, cached or fresh state, and scope actually exercised.
A passing command proves only the surfaces it observed. File presence, status, an implementation summary, a skipped integration suite, a test pattern matching zero tests, or an unrelated aggregate cannot carry the claim.
Complete when required claims are supported at their stated scope or returned with the exact missing required proof and owner. Stop ordinary local work at its accepted build/unit boundary; disclose material optional gaps without blocking completion or repairing their environment. Never weaken an explicitly requested runtime or CI result into local success. Return Evidence Result V1. Load a matching reference only when the boundary is non-obvious.
What ships with it
3 files 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.
- 4d ago Changed · +8 lines b6e49ef4afcb
- 5d ago Changed · +4 lines 1c0b385e67b9
- 12d ago First seen · 31 lines · 28 tokens per session scan A a22caed9fb5b
go-verification-before-completion is a skill published in the GitHub repository Dankosik/go-service-template-rest (7 stars, last pushed 3d ago), licensed MIT. It adds 28 tokens to every session and 429 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
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…
bubbletea-testing
Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm…
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
ci-orchestrator
Run a CI-like pipeline locally (format, lint, vet, static-analysis, tests) and summarize per-step results with remediation guidance.
config-loader-helper
Diagnose configuration-related failures, enumerate required env vars, and guide safe local test setup (no secrets).