Borrowing it
Nothing to install: this file belongs to ai-swiss/base. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ai-swiss/base/main/.ai/agents/base-contributor/skills/processes/verify/SKILL.mdgit clone --depth 1 https://github.com/ai-swiss/baseWrote 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/ai-swiss/base/verify)<a href="https://agentmods.dev/skills/ai-swiss/base/verify"><img src="https://agentmods.dev/badge/skills/ai-swiss/base/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/ai-swiss/base/verify"><img src="https://agentmods.dev/badge/skills/ai-swiss/base/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.00623 |
| Opus 5.5 | $0.00015 | $0.00249 |
| Sonnet 5.5 | $0.00007 | $0.00125 |
| Haiku 4.5 | $0.00004 | $0.00062 |
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 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
Verify the gates
The discipline is gate-enforced, not trusted. A contributor runs the gates locally before CI does. The single command runs them all; run it and read the output honestly.
Steps
- Run the core gates:
npm run check(tests, typecheck, thespec:checkchain, docs validation and route-test). Green here means the core is sound; CI additionally runs coverage, the regenerated-artifact diffs (base index/base build),doctor, the pack smoke test and the MCP/Studio suites — run those when you touch those areas (commands inCONTRIBUTING.md). - Read each gate's meaning if one fails (the full registry is
docs/reference/gates.md; each script also prints what it checks): the requirements matrix rejects phantom citations;spec-syncwants a runtime change to touchspecs/or declare[SPEC-NEUTRAL]; the immutability check forbids renumbering or reusing an ID;changelog-syncwants a visible change to carry its[Unreleased]line. - Fix the cause, not the symptom. Never bypass a hook (
--no-verify,--force), never add a silent fallback to make a gate pass. A red gate is information. - Confirm the proof is honest. Regenerate the matrix (
npm run spec:matrix) and check that the change's requirements are✅, not⚠️/❌; a gap is reported, never hidden. - Report green (or the exact failing gate and why), then hand back for commit.
What you never do
- Declare done on a red gate, or claim a gate passed without running it.
- Run heavy suites to look thorough; run what can falsify the change, plus the one command.
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 · 52 lines · 37 tokens per session scan A 606a4bdcf8a0
verify is a skill published in the GitHub repository ai-swiss/base (65 stars, last pushed 8d ago), licensed Apache-2.0. It adds 37 tokens to every session and 623 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-30.
verify compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| verifyai-swiss/base | Skill | 65 | 8d ago | Apache-2.0 | A | 37 | Claude Code |
| complianceericrisco/rsc-harness | Skill | 503 | 2d ago | MIT | A | 96 | Claude Code, Codex |
| wallet-cliBofAI/skills | Skill | 164 | 4d ago | MIT | A | 92 | Codex |
| vaultjoelhooks/joelclaw | Skill | 65 | yesterday | none | A | 82 | Claude Code |
| feishuHmbown/CodeWhale | Skill | 41k | 5d ago | MIT | A | 33 | Claude Code, Codex |
| interviewHmbown/CodeWhale | Skill | 41k | 5d ago | MIT | A | 40 | Claude Code, Codex |
| atmos-validationcloudposse/atmos | Skill | 1.4k | yesterday | Apache-2.0 | A | 31 | Claude Code |