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/drizzy07x/skillquiver/verify-worknpx skills add Drizzy07x/Skillquiver --skill verify-workgit clone --depth 1 https://github.com/Drizzy07x/SkillquiverWrote 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/drizzy07x/skillquiver/verify-work)<a href="https://agentmods.dev/skills/drizzy07x/skillquiver/verify-work"><img src="https://agentmods.dev/badge/skills/drizzy07x/skillquiver/verify-work.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.01985 |
| Opus 5 | $0.00023 | $0.00992 |
| Sonnet 5 | $0.00009 | $0.00397 |
| Haiku 4.5 | $0.00005 | $0.00198 |
Grade A, and why
verify-work 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Work
Treat completion as a set of falsifiable claims, not a confident summary. One evidence standard and one finding format govern the audit of a delivery or completion claim. The audit is read-only — report findings and verdicts; never fix, install, or remove.
Shared evidence standard
Evidence levels, weakest to strongest:
- Inspection — text, structure, configuration, static relationships.
- Static analysis — a linter, type checker, parser, or validator accepted the artifact.
- Build — compilation or packaging for the tested target.
- Behavioral test — specified behavior for exercised cases.
- Runtime validation — behavior in the real application or a representative environment.
- External state — current remote, deployed, scheduled, or published state.
Higher levels do not cover unrelated lower claims: a clean build does not prove startup; a unit test does not prove deployment. For each material claim record: the claim, the required evidence level, the evidence obtained verbatim (exact command, exit code, decisive output lines; for visual, web, or desktop evidence a screenshot or artifact path plus what it shows), and a verdict: verified, partially verified, unverified, or contradicted. Missing tools, skipped checks, timeouts, stale reports, or absent logs are never a pass. If a check cannot run, report the exact reason; never replace execution with a predicted result.
Useful-test gate: a test counts only when it observes requested behavior or a realistic failure boundary. Run a regression test and show it fail against the defective state, then rerun the identical command and show it pass. Discount tests that grep for an implementation string, always pass, silently skip, or never reach the change.
Shared finding format
Each finding carries: axis (contract or quality), category (regression, security, reliability, compatibility, coverage, scope), severity and confidence (high/medium/low), location, problem, evidence, follow-up. Merge only findings describing the same observable issue: keep highest severity, lowest confidence, all evidence; preserve disagreements as conflicts; order by severity then confidence. Each pass returns one verdict — confirmed, failed, or inconclusive; missing, stale, or skipped evidence is inconclusive, never confirmed. Only confirmed contributes to completion; never average away a failed or inconclusive mandatory check.
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.
- 4d ago First seen · 129 lines · 47 tokens per session scan A a5fc76fc7c09
verify-work is a skill published in the GitHub repository Drizzy07x/Skillquiver (2 stars, last pushed 12d ago), licensed MIT. It adds 47 tokens to every session and 1,985 once invoked, about $0.0002 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
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
codex-test-gen
Generate unit tests for specified functions using Codex MCP.
brand-docx
Brand-aware Word engine. Use to (1) EXTRACT a company's brand from a Word template into a reusable "Brand Profile", (2) COMPREHEND the template with the model (optional), (3) VERIFY it, (4) GENERATE new on-brand .docx documents FROM a saved profile. Trigger on "extract our brand", "learn/match this template", "use our…
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.