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.
git clone --depth 1 https://github.com/RohitBind123/claude-setupWrote 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/rohitbind123/claude-setup/verify)<a href="https://agentmods.dev/commands/rohitbind123/claude-setup/verify"><img src="https://agentmods.dev/badge/commands/rohitbind123/claude-setup/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/rohitbind123/claude-setup/verify"><img src="https://agentmods.dev/badge/commands/rohitbind123/claude-setup/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.00000 | $0.00312 |
| Opus 5.5 | $0.00000 | $0.00125 |
| Sonnet 5.5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
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 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.
This is a copy
100% identical to verify — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Verification Command
Run comprehensive verification on current codebase state.
Instructions
Execute verification in this exact order:
-
Build Check
- Run the build command for this project
- If it fails, report errors and STOP
-
Type Check
- Run TypeScript/type checker
- Report all errors with file:line
-
Lint Check
- Run linter
- Report warnings and errors
-
Test Suite
- Run all tests
- Report pass/fail count
- Report coverage percentage
-
Console.log Audit
- Search for console.log in source files
- Report locations
-
Git Status
- Show uncommitted changes
- Show files modified since last commit
Output
Produce a concise verification report:
VERIFICATION: [PASS/FAIL]
Build: [OK/FAIL]
Types: [OK/X errors]
Lint: [OK/X issues]
Tests: [X/Y passed, Z% coverage]
Secrets: [OK/X found]
Logs: [OK/X console.logs]
Ready for PR: [YES/NO]
If any critical issues, list them with fix suggestions.
Arguments
$ARGUMENTS can be:
quick- Only build + typesfull- All checks (default)pre-commit- Checks relevant for commitspre-pr- Full checks plus security scan
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 · 60 lines · 0 tokens per session scan A 22ad1cca29aa
verify is a command published in the GitHub repository RohitBind123/claude-setup (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 312 tokens. A static security scan graded it A with 0 findings. It is 100% identical to verify, differing in 0 lines, and is treated as a copy.
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.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
flowspec.validate
../../templates/commands/flow/validate.md.