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/duckbugio/flock/verification-before-completionnpx skills add duckbugio/flock --skill verification-before-completiongit clone --depth 1 https://github.com/duckbugio/flockWhat 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.00058 | $0.00424 |
| Opus 5 | $0.00029 | $0.00212 |
| Sonnet 5 | $0.00012 | $0.00085 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
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 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
Verify before you claim it's done
Saying "done" without checking is the most common way an agent ships a broken change. Before you report a coding task as finished, fixed, or working, VERIFY it — do not assume.
Checklist (do it, don't narrate it)
- Build / compile what you changed. If it doesn't build, it isn't done.
- Run the relevant tests with the project's own command (a
Taskfile/Makefiletarget,go test,npm test, …). Run the narrowest command that covers your change first, then the fuller suite if it's cheap. If the area you changed has no test and the change is non-trivial, add one. - Run the linter/formatter the project uses and fix what it flags.
- Re-read the request and confirm EVERY part is addressed — not just the easy part. Check the edge cases and error paths you touched.
- Look for regressions — did the change break a caller, a contract, a test, or a neighbouring feature?
Reporting
- Report what you actually ran and its result ("
go test ./...green,task lint0 issues"), never "should work". - If something failed, or you could not verify a part, SAY SO plainly — never paper over a failure or a skipped step.
- If a test fails, fix the code (or the test, if the test was wrong) before claiming done — don't hand back a red build.
A task is "done" only when you have evidence it works, not when the code looks right.
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 · 36 lines · 58 tokens per session scan A 01fff12a93b0
verification-before-completion is a skill published in the GitHub repository duckbugio/flock (506 stars, last pushed 9d ago), licensed MIT. It adds 58 tokens to every session and 424 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
electron-pro
Expert in building cross-platform desktop applications using web technologies (HTML/CSS/JS) with the Electron framework.
lat-md
Writing and maintaining lat.md documentation files — structured markdown that describes a project's architecture, design decisions, and test specs. Use when creating, editing, or reviewing files in the lat.md/ directory.
local-tools
Access local system resources including Calendar on macOS and Windows. Use this skill when you need to manage user's schedule directly on their device.
seedance
Generate AI videos using Volcengine Seedance model. Supports text-to-video (T2V), image-to-video (I2V), and audio-synced video generation. Use this skill when the user wants to create or generate videos.
seedream
Generate AI images using Volcengine Seedream model. Supports text-to-image (T2I), image editing (I2I), multi-image fusion, and web-search-based generation. Use this skill when the user wants to create, generate, or edit images.
technology-search
Search tech blogs, developer forums, and IT media (TechCrunch, Hacker News, 36氪, etc.) for software and hardware industry updates with heat ranking and EN↔CN translation. Use this skill only when the topic is clearly about programming, software, hardware, AI, or IT infrastructure.