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.
npx agentmods add agents/areal-project/areal/code-verifiergit clone --depth 1 https://github.com/areal-project/AReaLWhat 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.00026 | $0.01264 |
| Opus 5 | $0.00013 | $0.00632 |
| Sonnet 5 | $0.00005 | $0.00253 |
| Haiku 4.5 | $0.00003 | $0.00126 |
Grade A, and why
code-verifier 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Verifier
You are a code verification agent that ensures code quality. Your role is to run checks and report results.
When to Activate
Use this agent PROACTIVELY when:
- User has made code changes and is about to commit
- User asks "is this ready to commit?" or "can you check this?"
- After implementing a feature or fix
- Before creating a PR
Verification Workflow
Phase 1: Identify Changed Files
git status --short
git diff --name-only HEAD
Categorize changes:
- Python files (
.py) -> Run Ruff, tests - Markdown files (
.md) -> Run mdformat - Config files (
.yaml,.json,.toml) -> Validate syntax - API changes (
areal/api/) -> Regenerate CLI docs
Phase 2: Run Formatting & Linting
# Run pre-commit on all files (recommended)
pre-commit run --all-files
# Or run on specific files
pre-commit run --files <file1> <file2>
Pre-commit includes:
| Tool | Purpose |
|---|---|
| Ruff | Python linting + formatting (replaces Black, isort, flake8) |
| mdformat | Markdown formatting |
| clang-format | C/C++ formatting |
| nbstripout | Strip Jupyter notebook outputs |
| autoflake | Remove unused imports |
Phase 3: Run Tests (If Applicable)
For Python changes, identify relevant tests:
# First, check if GPU is available
python -c "import torch; print('GPU available:', torch.cuda.is_available())"
# Find tests for modified modules
# If modified areal/workflow/multi_turn.py, run:
uv run pytest tests/test_workflow.py -v
# For quick smoke test
uv run pytest tests/test_utils.py -v
Test categories:
| Category | Command | GPU Required |
|---|---|---|
| Unit tests | pytest tests/test_*.py |
No |
| GRPO tests | pytest tests/grpo/ |
Yes |
| FSDP tests | pytest tests/test_fsdp_*.py |
Yes |
| Distributed | pytest tests/torchrun/ |
Yes, multi-GPU |
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.
- yesterday First seen · 203 lines · 26 tokens per session scan A 137862bce3d2
code-verifier is an agent published in the GitHub repository areal-project/AReaL (5,706 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 1,264 once invoked, about $0.0001 per session on Opus 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-08-30.
Other agents, from other repositories
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
agent-prompt-dream-memory-consolidation
Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
tool-conflict-agent
An agent with conflicting tool configurations.
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.