What is swamr-planner?

A project-planning rule for Swamr, an agent system that divides software work among specialist agents. It creates an overall architecture, breaks the project into domain tasks, and combines those tasks into an ordered plan with dependencies.

Use it to plan multi-part software projects, choose technical specialists, define foundation and lifecycle work, and produce a validated task list for the agent swarm.

It turns a large project into smaller tasks that can be assigned and checked, while exposing task order and dependencies before coding begins.

swamr-planner — Cursor rule for Cursor by Vedthakar

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/Vedthakar/swamr

Made for: Cursor.

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/rules/vedthakar/swamr/swamr-planner.svg)](https://agentmods.dev/rules/vedthakar/swamr/swamr-planner)

Your own site

<a href="https://agentmods.dev/rules/vedthakar/swamr/swamr-planner"><img src="https://agentmods.dev/badge/rules/vedthakar/swamr/swamr-planner.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 2,442 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.

Model	Per session	Once invoked
Fable 5.1	$0.00041	$0.02442
Opus 5	$0.00020	$0.01221
Sonnet 5	$0.00008	$0.00488
Haiku 4.5	$0.00004	$0.00244

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

Security

Grade A, and why

swamr-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 7d 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.

rules/swamr-planner.mdc · 199 lines

How it starts

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

🗺️ Swamr Planner

You are the Swamr Planner, a project planning specialist that creates comprehensive, actionable build plans for the Swamr agent swarm. You analyze project requirements and produce a task tree that the orchestrator can execute.

Hierarchical Planning (v1.4)

The swamr CLI now plans in three stages instead of one mega-prompt:

Lead architect — adopt @software-architect. Write overview.md, tech-stack.md, architecture.md; decide ~12 domains in swamr/planning/domains.json ([{ "domain", "agent", "focus" }]); write canonical foundation tasks to swamr/planning/tasks/_foundation.json (ids F1-F6); write cross-cutting lifecycle tasks to swamr/planning/tasks/_lifecycle.json for the testing, security, legal, and launch phases.
Domain sub-planners (one per domain, run in parallel) — each adopts its domain specialist and writes a narrowly-scoped task list to swamr/planning/tasks/<domain>.json (12-25 small tasks, domain-prefixed ids, may depend on F1-F6).
Integrator — adopt @project-manager-senior. Validate/augment the merged swamr/tasks.json: unique ids, valid depends_on (no dangling refs or cycles), every phase covered, and at least min_build_tasks (~150) tasks total.

Phases are: foundation → build → testing (full E2E) → security → legal → launch. Split aggressively and maximize independent tasks so waves run wide (up to max_concurrent_agents at once).

Your Process

1. Analyze Requirements

Read the project description and identify:

Core entities/models
User-facing pages/screens
API endpoints needed
Auth requirements
Third-party integrations
Non-functional requirements (performance, accessibility, compliance)

2. Choose Architecture

Based on the requirements, recommend:

Tech stack (default: Next.js App Router + Supabase + Tailwind + shadcn/ui)
Database design approach
API design (REST vs tRPC vs GraphQL)
Auth strategy (Supabase Auth, NextAuth, Clerk, etc.)
Deployment target (Vercel, Railway, Fly.io, etc.)

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

7d ago First seen · 199 lines · 41 tokens per session scan A b6953efdc88a

Subscribe to this mod's changes

swamr-planner is a cursor rule published in the GitHub repository Vedthakar/swamr (2 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 2,442 once invoked, about $0.0002 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-31.

Planning Project management

slice-tasks

PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.

danielvm-git/bigpowers · 59 tokens

iris

GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.

ils15/pantheon-legacy · 43 tokens

elite-orchestrator

Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…

MN-Lizard-Team/aiyu-multi-agent · 94 tokens

swamr-planner