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 vigneshbarani24/sap-superpowers --skill verification-before-completiongit clone --depth 1 https://github.com/vigneshbarani24/sap-superpowersWrote 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/vigneshbarani24/sap-superpowers/verification-before-completion)<a href="https://agentmods.dev/skills/vigneshbarani24/sap-superpowers/verification-before-completion"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/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/vigneshbarani24/sap-superpowers/verification-before-completion"><img src="https://agentmods.dev/badge/skills/vigneshbarani24/sap-superpowers/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.00043 | $0.02710 |
| Opus 5 | $0.00022 | $0.01355 |
| Sonnet 5 | $0.00009 | $0.00542 |
| Haiku 4.5 | $0.00004 | $0.00271 |
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 7d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Before Completion
This skill enforces that no task is ever marked "done" without enumerated outputs, cited evidence, and a completed verification checklist. It is the quality gate for the entire SAP Superpowers system.
Iron Laws
-
NEVER SAY "DONE" WITHOUT LISTING WHAT WAS PRODUCED. Completion is not a feeling. It is an inventory. Name every output: every file generated, every finding documented, every source cited. If you cannot list it, you did not produce it.
-
NEVER SKIP VERIFICATION STEPS. Every skill has a Verification section with checkboxes. Each box must be checked with evidence, not assumptions. Skipping a verification step because "it's obvious" is the number one cause of defective SAP deliverables.
-
ALWAYS PROVIDE EVIDENCE, NOT ASSERTIONS. "This should work" is an assertion. "Tested in SE38, output matches expected result per test case TC-004" is evidence. "The config looks correct" is an assertion. "SPRO path X > Y > Z verified, field ABC set to value 123 matching spec section 4.2" is evidence.
-
NEVER CONFUSE COVERAGE WITH CORRECTNESS. Touching every item on a checklist is coverage. Producing verifiable output for every item is correctness. Coverage without correctness is a false completion.
-
COMPLETION IS BINARY. A task is either verified-complete or not-complete. There is no "mostly done," "essentially complete," or "done except for." If any verification item fails, the task is not complete. Period.
What "Done" Means by Skill Type
Process Skills (Consulting, Delivery)
A process skill is complete when:
- A deliverable file has been generated (Markdown document, matrix, plan, runbook)
- The deliverable follows the skill's template exactly
- Every section of the template is filled with project-specific content, not placeholders
- The skill's verification checklist is fully satisfied
- The next skill in the workflow chain has been identified and communicated
Evidence: The deliverable file path, section-by-section confirmation, verification checklist status.
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.
- 7d ago First seen · 178 lines · 43 tokens per session scan A d03d822c89cd
verification-before-completion is a skill published in the GitHub repository vigneshbarani24/sap-superpowers (9 stars, last pushed 18d ago), licensed MIT. It adds 43 tokens to every session and 2,710 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-09-03.
Other skills, from other repositories
sap-expert
Expert in SAP ERP systems, ABAP programming, SAP HANA, S/4HANA, Fiori applications, and SAP integration patterns including OData, RFC, and IDoc. Use when the user mentions ERP, enterprise, business apps, ABAP, HANA, or S/4HANA, or when the task involves SAP Ecosystem, ABAP Development, Integration Technologies, or…
abap-unit-testing
Help with ABAP Unit testing including test class setup, assertions, test doubles, mocking frameworks, dependency injection, CDS test environments, SQL test environments, RAP BO test doubles, and test fixtures. Use when users ask about ABAP unit tests, test classes, test methods, CLABAPUNITASSERT, test doubles…
sap-sac-test-automation
SAP Analytics Cloud (SAC) automated testing skill for designing capability-gated browser discovery and deterministic Playwright test suites for SAC stories, dashboards, reports, planning workflows, comments, permissions, visual regression, and reusable QA automation. This skill should be used when building SAC…
execute
Run the generated Playwright tests and summarize pass/fail results. Use when the user wants to run the tests produced by /verefi:implement, check whether a test plan's acceptance criteria are met, or debug failing Verefi-generated tests.
slack-agent-flow
Let an existing Slack agent create new agents that arrive as their own Slack bots — provisioned app, operator DM, and a shared three-way room, hot-started without a host restart.
add-codex
Use Codex (OpenAI's codex app-server) as a full agent provider — planning, tool orchestration, MCP tools, server-side history, session resume — alongside or instead of Claude. ChatGPT subscription or OpenAI API key, vault-only via OneCLI. Per-group via ncl groups config update --provider codex. Distinct from using…