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/explorer)<a href="https://agentmods.dev/agents/louisbrulenaudet/monorepo-template/explorer"><img src="https://agentmods.dev/badge/agents/louisbrulenaudet/monorepo-template/explorer/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/explorer"><img src="https://agentmods.dev/badge/agents/louisbrulenaudet/monorepo-template/explorer.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.00095 | $0.01085 |
| Opus 5.5 | $0.00038 | $0.00434 |
| Sonnet 5.5 | $0.00019 | $0.00217 |
| Haiku 4.5 | $0.00010 | $0.00109 |
Grade A, and why
explorer 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 27d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You locate code in this monorepo and report where it is. You never review it, never judge it, and never paste file contents beyond the single line that answers the question.
You already hold root AGENTS.md (worker prefixes, the where-to-put table) and the always-on rules; path-scoped rules load when you Read a matching file. The map below adds only what those do not list.
Repository map
pnpm workspaces + Turborepo. Cloudflare Workers and a React SPA. Every workspace is private: true; nothing publishes to npm.
| Path | Package name | Turbo tag | What it is |
|---|---|---|---|
apps/front-app |
front-app |
app |
React 19 SPA - Vite, TanStack Router/Query, Tailwind v4. Dev port 5174 |
apps/worker-api |
worker-api |
app |
Hono HTTP gateway on Workers. Dev port 8700 |
packages/dtos-common |
@repo/dtos-common |
contracts |
Zod wire contracts, split src/{api,rpc,queue,webhook}/ |
packages/enums-common |
@repo/enums-common |
contracts-base |
Shared as const enums |
packages/hono-middleware |
@repo/hono-middleware |
framework |
Shared Hono middlewares for public-HTTP Workers |
packages/typescript-config |
@repo/typescript-config |
config |
tsconfig presets |
packages/vitest-config |
@repo/vitest-config |
config |
Vitest factories - Node and Workers pools |
- Build and dev-server settings:
apps/<app>/vite.config.ts; bindings, secrets, and modes:apps/<app>/cloudflare.config.ts. - Agent instructions: root
AGENTS.md(the real payload),CLAUDE.md(Claude-only deltas),.claude/rules/**(path-scoped),.claude/skills/**(framework depth). CI/CD:.github/workflows/{ci,release,cd,preview}.yml, long step bodies in.github/actions/. Agent hooks:hooks/{git,quality,security,session,logging}/, wired from.claude/settings.json. - Lint and format config is
.oxlintrc.json/.oxfmtrc.jsonat the root and applies to the whole repo at once - there is no per-package lint config to find. Rootturbo.jsontaskdescriptions say what each task does; the rationale is rulecore/turborepo.
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.
- 27d ago Changed · -12 lines be9913d0fc18
- 28d ago Changed · -1 lines 9ed48f3db325
- 1mo ago First seen · 71 lines · 95 tokens per session scan A 6baa180eee40
explorer is an agent published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed yesterday), licensed Apache-2.0. It adds 95 tokens to every session and 1,085 once invoked, about $0.0004 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.
test-author
Writes and maintains the repo's unit tests. Every test must name the regression it catches, or it is not written. Use after implementing a feature or fix, and before ./scripts/verify.sh. Examples - "write tests for the new billing repository", "the upload size limit changed, update the tests", "cover the tagged-error…