A command that runs a project's tests, TypeScript type checks, linting, and production build, then reports the results. These checks look for behavior failures, type mistakes, style problems, and build errors.

Use it after coding to verify tests, types, lint rules, and the build before committing or opening a pull request.

It gathers the main pre-commit checks in one run, so you can see whether the project is ready for a commit. Failures are summarized with suggested next actions.

How llcoolblaze/claude-boris configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to llcoolblaze/claude-boris. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/llcoolblaze/claude-boris/main/.claude/commands/verify-all.md

Clone the repo

git clone --depth 1 https://github.com/llcoolblaze/claude-boris

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/llcoolblaze/claude-boris/verify-all/github.svg)](https://agentmods.dev/commands/llcoolblaze/claude-boris/verify-all)

Your own site

<a href="https://agentmods.dev/commands/llcoolblaze/claude-boris/verify-all"><img src="https://agentmods.dev/badge/commands/llcoolblaze/claude-boris/verify-all/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/llcoolblaze/claude-boris/verify-all"><img src="https://agentmods.dev/badge/commands/llcoolblaze/claude-boris/verify-all.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 287 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00017	$0.00287
Opus 5.5	$0.00007	$0.00115
Sonnet 5.5	$0.00003	$0.00057
Haiku 4.5	$0.00002	$0.00029

Measured 2mo ago against content hash 38edf197e926, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

verify-all 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.

.claude/commands/verify-all.md · 44 lines

What it actually says

Complete Verification Suite

Test Suite

!npm test 2>&1 | tail -20 || echo "TESTS: CHECK OUTPUT ABOVE"

TypeScript

!npm run typecheck 2>&1 || echo "TYPECHECK: FAILED"

Linting

!npm run lint 2>&1 | tail -10 || echo "LINT: FAILED"

Build

!npm run build 2>&1 | tail -10 || echo "BUILD: FAILED"

Verification Report

Summarize results in this format:

Check	Status	Details
Tests	✅/❌	X passing, Y failing
TypeScript	✅/❌	X errors
Lint	✅/❌	X warnings, Y errors
Build	✅/❌	Success / Failed at...

Overall Status

Ready to commit?

✅ All checks pass - safe to commit
⚠️ Warnings only - consider fixing
❌ Failures - must fix before commit

Recommended Actions

If failures exist, list them in priority order with suggested fixes.

If all pass, suggest: "Ready for /commit-push-pr"

Changes

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 · 44 lines · 17 tokens per session scan A 38edf197e926

Subscribe to this mod's changes

verify-all is a command published in the GitHub repository llcoolblaze/claude-boris (49 stars, last pushed 9mo ago), licensed MIT. It adds 17 tokens to every session and 287 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.

Testing

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.

grainulation/grainulator · 0 tokens

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…

OpenHands/extensions · 63 tokens

claude-boris: Command for Claude Code