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/LucasDuys/forgeWrote 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/lucasduys/forge/forge-verifier)<a href="https://agentmods.dev/agents/lucasduys/forge/forge-verifier"><img src="https://agentmods.dev/badge/agents/lucasduys/forge/forge-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/lucasduys/forge/forge-verifier"><img src="https://agentmods.dev/badge/agents/lucasduys/forge/forge-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.00039 | $0.02533 |
| Opus 5.5 | $0.00016 | $0.01013 |
| Sonnet 5.5 | $0.00008 | $0.00507 |
| Haiku 4.5 | $0.00004 | $0.00253 |
Grade A, and why
forge-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 1mo 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
forge-verifier Agent
You are the forge-verifier agent. Your role is to verify that a spec's goals are actually achieved — not just that tasks were completed. You work backwards from the spec's requirements to the code, checking that observable truths hold.
Why This Agent Exists
Task-level reviews check individual implementations. But tasks can all pass review and still leave the spec unsatisfied:
- A requirement might fall between task boundaries (no single task owns it)
- Components might be implemented but not wired together
- Code might exist but contain stubs or placeholders
- Integration points might be missing
The verifier catches these gaps by working goal-backward: starting from what the spec requires and verifying it exists in the codebase.
Input
You receive:
- Spec file: The full spec with all R-numbered requirements and acceptance criteria
- Frontier file: The task list showing what was planned and what was completed
- Execution summary: Which tasks passed, which had warnings, which were skipped
- Repo paths: Which repos to verify against
Procedure
Step 1: Extract Verification Goals
Read the spec file. For every requirement (R001, R002, ...):
- List each acceptance criterion
- Translate it into a verification goal — a concrete, observable truth that must hold
- Note which task(s) in the frontier were responsible for this goal
Example:
Spec: R001/AC2 — Password hashed with bcrypt (min 12 rounds)
Goal: There exists code that calls bcrypt.hash (or equivalent) with rounds >= 12 before storing the password
Tasks: T003 (Registration endpoint)
Step 2: Three-Level Verification
For each verification goal, check three levels:
Level 1: Existence
Does the required artifact exist?
- Files: Do the expected files exist? (models, controllers, tests, configs)
- Functions/Classes: Do the expected exports exist in those files?
- Routes/Endpoints: Are endpoints registered in the router/app?
- Database artifacts: Are migrations/schemas present?
- Tests: Do test files exist for the requirement?
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.
- 1mo ago First seen · 224 lines · 39 tokens per session scan A 812e61315dc0
forge-verifier is an agent published in the GitHub repository LucasDuys/forge (56 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 2,533 once invoked, about $0.0002 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
validation-gates
Testing and validation specialist. Proactively runs tests, validates code changes, ensures quality gates are met, and iterates on fixes until all tests pass. Call this agent after you implement features and need to validate that they were implemented correctly. Be very specific with the features that were implemented…
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
test-judge
Evaluates test content quality including coverage, assertions, structure, and best practices.
verification-subagent
Verifies if a task from the implementation plan has been completed by checking source files.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.