A command that audits an implementation against its product requirements and task plan. It reviews the actual code and reports issues by severity instead of only running tests.

Reviewing files against full-prd.md and tasks.md, checking implementation coverage, and producing critical, major, and minor review comments.

It helps find missing requirements, deviations from the planned design, and code-quality problems that tests may not catch.

How that0n3guy/mealie-mcp-server-ts configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to that0n3guy/mealie-mcp-server-ts. 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/that0n3guy/mealie-mcp-server-ts/main/.claude/commands/clavix/verify.md

Clone the repo

git clone --depth 1 https://github.com/that0n3guy/mealie-mcp-server-ts

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/that0n3guy/mealie-mcp-server-ts/verify/github.svg)](https://agentmods.dev/commands/that0n3guy/mealie-mcp-server-ts/verify)

Your own site

<a href="https://agentmods.dev/commands/that0n3guy/mealie-mcp-server-ts/verify"><img src="https://agentmods.dev/badge/commands/that0n3guy/mealie-mcp-server-ts/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/commands/that0n3guy/mealie-mcp-server-ts/verify"><img src="https://agentmods.dev/badge/commands/that0n3guy/mealie-mcp-server-ts/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 10,166 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 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.00000	$0.10166
Opus 5.5	$0.00000	$0.04066
Sonnet 5.5	$0.00000	$0.02033
Haiku 4.5	$0.00000	$0.01017

Measured 2mo ago against content hash 320ed4e9ec4c, 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 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.

Subtle steeringlowPrompt injection

Instructions that bias recommendations or shape behaviour without the user noticing.

**⚠️ Never tell the user a file was saved without verifying it exists.**

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

.claude/commands/clavix/verify.md · 1,353 lines

How it starts

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

Clavix: Verification & Audit

I will perform a Spec-Driven Technical Audit of your implementation. I don't just "run tests"—I verify that your code matches the Plan (tasks.md) and the Requirements (full-prd.md).

What This Does

When you run /clavix:verify, I act as a Senior Code Reviewer. I compare what was built against what was planned.

Load the Spec: I read the full-prd.md and tasks.md to understand the requirements and technical design.
Read the Code: I inspect the actual source files associated with completed tasks.
Compare & Analyze: I check for:
- Implementation Accuracy: Does the code follow the "Implementation Notes" from the plan?
- Requirements Coverage: Are all PRD requirements for this feature met?
- Code Quality: Are there hardcoded values, type errors, or architectural violations?
Generate Review Comments: I output a structured list of issues (Critical, Major, Minor) for you to address.

CLAVIX MODE: Technical Auditor

I'm in Audit Mode.

What I'll do:

✓ Treat tasks.md as the "Source of Truth" for architecture.
✓ Treat full-prd.md as the "Source of Truth" for behavior.
✓ Read source code line-by-line.
✓ Generate specific, actionable Review Comments.

What I won't do:

✗ Assume "it works" because a test passed.
✗ Ignore the architectural plan.
✗ Fix issues automatically (until you tell me to "Fix Review Comments").

Self-Correction Protocol

DETECT: If you find yourself:

Skipping Source Analysis: "Looks good!" without reading src/....
Ignoring the Plan: Verifying a feature without checking the Technical Implementation Details in tasks.md.
Vague Reporting: "Some things need fixing" instead of "Issue #1: Critical - ...".
Hallucinating Checks: Claiming to have run E2E tests that don't exist.

STOP: Halt immediately.

CORRECT: "I need to perform a proper audit. Let me read the relevant source files and compare them against the plan."

Read the full file on GitHub · 1,353 lines

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.

2mo ago First seen · 1,353 lines · 0 tokens per session scan A 320ed4e9ec4c

Subscribe to this mod's changes

verify is a command published in the GitHub repository that0n3guy/mealie-mcp-server-ts (0 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 10,166 tokens. A static security scan graded it A with 1 finding (subtle steering). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review Planning

verify next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
verifythat0n3guy/mealie-mcp-server-ts	Command	0	10mo ago	MIT	A	0	Claude Code
diff-reviewcoco-research/coco	Command	785	yesterday	Apache-2.0	A	11	Claude Code
review-branchdamusix/atomic-claude	Command	115	5d ago	MIT	A	35	Claude Code
refactorRchGrav/claudebox	Command	1.2k	1mo ago	MIT	A	9	Claude Code
spec-trace-requirementsrjmurillo/ai-agents	Command	49	yesterday	MIT	A	0	GitHub Copilot
merge-conflict-analysisrjmurillo/ai-agents	Command	49	yesterday	MIT	A	0	GitHub Copilot
initazrtydxb/procoder	Command	211	11d ago	Apache-2.0	A	16	Claude Code

mealie-mcp-server-ts: Command for Claude Code