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 Stivi7/cyberpunk-context-runners --skill verification-before-deliverygit clone --depth 1 https://github.com/Stivi7/cyberpunk-context-runnersWrote 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/stivi7/cyberpunk-context-runners/verification-before-delivery)<a href="https://agentmods.dev/skills/stivi7/cyberpunk-context-runners/verification-before-delivery"><img src="https://agentmods.dev/badge/skills/stivi7/cyberpunk-context-runners/verification-before-delivery/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/stivi7/cyberpunk-context-runners/verification-before-delivery"><img src="https://agentmods.dev/badge/skills/stivi7/cyberpunk-context-runners/verification-before-delivery.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.00026 | $0.00272 |
| Opus 5.5 | $0.00010 | $0.00109 |
| Sonnet 5.5 | $0.00005 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
verification-before-delivery 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 2mo 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 Delivery
Metadata
- Version: 1.0.0
- Triggers: Completion, approval, integration, or delivery claim
- Allowed agents: Nexus, Gatekeeper
- Side effects: Runs project commands and may block delivery
When to Use
Use at the last responsible moment. Prior results do not replace fresh verification after relevant changes or merges.
Inputs
Acceptance criteria, current branch and commit, changed scope, command registry, baseline failures, review state, and integration state.
Procedure
- Confirm the branch, commit, diff, and merge state being claimed.
- Select relevant discovered project commands based on affected areas and risk.
- Run them freshly and inspect exit status plus meaningful output.
- Confirm acceptance criteria and required reviews.
- Record unavailable checks, pre-existing failures, and residual risk without disguising them as success.
- Make only the claim supported by current evidence.
Verification
Evidence must identify commands, observed results, branch, commit, and time relative to the final change.
Output
Delivery status, acceptance results, fresh verification, omitted checks, baseline failures, branch, commit, and remaining risks.
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.
- 2mo ago First seen · 39 lines · 26 tokens per session scan A 468015e2b80c
verification-before-delivery is a skill published in the GitHub repository Stivi7/cyberpunk-context-runners (4 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 272 once invoked, about $0.0001 per session on Opus 5.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
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
review-checklist
The team's checklist for reviewing a change to linkcheck. Use before you commit or open a pull request.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.