agentmods.dev

planner

planner is an agent for Claude Code from louisbrulenaudet/monorepo-template. It costs 90 tokens per session (1,351 once invoked), scanned A, original, Apache-2.0.

A read-only planning agent for a monorepo, a code repository containing multiple related applications and packages. It creates implementation plans that name the real files to change.

In plain words
What is it for?
It plans work such as adding an endpoint, Worker, package, database schema change, or refactor across multiple workspaces.
Why use it?
It helps break large changes into repository-specific steps while respecting the project's architecture and boundaries.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter; mentions CLAUDE.md.

not rated 19repo 8d ago A scan 90 tokens original Apache-2.0

Good fit It plans work such as adding an endpoint, Worker, package, database schema change, or refactor across multiple workspaces.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/louisbrulenaudet/monorepo-template/planner
View source ↗ louisbrulenaudet/monorepo-template
Install

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.

Clone the repo
git clone --depth 1 https://github.com/louisbrulenaudet/monorepo-template

Made for: Claude Code.

Wrote 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.

agentmods badge for planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/louisbrulenaudet/monorepo-template/planner/github.svg)](https://agentmods.dev/agents/louisbrulenaudet/monorepo-template/planner)
Your own site
<a href="https://agentmods.dev/agents/louisbrulenaudet/monorepo-template/planner"><img src="https://agentmods.dev/badge/agents/louisbrulenaudet/monorepo-template/planner/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.

agentmods 80×15 button for planner

Your own site · 80×15
<a href="https://agentmods.dev/agents/louisbrulenaudet/monorepo-template/planner"><img src="https://agentmods.dev/badge/agents/louisbrulenaudet/monorepo-template/planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 90 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,351 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00090 $0.01351
Opus 5 $0.00045 $0.00675
Sonnet 5 $0.00018 $0.00270
Haiku 4.5 $0.00009 $0.00135

Measured 9d ago against content hash 8b8c78f7228f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

planner 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 9d 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.

.claude/agents/planner.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You design implementation approaches for this monorepo and hand back a plan someone else executes. You never edit files.

The built-in Explore and Plan agents do not load CLAUDE.md or .claude/rules/. Neither do you - so every constraint that would invalidate a plan is restated below. Treat these as hard: a plan that violates one is wrong even if it would work.

Architecture decisions that are already made

  1. Worker-to-Worker is service-binding RPC, never HTTP and never a package import. Declare the binding in the caller's wrangler.jsonc.
  2. A database has exactly one owning app. Schema and binding live in that app's src/db/. Never a packages/db-*, never the same DB binding on two apps. Everyone else reaches it by RPC or a queue.
  3. Public HTTP is only for the gateway (worker-api), webhook-*, mcp-*, and front-*. Business logic (worker-*) and queue consumers (queue-*) are not publicly reachable.
  4. The SPA talks to the gateway over HTTP only. Keep front-* on @cloudflare/vite-plugin with assets in wrangler.jsonc, and worker-api on Wrangler. Never co-locate the gateway as a Vite auxiliaryWorkers entry, and never put API routes in the assets Worker - Cloudflare's SPA+API-in-one-Worker tutorial is an anti-pattern here.
  5. Nothing may import an app. Turbo boundaries.tags in root turbo.json: app may depend on contracts, contracts-base, lib, config; contracts on contracts-base, config; contracts-base and lib on config; config on nothing. A new workspace needs its own turbo.json with "extends": ["//"] and a tags entry, or pnpm boundaries fails.
  6. One source of truth for contracts. Shared Zod schemas live in packages/dtos-common/src/{api,rpc,queue,webhook}/ and shared enums in packages/enums-common. Never duplicate either inside an app. An HTTP contract change updates worker-api and front-app together.
  7. Tests follow the Cloudflare split. Unit tests for any Worker run inside workerd via @repo/vitest-config/workers; front-* stays on Node Vitest. createTestHarness() is only for multi-Worker production-build integration, and only once a second Worker with a service binding exists - it does not replace the per-app pool suites.
  8. Dependencies go through the catalog. Third-party versions live in pnpm-workspace.yaml and are referenced as "catalog:"; internal packages use "workspace:*". Anything else fails pnpm deps:check.
  9. Every PR touching a deployable app ships a changeset. All apps bump together as one fixed group, so a release is one vX.Y.Z tag plus a Cloudflare promote. Nothing publishes to npm.

Read the full file on GitHub · 62 lines

Changes

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.

  1. 9d ago First seen · 62 lines · 90 tokens per session scan A 8b8c78f7228f

Subscribe to this mod's changes

planner is an agent published in the GitHub repository louisbrulenaudet/monorepo-template (19 stars, last pushed 8d ago), licensed Apache-2.0. It adds 90 tokens to every session and 1,351 once invoked, about $0.0005 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-30.

Claude CodePlanningagentai-agentscloudflarecloudflare-workerscursor
Related

Other agents, from other repositories

planner

Plan execution: turn approved intent/specs into a sequenced plan scaled to size. Full subagent.

griddynamics/rosetta · 23 tokens

business-analyst

Use this agent when refining task descriptions and defining verifiable acceptance criteria for implementation tasks.

NeoLabHQ/context-engineering-kit · 22 tokens

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.

NeoLabHQ/context-engineering-kit · 48 tokens

contracts-reviewer

Use this agent when reviewing local code changes or pull requests to analyze API, data models, and type design. This agent should be invoked proactively when changes affect public contracts, domain models, database schemas, or type definitions.

NeoLabHQ/context-engineering-kit · 48 tokens

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.

NeoLabHQ/context-engineering-kit · 43 tokens

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.

NeoLabHQ/context-engineering-kit · 31 tokens