Borrowing it
Nothing to install: this file belongs to tensorbee/rdocx. 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/tensorbee/rdocx/main/.claude/commands/verify.mdgit clone --depth 1 https://github.com/tensorbee/rdocxWrote 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/commands/tensorbee/rdocx/verify)<a href="https://agentmods.dev/commands/tensorbee/rdocx/verify"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/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/commands/tensorbee/rdocx/verify"><img src="https://agentmods.dev/badge/commands/tensorbee/rdocx/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.00019 | $0.03207 |
| Opus 5.5 | $0.00008 | $0.01283 |
| Sonnet 5.5 | $0.00004 | $0.00641 |
| Haiku 4.5 | $0.00002 | $0.00321 |
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 6d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/verify [--fast | --scoped F-XXX | --full]
There are three verification scopes:
--fastruns formatting, changed-crate linting and the unique affected local regression tests. It does not run whole-crate or complete installed suites.--scoped F-XXXis the feature-completion gate for local evidence. It binds the fast checks and the approved plan's named local RED/GREEN regressions to the claimed Base and actual source. Independent/microscoperemains required.--fullis the final integrated sprint gate. It runs the workspace suites and the union of every approved plan's final oracle and risk checks once.
Whole-crate suites, ordinary complete installed suites, external oracle comparisons, native Office controls, hash/pixel corpora, whole-package typing and stub checks, WASM, documentation, publication dry runs and supply-chain checks belong to the final union. A small affected typing or compile check can be a local regression when the change needs it. Do not promote it to another whole-suite run. Keep distinct configurations and artifact identities separate.
The caller consumes an applicable successful observation instead of running
it again. Record exact source, command/configuration, tools, inputs and results.
A later failed attempt invalidates an older green result for the same check.
After a source fix rerun affected checks, preserving earlier failures. Never
call an unperformed final oracle a passed local gate.
Record in-flight evidence and pending checks in the feature's existing
.claude/scratch/<F-ID>-progress.md before handing over.
Acceptance applicability
Build, artifact and semantic outcome
Dependent batches stop after a failed prerequisite. Use set -e in a shell
build/test batch or check the actual child status before the next stage. A
failed extension build must not fall through to tests or timings on an older
installed module. Preserve the failed attempt and authenticate the replacement
artifact after a successful build.
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.
- 6d ago Changed · +70 lines 6fc0cdcdcf0e
- 11d ago Changed · +14 lines 8d04263525ed
- 26d ago First seen · 166 lines · 19 tokens per session scan A c1582f6e7a55
verify is a command published in the GitHub repository tensorbee/rdocx (44 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 3,207 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-10-04.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
check-dev
Type-check a Z specification with fuzz.