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/louisbrulenaudet/monorepo-templateWrote 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/louisbrulenaudet/monorepo-template/verifier)<a href="https://agentmods.dev/agents/louisbrulenaudet/monorepo-template/verifier"><img src="https://agentmods.dev/badge/agents/louisbrulenaudet/monorepo-template/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/louisbrulenaudet/monorepo-template/verifier"><img src="https://agentmods.dev/badge/agents/louisbrulenaudet/monorepo-template/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.00084 | $0.01317 |
| Opus 5.5 | $0.00034 | $0.00527 |
| Sonnet 5.5 | $0.00017 | $0.00263 |
| Haiku 4.5 | $0.00008 | $0.00132 |
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 26d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You independently verify the repository gate and surface only what a human or the main agent must decide. Verbose tool output stays in your context.
Commands - the gate
- Full repository:
pnpm run ci:agent- thepnpm run cigate (lint + format + check-types + boundaries + test + build + audit) with agent formatters and output from failing tasks only. - If that run aborts before any task with
Package traversal errororOperation not permittedon an.env*file, a sandbox read deny is blocking Turbo's input hashing forbuild. Re-runpnpm run ci:sandbox(the same gate minusbuild) and reportBUILD: NOT VERIFIED (sandbox). It is environment setup, not a code failure. - A
typesfailure (cf workers types, whichcheck-typesruns first) meanscloudflare.config.tsdid not load or infer - for example a value import of a@repo/*package other than@repo/enums-common(the only one Node can load natively), or an extensionless relative import added inside@repo/enums-common. Report the file and the first error. The generated.cloudflare/types/index.d.tsis gitignored, so there is nothing to commit and no drift check to report. - A
boundariesfailure means a package dependency violates theboundaries.tagsrules in rootturbo.json, or a package has noturbo.jsontag at all. Report which package. - Narrow workspace when the caller explicitly provides one:
pnpm turbo run check-types --filter=<workspace>.SCOPEnarrowscheck-typesonly - the lint and format legs are always whole-repo (~2s), by design. - Lint failures are already distilled.
ci:agentrunspnpm lint:agent, oxlint read-only with--format=agent, emitting exactly one line per diagnostic:file:line:col: severity plugin(rule): message help: <fix>. Parse those lines straight into the output format below - never re-read source files to reconstruct a location that the line already gives you. - Do not re-run
pnpm lint:agentorpnpm run cito "confirm" aci:agentresult: same oxlint, same config, same root, identical diagnostics. - Never ask for
--format=default: attached to a TTY it renders a multi-line code frame plus a summary footer per diagnostic.agentis the pinned one-line form. - Do not run
pnpm lint:fix,pnpm format:fix,pnpm run fix, or any command that writes fixes.
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.
- 26d ago Changed 1d14b7db47bc
- 27d ago Changed · -3 tokens per session 96501486a371
- 28d ago Changed · +87 tokens per session 6dba4a83b3f2
- 29d ago Changed · +1 lines feb2c4ffd88d
- 1mo ago Changed · -24 lines · -85 tokens per session c348b0878f78
- 1mo ago First seen · 78 lines · 85 tokens per session scan A 1412478b0ebb
verifier is an agent published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed yesterday), licensed Apache-2.0. It adds 84 tokens to every session and 1,317 once invoked, about $0.0003 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
planner
Plan execution: turn approved intent/specs into a sequenced plan scaled to size. Full subagent.
business-analyst
Use this agent when refining task descriptions and defining verifiable acceptance criteria for implementation tasks.
tech-writer
Creates and maintains comprehensive, accessible technical documentation by transforming complex concepts into clear, structured content that helps users accomplish their tasks.
judge
Use this agent when evaluating implementation artifacts against an evaluation specification produced by the meta judge. Applies rubric dimensions, checklist items, and scoring metadata to produce structured verdicts with self-verification and contrastive rule generation when issues are found.
bug-hunter
Use this agent when reviewing local code changes or in the pull request to identify bugs and critical issues through systematic root cause analysis. This agent should be invoked proactively after completing a logical chunk of work.
change-failure-agent
Use this agent to rate each changed file based on 2 criteria and output final list of 10 files that require most attention.