A command for reviewing work that is waiting to be checked. It reads pending verification tasks and suggests checks for code, deployments, and commits.

Use it to review verification notes, run tests, linters, builds, or coverage checks, inspect staging deployments, and check CI or pull-request status.

It keeps unfinished verification work visible and provides a consistent way to confirm that changes are ready.

How sumulige/sumulige-claude configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to sumulige/sumulige-claude. 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/sumulige/sumulige-claude/main/.claude/commands/verify-work.md

Clone the repo

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

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/sumulige/sumulige-claude/verify-work/github.svg)](https://agentmods.dev/commands/sumulige/sumulige-claude/verify-work)

Your own site

<a href="https://agentmods.dev/commands/sumulige/sumulige-claude/verify-work"><img src="https://agentmods.dev/badge/commands/sumulige/sumulige-claude/verify-work/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/sumulige/sumulige-claude/verify-work"><img src="https://agentmods.dev/badge/commands/sumulige/sumulige-claude/verify-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan B 1 finding. 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.00006	$0.00313
Opus 5.5	$0.00002	$0.00125
Sonnet 5.5	$0.00001	$0.00063
Haiku 4.5	$0.00001	$0.00031

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

Security

Grade B, and why

verify-work scanned grade B 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 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat .claude/verify/verify-log.md 2>/dev/null || echo "No verification log found"

.claude/commands/verify-work.md · 64 lines

What it actually says

You are helping the user review and verify completed work.

Check Pending Tasks

First, read the verification log:

cat .claude/verify/verify-log.md 2>/dev/null || echo "No verification log found"

And check pending tasks:

cat .claude/verify/.pending-verify.json 2>/dev/null || echo "No pending tasks"

Verification Process

For each pending task, guide the user through:

What was done - Summarize the action
How to verify - Run appropriate verification commands:
- For code changes: run tests, linters
- For deployments: check staging environment
- For commits: verify CI/CD status

Common Verification Commands

# Run tests
npm test

# Check test coverage
npm run test:coverage

# Run linter
npm run lint

# Type check
npm run type-check

# Build verification
npm run build

# Check CI status (if using GitHub)
gh run list --limit 5

# Check PR status
gh pr status

Mark as Complete

After verification is successful, ask the user if they want to:

Mark the task as verified (remove from pending)
Keep it for later verification
Add additional verification steps

To mark as complete, edit .claude/verify/.pending-verify.json to remove the completed task.

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.

1mo ago First seen · 64 lines · 6 tokens per session scan B 8582467c774d

Subscribe to this mod's changes

verify-work is a command published in the GitHub repository sumulige/sumulige-claude (1 stars, last pushed 8mo ago), licensed MIT. It adds 6 tokens to every session and 313 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Testing agent-orchestration ai-agent ai-coding-assistant cli-tool codex-cli

sumulige-claude: Command for Claude Code