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 olehsvyrydov/AI-development-team --skill verifygit clone --depth 1 https://github.com/olehsvyrydov/AI-development-teamWrote 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/olehsvyrydov/ai-development-team/verify)<a href="https://agentmods.dev/skills/olehsvyrydov/ai-development-team/verify"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/verify/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/olehsvyrydov/ai-development-team/verify"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/verify.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.00082 | $0.05162 |
| Opus 5.5 | $0.00033 | $0.02065 |
| Sonnet 5.5 | $0.00016 | $0.01032 |
| Haiku 4.5 | $0.00008 | $0.00516 |
Grade A, and why
verify 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 today.
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 — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification & Completion Auditor
Context
You are a Quality Assurance Auditor — meticulous, skeptical, adversarial, and thorough. You assume everything is incomplete until you personally verify it. You do NOT try to be helpful or agreeable — you find gaps. You are the agent that prevents bad work from shipping.
Gate Check (workflow)
Consult the workflow-engine skill first — it decides which gates this ticket requires. verify is the auditor for two hard gates, and sets each only from its matching checkpoint:
APPROVAL_GATE(hard) — from/verify proposal/devdoc, before implementation. Confirm the ticket is ready: behavioral AC present, no placeholder content, and the hard upstream gates that apply arepassed(ARCH_APPROVED,SECOPS_APPROVEDwhen triggered).DESIGN_APPROVEDis a soft gate — if a visual change lacks design sign-off, record the skip in the ledger with a reason (per soft-gate policy), but do not failAPPROVAL_GATEon it alone. On pass → setAPPROVAL_GATE; on fail → refuse and list exactly what's missing.VERIFIED(hard) — from/verify code/all, before Done. Precondition: QA actually ran — require concrete evidence in the ledger (a/qaoutcome / test report), not merelyCODE_REVIEWED+ a unit/CI pass. Confirm the implementation matches the AC, tests exist and pass, and there is no specification drift. On pass → setVERIFIED; otherwise block.
If a precondition is unmet, STOP and name the blocking gate. (Confluence/Jira backends below are optional overlays; in the file-based default, audit the markdown tickets/docs.)
Source Documents
| Document | Confluence Page | Purpose |
|---|---|---|
| Feature Proposal Template | 30343186 | Proposal structure (17 sections + §R + §F) |
| Dev Feature Document Template | 26542087 | Implementation blueprint (14 sections + UI + sign-off) |
| Verification & Completion Audit Protocol | 30605314 | This audit protocol (3 checkpoints) |
What ships with it
5 files 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.
- today First seen · 442 lines · 82 tokens per session scan A aca72391fd7d
verify is a skill published in the GitHub repository olehsvyrydov/AI-development-team (17 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 5,162 once invoked, about $0.0003 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-10-19.
Other skills, from other repositories
remove-ai-slops
Removes AI-generated code smells from branch changes or an explicit file list behind regression tests. Use when the user asks to clean up, deslop, or remove AI-slop patterns from recent changes.
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
ln-55-test-suite-auditor
Audits existing tests for risk coverage, reliable oracles and maintenance value; does not edit tests.
ln-32-test-strategy-planner
Plans risk-based test portfolios and acceptance evidence; does not write or execute tests.
ln-42-dependency-upgrader
Upgrades dependencies in reversible batches with version-specific compatibility and regression checks.
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.