verify

A verification command checks a code repository by building it, checking types, linting code, running tests, scanning for secrets, reviewing console logs, and showing Git changes.

In plain words
What is it for?
Use quick checks for a build and type check, or full, pre-commit, and pre-pull-request checks. It reports failures, test coverage, exposed secrets, debug logs, and readiness for review.
Why use it?
It gathers common pre-commit and pre-review checks into one report and stops early when the build fails.

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/luohaothu/everything-codex/verify
Clone the repo
git clone --depth 1 https://github.com/Luohaothu/everything-codex
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 368 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00368
Opus 5 $0.00000 $0.00184
Sonnet 5 $0.00000 $0.00074
Haiku 4.5 $0.00000 $0.00037

Measured 2d ago against content hash 2fe5a37818e7, 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 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.

docs/zh-CN/commands/verify.md · 61 lines

What it actually says

验证命令

对当前代码库状态执行全面验证。

说明

请严格按照以下顺序执行验证:

  1. 构建检查

    • 运行此项目的构建命令
    • 如果失败,报告错误并停止
  2. 类型检查

    • 运行 TypeScript/类型检查器
    • 报告所有错误,包含文件:行号
  3. 代码检查

    • 运行代码检查器
    • 报告警告和错误
  4. 测试套件

    • 运行所有测试
    • 报告通过/失败数量
    • 报告覆盖率百分比
  5. Console.log 审计

    • 在源文件中搜索 console.log
    • 报告位置
  6. Git 状态

    • 显示未提交的更改
    • 显示自上次提交以来修改的文件

输出

生成一份简洁的验证报告:

VERIFICATION: [PASS/FAIL]

Build:    [OK/FAIL]
Types:    [OK/X errors]
Lint:     [OK/X issues]
Tests:    [X/Y passed, Z% coverage]
Secrets:  [OK/X found]
Logs:     [OK/X console.logs]

Ready for PR: [YES/NO]

如果存在任何关键问题,列出它们并提供修复建议。

参数

$ARGUMENTS 可以是:

  • quick - 仅构建 + 类型检查
  • full - 所有检查(默认)
  • pre-commit - 与提交相关的检查
  • pre-pr - 完整检查加安全扫描
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.

  1. 2d ago First seen · 61 lines · 0 tokens per session scan A 2fe5a37818e7

Subscribe to this mod's changes

verify is a command published in the GitHub repository Luohaothu/everything-codex (24 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 368 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-30.