A compatibility command that forwards the old `/verify` command to a maintained verification workflow. It checks a project using the appropriate build, type, lint, test, security, and change-review steps.

Use it to verify a codebase before delivery and report the checks that passed or are blocked.

It keeps older verification commands working while avoiding a second, outdated checklist.

verify — Command for Claude Code by sifxprime: A compatibility command that forwards the old /verify command…

Install

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.

agentmods

npx agentmods add commands/sifxprime/kodelyth-ecc/verify

Clone the repo

git clone --depth 1 https://github.com/sifxprime/kodelyth-ecc

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/sifxprime/kodelyth-ecc/verify.svg)](https://agentmods.dev/commands/sifxprime/kodelyth-ecc/verify)

Your own site

<a href="https://agentmods.dev/commands/sifxprime/kodelyth-ecc/verify"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/verify.svg" alt="Measured on agentmods" height="20"></a>

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

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

Security scan A 0 findings. Scan, not verified.

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.00015	$0.00153
Opus 5	$0.00008	$0.00077
Sonnet 5	$0.00003	$0.00031
Haiku 4.5	$0.00002	$0.00015

Measured 2d ago against content hash 4cd8df723451, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 2d 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.

commands/verify.md · 24 lines

What it actually says

Verification Command (Legacy Shim)

Use this only if you still invoke /verify. The maintained workflow lives in skills/verification-loop/SKILL.md.

Canonical Surface

Prefer the verification-loop skill directly.
Keep this file only as a compatibility entry point.

Arguments

$ARGUMENTS

Delegation

Apply the verification-loop skill.

Choose the right verification depth for the user's requested mode.
Run build, types, lint, tests, security/log checks, and diff review in the right order for the current repo.
Report only the verdicts and blockers instead of maintaining a second verification checklist here.

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.

2d ago First seen · 24 lines · 15 tokens per session scan A 4cd8df723451

Subscribe to this mod's changes

verify is a command published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 4d ago), licensed MIT. It adds 15 tokens to every session and 153 once invoked, about $0.0001 per session on Opus 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-09-03.

Testing ai-agents antigravity automation claude claude-code coding-assistant

maintainer-review-test-coverage

Review the PR for test coverage — does new behavior have tests, are critical paths exercised, do existing tests still cover what they should (Pi-tuned).

coleam00/Archon · 31 tokens

assess

Ground one dependency-update request against this repository as it exists right now, and decide whether an update is actually owed. You produce an assessment and a verdict; you change nothing. No one watches the run; the assessment file and your declared fields are the only things that persist.

coleam00/Archon · 0 tokens

review-tests

Find one defect: the change establishes or alters meaningful behavior, and no test would fail when that behavior regresses in a plausible way. Tests protect outcomes and invariants — count, lines, and coverage percentages are not outcomes. Read-only: never modify files, commit, or post anywhere.