clare: Command for Claude Code

.claude/commands/verify.md

verify is a command for Claude Code from jketreno/clare. It costs 0 tokens per session (302 once invoked), scanned A, original, MIT.

A verification command that runs clare/verify-ci.sh and reports whether the project’s automated checks passed or failed.

In plain words
What is it for?
Use it after making changes to check the project and identify which checks need attention.
Why use it?
It gathers failures into a structured summary, including error snippets, suggested commands, and possible fixes.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is jketreno/clare's own configuration. It tells Claude Code how to work on clare itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything clare configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./clare/verify-ci.sh 2>&1.

Reuse

Borrowing it

Nothing to install: this file belongs to jketreno/clare. 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/jketreno/clare/main/.claude/commands/verify.md
Clone the repo
git clone --depth 1 https://github.com/jketreno/clare

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.

agentmods badge for verify

README.md
[![agentmods](https://agentmods.dev/badge/commands/jketreno/clare/verify/github.svg)](https://agentmods.dev/commands/jketreno/clare/verify)
Your own site
<a href="https://agentmods.dev/commands/jketreno/clare/verify"><img src="https://agentmods.dev/badge/commands/jketreno/clare/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.

agentmods 80×15 button for verify

Your own site · 80×15
<a href="https://agentmods.dev/commands/jketreno/clare/verify"><img src="https://agentmods.dev/badge/commands/jketreno/clare/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 302 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00302
Opus 5.5 $0.00000 $0.00121
Sonnet 5.5 $0.00000 $0.00060
Haiku 4.5 $0.00000 $0.00030

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

Security

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.

.claude/commands/verify.md · 38 lines

What it actually says

/project:verify — Run CLARE verification

Runs ./clare/verify-ci.sh and reports a structured summary of results.

Instructions

Execute the following and report results clearly:

./clare/verify-ci.sh 2>&1
# Or to continue past failures and collect all results before reviewing:
./clare/verify-ci.sh --fail-slow 2>&1

After running:

  1. State clearly: PASSED or FAILED
  2. If failed, list each failing check by name
  3. For each failure, show the first few lines of the captured error output (the script prints a concise snippet). Include a suggested "quick command" the developer/agent can run to iterate on that specific failure (e.g., npx eslint --fix ., npx tsc --noEmit, pytest -q).
  4. Propose specific fixes for each failure
  5. Offer to fix and re-run: "Shall I fix these issues and run verify again?"

Format

## Verify CI Results

Status: ✅ PASSED / ❌ FAILED

### Failing Checks
- **[Check name]**: [brief error description]
  Fix: [specific action needed]

### Next Step
[Offer to fix and rerun, or confirm completion if passed]

If all checks pass, confirm: "All CI checks pass. Work is complete. Please review the diff and commit."

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.

  1. 1mo ago First seen · 38 lines · 0 tokens per session scan A f5d83c2247b2

Subscribe to this mod's changes

verify is a command published in the GitHub repository jketreno/clare (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 302 tokens. 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-31.