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 wellkilo/RepoPilot --skill verification-gategit clone --depth 1 https://github.com/wellkilo/RepoPilotWrote 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/wellkilo/repopilot/verification-gate)<a href="https://agentmods.dev/skills/wellkilo/repopilot/verification-gate"><img src="https://agentmods.dev/badge/skills/wellkilo/repopilot/verification-gate/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/wellkilo/repopilot/verification-gate"><img src="https://agentmods.dev/badge/skills/wellkilo/repopilot/verification-gate.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.00038 | $0.00440 |
| Opus 5.5 | $0.00015 | $0.00176 |
| Sonnet 5.5 | $0.00008 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
verification-gate 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 1mo 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 Gate
You are the Verifier Worker. Independently determine whether the patch satisfies the acceptance criteria without introducing a known regression.
Inputs
- RepoPilot
runId - Base and patched revisions
- Locator reproduction evidence
- Fixer change summary and pull request
- Triage acceptance criteria
Outputs
- Before/after reproduction result.
- Focused test result.
- Relevant broader test, lint, and type-check results.
- GitHub pull request check status.
- Verdict:
PASS,FAIL, orBLOCKED. - Residual risk and any required human review.
Append each command result as ci_result or tool_result evidence.
Invocation Conditions
Use after Fixer produces a commit. Repeat only for a new commit SHA.
Call repopilot_start_step before execution with a stable attempt-specific
idempotencyKey. Call repopilot_finish_step exactly once with the final
succeeded, failed, blocked, skipped, or cancelled outcome.
Dependencies
- Repository-local test tools
github_list_pull_request_checksrepopilot_append_evidence
Failure Handling
- Distinguish changed-code failures from pre-existing failures.
- Retry only tests documented as flaky and record every attempt.
- If CI is pending, return
BLOCKED; do not infer success. - If the target behavior cannot be observed, return
BLOCKED.
Permission and Safety Boundary
- Read-only verification.
- Do not amend the patch, merge the pull request, or dismiss failing checks.
- A green result is not merge approval.
Reuse Value
The evidence-based verdict contract is portable to dependency upgrades, test additions, documentation builds, and security remediations.
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.
- 1mo ago First seen · 64 lines · 38 tokens per session scan A be937c490ba3
verification-gate is a skill published in the GitHub repository wellkilo/RepoPilot (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 440 once invoked, about $0.0002 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
trace
Use when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports. Systematic root-cause analysis before any patch — never blind-patches symptoms. Standalone, ends with a final-integration review of the fix. Trigger with /hyperflow:trace, "debug this", "find the root cause", "why…
attest
Verifying spec compliance: extracts ACs from specs, adversarially checks conformance, generates BDD scenarios and traceability matrices. Use when impl must be proven to match a PRD/SRS/AC.
test-strategy
Coverage-design method for qa-engineer — pyramid ratios per archetype, equivalence/boundary/property case selection, mutation score as the real coverage signal, and a flake-quarantine policy. Turns "coverage is 90%" (a number with no method) into a defensible test plan. Emits TEST-STRATEGY-{slug}.md, which the QA gate…
quant-validation
The methods a financial-ML result has to survive before it is evidence — purged cross-validation with an embargo, triple-barrier labelling, sample uniqueness under overlapping labels, fractional differentiation, meta-labelling, and multiple-testing correction. Written because the invariants were required of…
adversarial-implementation-review-coach
Adversarial implementation review based on Block's g3 dialectical autocoding research. Use when validating implementation completeness against requirements with fresh objectivity.
cdt
Multi-agent development workflow using Agent Teams. Supports five modes: plan (architect teammate + PM teammate debate → plan.md), dev (developer teammate + code-tester teammate + qa-tester teammate + reviewer teammate iterate → code), full (plan → approval gate → dev), auto (plan → dev, no gate), and bugfix (tester +…