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 J-Pster/Psters_AI_Workflow --skill verification-before-completiongit clone --depth 1 https://github.com/J-Pster/Psters_AI_WorkflowWrote 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/j-pster/psters_ai_workflow/verification-before-completion)<a href="https://agentmods.dev/skills/j-pster/psters_ai_workflow/verification-before-completion"><img src="https://agentmods.dev/badge/skills/j-pster/psters_ai_workflow/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/j-pster/psters_ai_workflow/verification-before-completion"><img src="https://agentmods.dev/badge/skills/j-pster/psters_ai_workflow/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.00034 | $0.00307 |
| Opus 5 | $0.00017 | $0.00153 |
| Sonnet 5 | $0.00007 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00031 |
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 9d 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
Verification Before Completion
Never claim "done", "fixed", "passing", or "ready" without fresh evidence from commands run in the current execution context.
Iron Rule
No completion claims without command evidence.
Mandatory flow
- Identify which command validates the claim.
- Run the command fully.
- Check exit code and meaningful output.
- Report the claim with evidence.
- If full verification is not possible, state limitations explicitly.
Evidence format
- Command executed:
<command> - Result:
exit code 0|non-zero - Key output:
<1-2 relevant lines> - Conclusion:
<what is verified>
Typical mappings
- Build claim ->
npm run build(or project equivalent) - Lint claim -> linter command output with zero errors
- Bug fix claim -> reproduction command/script no longer fails
- Migration safety claim -> migration run and drift check evidence
Anti-patterns
- "Should be fine now"
- "Looks correct"
- "I think it works"
- Using old command output as evidence
In this workflow
- Apply at the end of
/pwf-workand/pwf-work-plan. - If evidence is partial, still provide status, but mark it as limited and list next verification steps.
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.
- 9d ago First seen · 47 lines · 34 tokens per session scan A 8520cadd61f9
verification-before-completion is a skill published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 307 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-30.
Other skills, from other repositories
trulens-evaluation-workflow
Systematically evaluate your LLM application with TruLens.
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
ccg-workflow
How to run a non-trivial change end to end with the CCG role tools (ccganalyze / ccgdesign / ccgbuild / ccgdebug / ccgoptimize / ccgreview / ccgtest) and the verify- quality gates. Use when a task is a whole feature, a refactor, a bug whose cause is not yet known, or any change large enough that one straight-through…
agent-builder
Load before calling build-agent for a new or existing n8n Agent. Governs prerequisite creation, faithful handoff of the user's request, agent targeting across turns, builder questions, testing, and publishing. Use directly for routine follow-ups when the conversation already targets an Agent; rerun intent-recognition…
config-evals
Builds and maintains configuration-based evaluations on a workflow with the eval-config tool. Use when the user asks to set up, add, view, change, or remove an evaluation, score, grade, or judge a workflow's output, or measure answer quality against a test dataset. This is the only eval form Instance AI handles — it…
flow-next-qa
Live-app QA pass derived from the spec. Drives the running app, files P0/P1/P2 findings with evidence, emits a YES or NO qaverdict receipt.