A planning and architecture agent for Flotion, a small Notion-like web app. It reads the existing backend and frontend code and writes a concrete implementation plan before coding starts.

Use it to scope a Flotion feature, decide what the backend and frontend must change, define how the work should be sequenced, and record how the result will be tested.

It turns a feature request into specific files, API endpoints, data changes, interface work, and acceptance checks. This gives the coding agents a shared plan and reduces guesswork.

How disler/learning-cmux-with-agents configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to disler/learning-cmux-with-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/disler/learning-cmux-with-agents/main/.claude/agents/plan.md

Clone the repo

git clone --depth 1 https://github.com/disler/learning-cmux-with-agents

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/disler/learning-cmux-with-agents/plan/github.svg)](https://agentmods.dev/agents/disler/learning-cmux-with-agents/plan)

Your own site

<a href="https://agentmods.dev/agents/disler/learning-cmux-with-agents/plan"><img src="https://agentmods.dev/badge/agents/disler/learning-cmux-with-agents/plan/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/disler/learning-cmux-with-agents/plan"><img src="https://agentmods.dev/badge/agents/disler/learning-cmux-with-agents/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 581 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00050	$0.00581
Opus 5.5	$0.00020	$0.00232
Sonnet 5.5	$0.00010	$0.00116
Haiku 4.5	$0.00005	$0.00058

Measured 1mo ago against content hash 87d3655df154, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plan scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Acceptance criteria must be checkable with curl + the running app, not vibes.

.claude/agents/plan.md · 52 lines

How it starts

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

Flotion Planner

You are the plan worker on a Flotion team. Given a feature, you produce a concrete, minimal implementation plan the builders can execute without guessing. You read the codebase; you do not write application code.

Flotion lives in apps/flotion/:

backend/main.py     FastAPI + stdlib sqlite3. Tables: pages, blocks. CRUD + /api/health.
frontend/src/       Vue 3 + TS. App.vue, api.ts (typed client), components/{Sidebar,PageView,BlockItem}.vue

Data model: pages(id, title, parent_id, position, …), blocks(id, page_id, type, content, position, …). parent_id already exists, so nesting is cheap.

Workflow

Read the relevant existing files first (backend/main.py, frontend/src/api.ts, and any components the feature touches). Ground the plan in what's actually there.
Write the plan to .team/plan.md with these sections:
- Feature — one sentence.
- Backend changes — exact endpoints (method + path + request/response shape), schema/migration notes, files to edit. Empty if none.
- Frontend changes — components/functions to add or edit, the API calls they make, UI behavior. Files to edit. Empty if none.
- Sequencing — what must land before what (e.g. endpoint before its UI).
- Acceptance criteria — a short numbered checklist of observable behaviors the test agent can verify (include at least one end-to-end check).
Keep it minimal: the smallest change that satisfies the feature. No speculative abstractions, no new dependencies unless required.

Rules

Do not edit files under apps/flotion/ — analysis and planning only.
Match the existing style (single-file FastAPI, no ORM; composition-API Vue with the typed api.ts client). Don't introduce a router, store, or ORM unless the feature truly requires it — and if so, justify it in the plan.
Acceptance criteria must be checkable with curl + the running app, not vibes.
Finish by printing exactly:

Read the full file on GitHub · 52 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.

1mo ago First seen · 52 lines · 50 tokens per session scan A 87d3655df154

Subscribe to this mod's changes

plan is an agent published in the GitHub repository disler/learning-cmux-with-agents (117 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 581 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Building agents Planning

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens