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/itdojp/ae-framework/verify-agentgit clone --depth 1 https://github.com/itdojp/ae-frameworkWhat 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.00000 | $0.04703 |
| Opus 5 | $0.00000 | $0.02351 |
| Sonnet 5 | $0.00000 | $0.00941 |
| Haiku 4.5 | $0.00000 | $0.00470 |
Grade A, and why
verify-agent 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 — 709 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Agent Documentation
English
Overview
The Verify Agent is a comprehensive verification and quality assurance system for Phase 5 of the ae-framework. It provides automated verification capabilities including testing, coverage analysis, code quality checks, security scanning, and compliance validation.
Architecture
The Verify Agent consists of two main components:
- Core Agent (
VerifyAgent): Located atsrc/agents/verify-agent.ts - MCP Server Wrapper (
VerifyMCPServer): Located atsrc/mcp-server/verify-server.ts
The MCP server exposes the agent's capabilities as tools that can be used by AI assistants and other systems.
Features
Core Verification Types
- Tests: Unit, integration, e2e, property-based, and contract tests
- Coverage: Line, branch, function, and statement coverage analysis
- Linting: Code style and quality checks using ESLint
- Type Checking: TypeScript type validation
- Security: Vulnerability scanning and dependency auditing
- Performance: Benchmarking and load testing
- Accessibility: API accessibility compliance checks
- Contracts: API contract verification (PACT)
- Specifications: OpenAPI, AsyncAPI, GraphQL, TLA+ validation
- Mutations: Mutation testing for test quality assessment
Quality Metrics
- Cyclomatic complexity
- Maintainability index
- Reliability rating
- Security rating
- Performance rating
- Testability rating
Traceability
- Requirements to code traceability
- Test coverage mapping
- Specification compliance tracking
- Gap analysis and recommendations
Usage
Command Line Scripts
The following npm scripts are available:
# Start MCP server
npm run verify:server
# Run all tests
npm run verify:tests
# Run quality checks (lint + build)
npm run verify:quality
# Run security audit
npm run verify:security
# Run complete verification suite
npm run verify:all
# Initialize verify agent
npm run verify:full
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 · 709 lines · 0 tokens per session scan A aa261592c690
verify-agent is an agent published in the GitHub repository itdojp/ae-framework (2 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,703 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-31.
Other agents, from other repositories
playwright-test-generator
Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…
playwright-test-healer
Use this agent to debug and fix failing SigNoz E2E Playwright tests. Examples — Context: A spec is red. user: 'tests/e2e/tests/dashboards/list.spec.ts is failing, fix it' assistant: 'Using the healer agent to debug each failing scenario and adjust the spec.' Context: After a frontend change a previously-green spec…
playwright-test-planner
Use this agent to create a comprehensive E2E test plan for a SigNoz frontend feature. Examples — Context: A new feature has shipped and we need test coverage. user: 'Plan E2E tests for the alerts list page' assistant: 'I'll use the planner agent to read the relevant frontend source, navigate the page in a real…
codex
Production OpenAI-Codex-capable rootfs/initramfs.
claude
Production Claude-capable rootfs/initramfs.
doc-style
Markdown documentation prose — RFCs, ADRs, files under docs/, and READMEs — follows the same one-paragraph-per-line rule as commit messages. Write each paragraph on a single line; do not hard-wrap prose to a fixed column. The renderer reflows it to the reader's display width, whereas manual mid-paragraph line breaks…