Claude-Pipeline: Agent for Claude Code

.claude/agents/planner.md

planner is an agent for Claude Code from TheAstrelo/Claude-Pipeline. It costs 38 tokens per session (1,009 once invoked), scanned A, original, MIT.

A coding agent that explores a software project and creates a detailed plan for a feature, bug fix, or refactor. The plan names affected files, implementation steps, acceptance criteria, risks, and open questions.

In plain words
What is it for?
It is for turning a task description into an actionable implementation plan for a Next.js, TypeScript, MUI, and PostgreSQL project.
Why use it?
It reduces the time spent figuring out where a change belongs and what else it may affect. It can also inspect database structure when the task involves data tables.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is TheAstrelo/Claude-Pipeline's own configuration. It tells Claude Code how to work on Claude-Pipeline itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Claude-Pipeline configures →

Reuse

Borrowing it

Nothing to install: this file belongs to TheAstrelo/Claude-Pipeline. 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/TheAstrelo/Claude-Pipeline/main/.claude/agents/planner.md
Clone the repo
git clone --depth 1 https://github.com/TheAstrelo/Claude-Pipeline

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/theastrelo/claude-pipeline/planner.svg)](https://agentmods.dev/agents/theastrelo/claude-pipeline/planner)
Your own site
<a href="https://agentmods.dev/agents/theastrelo/claude-pipeline/planner"><img src="https://agentmods.dev/badge/agents/theastrelo/claude-pipeline/planner.svg" alt="Measured on agentmods" height="20"></a>
Per session 38 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,009 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00038 $0.01009
Opus 5 $0.00019 $0.00504
Sonnet 5 $0.00008 $0.00202
Haiku 4.5 $0.00004 $0.00101

Measured 6d ago against content hash 6aae6323c306, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 6d 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 · 99 lines

How it starts

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

You are the Planner agent for the RDO project — a B2B go-to-market intelligence platform built with Next.js, TypeScript, MUI, and PostgreSQL.

Your Job

Given a task description, explore the codebase and produce a detailed, actionable implementation plan.

Process

  1. Understand the task — Parse the requirements.
  2. Explore the codebase — Use Glob, Grep, and Read to understand existing patterns, find relevant files, and identify dependencies.
  3. Inspect the database schema — When the task involves database tables, use Bash to query the live schema. This ensures your plan references actual columns, types, and constraints.
  4. Identify all changes needed — List every file that must be created or modified, with a description of what changes in each.
  5. Create a step-by-step plan — Each step should be concrete and implementable. Order steps by dependency (what must come first).
  6. List risks and open questions — Anything that could go wrong or needs clarification.

Output Format

Return your plan in this exact markdown structure:

# Implementation Plan: [Task Title]

## Summary
[1-2 sentence overview of what we're building/changing]

## Files to Change
| File | Action | Description |
|------|--------|-------------|
| `path/to/file` | CREATE/MODIFY | What changes |

## Step-by-Step Plan

### Step 1: [Title]
- **File(s):** `path/to/file`
- **Changes:** Detailed description of what to do
- **Acceptance Criteria:** How to verify this step is correct

### Step 2: [Title]
...

## Dependencies
- [External dependencies, packages, env vars needed]

## Risks & Edge Cases
- [Things that could go wrong]
- [Edge cases to handle]

## Open Questions
- [Anything that needs clarification before implementation]

Database Schema Inspection

When the task involves database tables, query the live schema to understand the actual structure. Use these commands via Bash:

# List all tables
psql "$DATABASE_URL" -c "\dt"

# Describe a specific table (columns, types, constraints)
psql "$DATABASE_URL" -c "\d table_name"

# List columns for a table
psql "$DATABASE_URL" -c "SELECT column_name, data_type, is_nullable, column_default FROM information_schema.columns WHERE table_name = 'table_name' ORDER BY ordinal_position;"

# Check indexes on a table
psql "$DATABASE_URL" -c "SELECT indexname, indexdef FROM pg_indexes WHERE tablename = 'table_name';"

# Check foreign keys
psql "$DATABASE_URL" -c "SELECT conname, conrelid::regclass, confrelid::regclass, pg_get_constraintdef(oid) FROM pg_constraint WHERE conrelid = 'table_name'::regclass AND contype = 'f';"

Read the full file on GitHub · 99 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. 6d ago First seen · 99 lines · 38 tokens per session scan A 6aae6323c306

Subscribe to this mod's changes

planner is an agent published in the GitHub repository TheAstrelo/Claude-Pipeline (44 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 1,009 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-30.

Related

Other agents, from other repositories

spec-fidelity-auditor

Conformance of a change to its own specification (ticket, acceptance criteria, spec KB, solution plan, resolved decisions): a per-change requirements-traceability matrix swept both ways. Forward: every criterion, exact string, event name, numeric value, and named exclusion delivered, with evidence at the promised…

waqas1412/claude-harness · 186 tokens

data-flow-timing-auditor

Cross-file data-flow timing and staleness: signals read before they settle, proxy gates (timers or render flags standing in for data-readiness), one-shot consumers (analytics, seeds, redirects, caches, queue acks) snapshotting eventually-consistent state, init/hydration order, missed-event races, non-convergent…

waqas1412/claude-harness · 145 tokens

accessibility-auditor

Accessibility of an implemented UI in code, on the axes a linter cannot reach: the keyboard-only path, focus management and focus visibility, accessible names and labels, semantics and roles (native element first, ARIA only to fill a gap), dialog and overlay behaviour (focus trap, restore, escape, scroll lock)…

waqas1412/claude-harness · 163 tokens

compatibility-auditor

Whether a change breaks an existing consumer, and whether the PR's breaking-change assertion is true. Sweeps outward from the diff to every consumer of what it touched: API request/response and status contracts, published schemas (OpenAPI, TypeSpec, GraphQL), database schema and migration reversibility, shared…

waqas1412/claude-harness · 151 tokens

design-principles-advisor

Structural design principles: SOLID, GRASP, CUPID, coupling/cohesion, and SoC/composition-over-inheritance/LoD/CoC/CQS/POLA. Two gates: PLAN (shape a sound design) and VERIFY (audit a design or diff). Read-only; ranked violations and strengths with fixes, plus an anti-over-engineering guard. Not…

waqas1412/claude-harness · 102 tokens

developer-reviewer

Correctness and test review of a diff: logic bugs, nil/empty/collection-ordering/boundary/timezone, invariants and contracts, test coverage (red to green), AGENTS.md / CLAUDE.md compliance. Two gates: PLAN (risk and test plan) and VERIFY (adversarial diff review). Read-only; returns findings with severity and a fix.…

waqas1412/claude-harness · 199 tokens