Borrowing it
Nothing to install: this file belongs to micheltlutz/dev-challenge. 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/micheltlutz/dev-challenge/main/.claude/commands/verify.mdgit clone --depth 1 https://github.com/micheltlutz/dev-challengeWrote 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/micheltlutz/dev-challenge/verify)<a href="https://agentmods.dev/commands/micheltlutz/dev-challenge/verify"><img src="https://agentmods.dev/badge/commands/micheltlutz/dev-challenge/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/micheltlutz/dev-challenge/verify"><img src="https://agentmods.dev/badge/commands/micheltlutz/dev-challenge/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.00483 |
| Opus 5.5 | $0.00000 | $0.00193 |
| Sonnet 5.5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
verify scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Read, Grep, Glob, Bash(python harness/cli.py:*), Bash(pytest harness/:*), Bash(curl:*) What it actually says
Verify a solution against its acceptance criteria.
Work out the target
Default --base-url is http://localhost:8000. If $ARGUMENTS names a
challenge or a URL, use those. If you do not know where their app is running,
ask — do not guess and report a connection error as a failure.
python harness/cli.py --base-url <url> --challenge <id>
Omit --challenge to run everything.
For the web track the runner is Playwright:
cd harness/ui/web && BASE_URL=<their-frontend> npx playwright test
Explain the scorecard
Do not paste the raw output and stop. For each failing criterion:
- Quote the criterion — its ID and its Given/When/Then.
- State what actually happened.
- Point at the likely cause, in their code if you can see it.
- Ask what they think is going on, before giving the fix. Default posture is
mentoring; see
AGENTS.md.
For each skipped criterion, explain that a skip is not a pass and name the missing prerequisite:
| Skip | Meaning |
|---|---|
| "Could not register a user" | backend-02-create-user is missing |
| "Could not authenticate" | backend-03-login is missing |
| "Reference seed data not present" | needs two users matching the fixture |
| "Cannot create statements" | POST /statement/ is missing |
| "GET /users/me returned 404" | the client cannot learn its own id |
Ignore uncovered criteria unless they ask — those are UI or manual-review items the API harness cannot reach, not something they did wrong.
Close
One line on where they stand — "6 of 7, and the last one is the scoping rule" —
and what to do next. If everything passes, say so without padding, and point at
/next.
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 · 56 lines · 0 tokens per session scan A d1dd2068801f
verify is a command published in the GitHub repository micheltlutz/dev-challenge (33 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 483 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
verify compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| verifymicheltlutz/dev-challenge | Command | 33 | 5d ago | MIT | A | 0 | Claude Code |
| firefabriqaai/specs.md | Command | 225 | 3d ago | MIT | A | 13 | Claude Code |
| toolsfirst-fluke/fullstack-starter | Command | 225 | 3d ago | MIT | A | 18 | GitHub Copilot |
| os-meetingCronusL-1141/AI-company | Command | 374 | 10d ago | MIT | A | 12 | Claude Code |
| erne-animateJubaKitiashvili/everything-react-native-expo | Command | 50 | 29d ago | MIT | A | 21 | Claude Code |
| react-nativegetsentry/toolkit | Command | 957 | yesterday | none | A | 0 | Claude Code |
| app-store-auditmjmirza/app-store-compliance | Command | 403 | yesterday | none | A | 35 | Claude Code |