agentmods.dev

verify

A project health check that runs backend, frontend, build, integration, security, and change-review checks.

In plain words
What is it for?
Use it before handing off changes to check Rust and TypeScript code, builds, frontend-backend command links, unsafe patterns, secrets, and uncommitted diffs.
Why use it?
It gathers common failures in one verification pass instead of requiring developers to remember and run each check separately.

Command for Claude Code

39 2d ago A scan 0 tokens original MIT
View the source file talayash/agentrium
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/talayash/agentrium/verify
Clone the repo
git clone --depth 1 https://github.com/talayash/agentrium

Made for: Claude Code.

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 460 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.00460
Opus 5 $0.00000 $0.00230
Sonnet 5 $0.00000 $0.00092
Haiku 4.5 $0.00000 $0.00046

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

.claude/commands/verify.md · 65 lines

What it actually says

Verify

Run a full verification pipeline to check project health.

Instructions

Run ALL of the following checks and report results. Do not stop on first failure - run everything.

1. Rust Backend

cd src-tauri && cargo check 2>&1

cd src-tauri && cargo clippy -- -W clippy::all 2>&1

cd src-tauri && cargo fmt --check 2>&1

2. TypeScript Frontend

npx tsc --noEmit 2>&1

3. Build Test

npm run build 2>&1

4. IPC Contract Check

  • Verify every #[tauri::command] in commands.rs is registered in main.rs
  • Verify every invoke() call in src/ references a valid command
  • Check event name consistency between emit() and listen()

5. Security Quick Scan

  • Search for unwrap() in production code paths (not tests)
  • Search for hardcoded secrets/tokens/passwords
  • Search for eval(), innerHTML, dangerouslySetInnerHTML
  • Check that cmd /C calls properly escape user input

6. Diff Review (if uncommitted changes exist)

  • Run git diff and review for:
    • Accidentally committed debug code (console.log, dbg!, println!)
    • TODO/FIXME without context
    • Large files that shouldn't be committed

Report Format

## Verification Report

| Check | Status | Details |
|-------|--------|---------|
| Rust compile | ✅/❌ | ... |
| Clippy | ✅/❌ | ... |
| Rust format | ✅/❌ | ... |
| TypeScript | ✅/❌ | ... |
| Vite build | ✅/❌ | ... |
| IPC contracts | ✅/❌ | ... |
| Security scan | ✅/❌ | ... |
| Diff review | ✅/❌ | ... |

**Overall: PASS / FAIL (N issues)**
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 · 65 lines · 0 tokens per session scan A 788e2e058111

Subscribe to this mod's changes

verify is a command published in the GitHub repository talayash/agentrium (39 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 460 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.

Code reviewFrontendSecuritybuildersclaude-codegrid-viewprofilesvibe-coding
Related

Other commands, from other repositories

spec-design

Create comprehensive technical design for a specification.

kbwo/ccmanager · 7 tokens

vibe-agents

Step 4 of the vibe-coding workflow: generate AGENTS.md + tool configs so the AI builder stays on track.

KhazP/vibe-coding-prompt-template · 0 tokens

validate-gap

Analyze implementation gap between requirements and existing codebase.

kbwo/ccmanager · 9 tokens

spec-impl

Execute spec tasks using TDD methodology.

kbwo/ccmanager · 7 tokens

oss-docs

(user-owned) oss-docs harness — README 4-locale + docs-site publishing for the moai-adk-go OSS project (adk.mo.ai.kr, Vercel auto-deploy).

modu-ai/moai-adk · 40 tokens

fix

Auto-detect and fix LSP errors, linting issues, and type errors.

modu-ai/moai-adk · 16 tokens