Borrowing it
Nothing to install: this file belongs to mag123c/toktrack. 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/mag123c/toktrack/main/.claude/skills/verify/SKILL.mdgit clone --depth 1 https://github.com/mag123c/toktrackWrote 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/mag123c/toktrack/verify)<a href="https://agentmods.dev/skills/mag123c/toktrack/verify"><img src="https://agentmods.dev/badge/skills/mag123c/toktrack/verify.svg" alt="Measured on agentmods" 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.00015 | $0.00651 |
| Opus 5 | $0.00008 | $0.00326 |
| Sonnet 5 | $0.00003 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
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 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify
Flow
cargo test → cargo clippy → cargo fmt --check
│ │ │
└── On fail: fix and retry (notify user after 3 same failures)
Commands
cargo test --quiet
cargo clippy --all-targets --all-features -- -D warnings
cargo fmt --all -- --check
Verification Honesty (MUST — PASS gate)
Verification trustworthiness lies not in "what passed" but in "what was actually executed and passed". Enforced before any PASS verdict.
Skip ≠ Pass
- Tests marked
ignored/#[ignore]are unverified → do not count as green. - Tests skipped due to environment (missing external service, platform constraints, etc.) are a BLOCKER. If unfixable, escalate to user as "verification incomplete + reason" rather than PASS.
Do not cite unrun tests as verification evidence
- "Confirmed via test X" is only valid when that test actually ran and passed in this execution.
- Do not use a merely written test as evidence of "confirmed" (false-green = false reassurance).
Coverage honesty (mock ≠ real)
- Mock-based unit tests verify only the logic inside the mock boundary. Behaviors invisible to mocks — file I/O, concurrency, simd-json real parsing — are confirmed only by integration verification.
- If a path is covered only by mocks, report it as "mock coverage only — integration unconfirmed" rather than "verified".
Acceptance/DoD cross-check (carry PLAN gates)
- Read the PLAN Acceptance/DoD and any
[unverified-gate]passed from implement; cross-check whether each item actually ran and passed in this execution. - If unrunnable (prod smoke / external service / CI-only environment) → no green-wash. Tag as
[unverified-gate: delegated, owner/due/probe]and carry to wrap Plan Reconciliation (../wrap/references/reconciliation.md).
Report format
- ✅ Actually executed and passed
- ⛔ Skipped/environment-blocked + reason (unresolved = BLOCKER, not PASS)
- ⚠️ Mock coverage only, integration unconfirmed
- ⏳ Delegated to wrap due to unverifiable Acceptance item
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 · 62 lines · 15 tokens per session scan A 9fe50e7df414
verify is a skill published in the GitHub repository mag123c/toktrack (188 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 651 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
rust-sota-arsenal
Reference guide for state-of-the-art Rust tooling across refactoring, profiling, benchmarking, testing, and SIMD optimization. Use whenever the.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
ios-development
Comprehensive guide for building native Apple platform applications.
kotlin-multiplatform
KMP/CMP shared business logic, Compose Multiplatform, expect/actual, Ktor, SQLDelight, and platform-specific implementations. Use when building cross-platform Kotlin applications for Android, iOS, desktop, or web.