A command that runs a thorough pre-commit or pre-pull-request check. It covers building, type checking, linting, tests, security concerns, and reviewing the code changes.

Use it to verify code before creating a pull request or committing, following the project’s configured build, lint, and test commands.

It catches broken builds, type errors, style problems, failing tests, common security issues, and unwanted changes before they are committed or proposed.

verify — Command for coding agents by rosudrag: A command that runs a thorough pre-commit or pre-pull-request…

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/rosudrag/ai-praxis/verify

Clone the repo

git clone --depth 1 https://github.com/rosudrag/ai-praxis

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/rosudrag/ai-praxis/verify.svg)](https://agentmods.dev/commands/rosudrag/ai-praxis/verify)

Your own site

<a href="https://agentmods.dev/commands/rosudrag/ai-praxis/verify"><img src="https://agentmods.dev/badge/commands/rosudrag/ai-praxis/verify.svg" alt="Measured on agentmods" 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 514 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	$0.00000	$0.00514
Opus 5	$0.00000	$0.00257
Sonnet 5	$0.00000	$0.00103
Haiku 4.5	$0.00000	$0.00051

Measured 4d ago against content hash 103202b85be3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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.

bootstrap/templates/commands/verify.md · 86 lines

How it starts

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

/verify - Pre-PR Verification

Run a comprehensive verification loop before creating a PR or committing.

Instructions

Execute each verification phase in order. Stop at the first failure and fix it before continuing.

Phase 1: Build

{{build_command}}

If fails: Fix build errors before proceeding. Do not skip.

Phase 2: Type Check (if applicable)

{{typecheck_command}}

If fails: Fix type errors. Do not use any, @ts-ignore, or # type: ignore to suppress.

Phase 3: Lint

{{lint_command}}

If fails: Fix lint violations. Auto-fix where possible, manual fix where needed.

Phase 4: Test Suite

{{test_command}}

If fails: Fix failing tests. If a test is legitimately wrong (testing old behavior), update it with a comment explaining why.

Phase 5: Security Scan

Check for common security issues in changed files:

Hardcoded secrets (API keys, passwords, tokens)
SQL injection vulnerabilities
Unvalidated user input at system boundaries
Exposed sensitive data in logs or error messages

Phase 6: Diff Review

git diff --stat
git diff

Review the full diff for:

Debug statements (console.log, print, debugger)
Commented-out code
TODO/FIXME without issue references
Files that shouldn't be committed (.env, credentials, binaries)
Unintended changes (formatting-only diffs, unrelated modifications)

Output

## Verification Report

| Phase | Status | Details |
|-------|--------|---------|
| Build | PASS/FAIL | [details if failed] |
| Types | PASS/FAIL/SKIP | [details] |
| Lint | PASS/FAIL | [details] |
| Tests | PASS/FAIL | [X passed, Y failed] |
| Security | PASS/WARN | [findings] |
| Diff Review | PASS/WARN | [findings] |

**Result**: READY / NOT READY

Constraints

Run ALL phases, even if early ones pass
Do not suppress warnings to make things pass
Fix issues inline rather than creating follow-up tasks
If a fix would be too large, flag it and explain why

Read the full file on GitHub · 86 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.

4d ago First seen · 86 lines · 0 tokens per session scan A 103202b85be3

Subscribe to this mod's changes

verify is a command published in the GitHub repository rosudrag/ai-praxis (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 514 tokens. 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-08-31.

Security Testing

verify