What is review-and-verify?

A verification and review procedure for checking code changes, tests, builds, and completion claims with fresh evidence.

Use it to review a diff, run repository-required verification, confirm a bug fix or feature, and report limitations before declaring completion.

It prevents saying that work passes or is complete based only on inspection or an earlier run. It requires identifying, running, and reading the relevant checks.

How asta-nguyen/kamehadb configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to asta-nguyen/kamehadb. 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/asta-nguyen/kamehadb/main/.agents/skills/review-and-verify/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/asta-nguyen/kamehadb

Made for: Claude Code, Codex.

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/skills/asta-nguyen/kamehadb/review-and-verify/github.svg)](https://agentmods.dev/skills/asta-nguyen/kamehadb/review-and-verify)

Your own site

<a href="https://agentmods.dev/skills/asta-nguyen/kamehadb/review-and-verify"><img src="https://agentmods.dev/badge/skills/asta-nguyen/kamehadb/review-and-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/asta-nguyen/kamehadb/review-and-verify"><img src="https://agentmods.dev/badge/skills/asta-nguyen/kamehadb/review-and-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,591 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.00042	$0.02591
Opus 5.5	$0.00017	$0.01036
Sonnet 5.5	$0.00008	$0.00518
Haiku 4.5	$0.00004	$0.00259

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

Security

Grade A, and why

review-and-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 19d 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.

.agents/skills/review-and-verify/SKILL.md · 216 lines

How it starts

The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.

review-and-verify

This skill reports findings; it does not fix them. A Status: fail returns to implement-task's ## After implementation fix loop (or to systematic-debugging for a bug). The only edits made here are the archive move and link rewrites in ## Archive a change and Execution: complete on a legacy plan; never edit code, wiki, or Progress.

Iron Law

NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE

If you have not performed a fresh verification check in this message, you cannot claim it passes. Previous runs are not evidence.

Verification gate

Before claiming any status: identify the command or repeatable procedure that proves the claim; run it fresh and complete; read the full output, including failures; verify it confirms the claim, stating the actual status with evidence either way; only then make the claim.

Before final completion, run every repository-mandated full verification command in AGENTS.md, manifests, or CI configuration; targeted checks do not replace it. If none is established, report that limitation.

Before reviewing requirements, read the active design and plan, the change's decisions.md, and the other sources in implement-task's ## Decision sources. A persisted decision is requirement evidence but does not override a pending approval gate; conversation recall is not review evidence. Mark completion only when this is the final review, every task is implemented (Progress: done with a Result: this review confirms with fresh evidence), and every required verification passes. A task with no Progress line is not complete: report a blocker so implement-task backfills it (../using-devkit/references/legacy.md). Approval status alone is not completion evidence.

A passing final review marks a legacy plan complete as ../using-devkit/references/legacy.md describes, and runs ## Archive a change for a change folder.

Verify the edit or the archive before reporting Status: pass. If work or required verification remains, leave the plan or change open and report the gap under Spec gaps.

Read the full file on GitHub · 216 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

references/receiving-code-review.md 842 B

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.

19d ago Changed · -44 lines f86d64c37775
26d ago Changed · +73 lines c59dd57c7040
1mo ago First seen · 187 lines · 42 tokens per session scan A 6e4524e01f06

Subscribe to this mod's changes

review-and-verify is a skill published in the GitHub repository asta-nguyen/kamehadb (14 stars, last pushed 10d ago), licensed Apache-2.0. It adds 42 tokens to every session and 2,591 once invoked, about $0.0002 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-10-05.

Databases LLM Testing ai database-management free tools

review-and-verify next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
review-and-verifyasta-nguyen/kamehadb	Skill	14	10d ago	Apache-2.0	A	42	Claude Code, Codex
chromaNousResearch/hermes-agent	Skill	261k	yesterday	MIT	A	12	Claude Code, Codex
backend-patternsaffaan-m/ECC	Skill	298k	4d ago	MIT	A	51	Claude Code, Codex
database-migrationsaffaan-m/ECC	Skill	298k	4d ago	MIT	A	61	Claude Code, Kiro
postgres-patternsaffaan-m/ECC	Skill	298k	4d ago	MIT	A	45	Claude Code, Kiro
free-llm-apismnfst/awesome-free-llm-apis	Skill	12k	yesterday	CC0-1.0	A	116	Claude Code, Codex
review-prsgoogleapis/mcp-toolbox	Skill	17k	yesterday	Apache-2.0	A	162	Claude Code, Codex

kamehadb: Skill for Claude Code