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 instructions/verifyax/verifyax-mcp/claude-mdgit clone --depth 1 https://github.com/verifyax/verifyax-mcpWrote 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/instructions/verifyax/verifyax-mcp/claude-md)<a href="https://agentmods.dev/instructions/verifyax/verifyax-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/verifyax/verifyax-mcp/claude-md.svg" alt="Measured on agentmods" 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.03217 | $0.03217 |
| Opus 5 | $0.01608 | $0.01608 |
| Sonnet 5 | $0.00643 | $0.00643 |
| Haiku 4.5 | $0.00322 | $0.00322 |
Grade A, and why
verifyax-mcp CLAUDE.md 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Persistent project context for Claude Code. Read this first in every session.
What we're building
A Model Context Protocol (MCP) server that exposes the VerifyAX agent-evaluation platform as conversational tools, distributed as an npm package. Plus the typed SDK it sits on top of.
Two packages in one monorepo:
@verifyax/sdk— typed TypeScript client for the VerifyAX REST API. Reusable by any consumer, not MCP-specific.@verifyax/mcp-server— MCP server exposing ~12 tools mapped to user intents. Depends on the SDK.
The MCP server complements (does not replace) the existing verifyax-api skill at https://github.com/verifyax/verifyax-plugins. The skill is for developers writing code; the MCP server is for conversational workflows.
v1 scope and constraints
Update (0.2.0): the constraints below describe the v1 (0.1.x) shape. As of 0.2.0 the server also ships a Streamable HTTP transport + GCP Cloud Run deployment (
verifyax-mcp-server-http), with per-request header auth — i.e. remote hosting, previously a v2 item, has landed. The stdio +VERIFYAX_API_KEYpath below is unchanged and remains the default.
- Local distribution only. Users install via npm and configure the server in their MCP client (Claude Code, Claude Desktop). Remote hosting is v2.
- API key auth. User pastes their VerifyAX key into MCP client config as
VERIFYAX_API_KEY. OAuth is v2. - Blocking-by-default tools. Async polling lives inside the server, invisible to Claude and the user. No
start_job/get_statuspairs in v1. - Structured errors over exceptions. Tools return
{ success: false, reason, suggested_fix }instead of throwing where possible. - Twelve tools. Resist the urge to wrap every endpoint. See the catalogue below.
Architecture decisions (already made — do not re-litigate)
- Language: TypeScript. Faster-moving MCP ecosystem, better tool descriptions support.
- Package manager: pnpm with workspaces.
- SDK and MCP server are separate packages, published under the
@verifyaxnpm scope. - API client style: resource-oriented, like
stripe-node.client.agents.create(...),client.scenarios.generate(...),client.simulations.simulate(...). - Error handling: typed error hierarchy.
VerifyaxErrorbase;AuthError,NotFoundError,ConflictError,JobFailedError,TimeoutError,RateLimitErrorderived. - MCP tool errors: structured. SDK throws; the tool handler catches and translates to MCP tool-result
{ success: false, ... }payloads. Never let raw exceptions escape into MCP output. - Polling: in-SDK helper.
client.jobs.pollUntilTerminal(jobUuid, { timeoutMs, intervalMs }). Used by both SDK consumers and the MCP server. - Logging: stderr only, structured JSON, controlled by
VERIFYAX_MCP_LOG_LEVELenv. stdout is reserved for MCP protocol. - No telemetry in v1. Document this explicitly in the README.
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.
- 5d ago First seen · 202 lines · 3,217 tokens per session scan A 2d2d77613b1e
verifyax-mcp CLAUDE.md is an instructions file published in the GitHub repository verifyax/verifyax-mcp (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 3,217 tokens to every session, about $0.0161 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-31.
Other instructions, from other repositories
nasde-toolkit CLAUDE.md
Instructions for NoesisVision/nasde-toolkit, covering nasde-toolkit, package structure, how to run, testing and development workflow.
agent-triage CLAUDE.md
Instructions for converra/agent-triage, covering agent-triage, architecture, core types, key modules and rules.
agent-triage copilot-instructions.md
Instructions for converra/agent-triage, covering copilot instructions for agent-triage, project context, code style, key patterns and when suggesting code.
any-agent AGENTS.md
AGENTS.md instructions for mozilla-ai/any-agent, covering claude.md, where to look first, project structure & module organization, build, test, and development commands and coding style & naming conventions.
eval-view AGENTS.md
AGENTS.md instructions for hidai25/eval-view, covering evalview agent instructions, what evalview is, core concepts, testcase and evaluationresult.
AgentKernelArena AGENTS.md
AGENTS.md instructions for AMD-AGI/AgentKernelArena, covering agents.md, purpose, repository map and sources of truth, architecture boundaries and working practices.