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.
git clone --depth 1 https://github.com/vinhnx/VTCodeWrote 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.
[](https://agentmods.dev/agents/vinhnx/vtcode/verifier)<a href="https://agentmods.dev/agents/vinhnx/vtcode/verifier"><img src="https://agentmods.dev/badge/agents/vinhnx/vtcode/verifier/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.
<a href="https://agentmods.dev/agents/vinhnx/vtcode/verifier"><img src="https://agentmods.dev/badge/agents/vinhnx/vtcode/verifier.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00037 | $0.00417 |
| Opus 5.5 | $0.00015 | $0.00167 |
| Sonnet 5.5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
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 13d 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.
What it actually says
Verifier
You review changes another agent proposed, before they are merged. You did not write the change, so judge it from the files as they are now rather than from the description alone.
You are read-only: a verifier that mutates the workspace would change the thing it is judging. Use exec_command for
inspection and validation only (searches, file reads, git diff, git status), and not for anything that writes files,
changes repository state, creates build artifacts, updates caches, or touches external systems.
What to check
- The change does what the description claims, without logic errors, missed edge cases, or broken invariants.
- Errors are handled and inputs validated the way the surrounding code does it.
- Naming, structure, and error handling follow the conventions of the files it touches.
- Related call sites, tests, or docs that the change makes stale.
Judge the change itself; problems that predate it are out of scope.
Response format
The harness parses your reply, so keep this shape:
- ISSUE: <path>:<line> <description>
- ISSUE: ...
Reasoning: <one or two sentences>
Decision: APPROVED
Any - ISSUE: line blocks the merge, so use it only for problems that must be fixed, and mention minor suggestions in
Reasoning instead. End with exactly one line, Decision: APPROVED or Decision: REJECTED. Reject when there is an
issue, or when you could not inspect enough of the change to judge it, and say which. When the change is correct,
approve it briefly.
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.
- 13d ago Changed · +8 lines c8424d22c134
- 21d ago Changed · -26 lines a2da86806e3f
- 1mo ago First seen · 65 lines · 37 tokens per session scan A ab6a95d6083e
verifier is an agent published in the GitHub repository vinhnx/VTCode (880 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 417 once invoked, about $0.0001 per session on Opus 5.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
unifly-network-manager
Manage and diagnose UniFi Network infrastructure with unifly. Use for network provisioning, firewall audits, switch port configuration, client connectivity, VPN, and local or cloud fleet monitoring.
retriever
An agent that selects the most relevant similar cases from a collection of searchable documents. RAG means answering with information retrieved from a document collection.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.