planner

A planning role for software changes. It decides the approach and writes a specific list of files, constraints, and checks before implementation starts.

In plain words
What is it for?
Use it for features, refactors, or architecture questions to inspect project rules and relevant source files, identify invariants and open questions, and produce a bounded implementation plan.
Why use it?
It reduces guesswork by making the intended scope and architecture fit explicit before code is edited.

Agent

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.

agentmods
npx agentmods add agents/xhulz/raze/planner
Clone the repo
git clone --depth 1 https://github.com/xhulz/raze
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 186 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 $0.00000 $0.00186
Opus 5 $0.00000 $0.00093
Sonnet 5 $0.00000 $0.00037
Haiku 4.5 $0.00000 $0.00019

Measured 2d ago against content hash 1f9ae5f47cef, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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.

.ia/agents/planner.md · 31 lines

What it actually says

Planner

Purpose

Decide the approach before any code changes. Produce a concrete, bounded plan.

When activated

  • feature, refactor, architecture-question tasks (see routing.md)

Required reads before planning

  • rules.md
  • memory/invariants.md
  • memory/decisions.md
  • Relevant entries in retrieval/file-map.md
  • Affected source files under src/

Output

  • Explicit list of files to change and why
  • Explicit list of files NOT to change
  • Call out any invariant that constrains the approach
  • Flag any open question that blocks a decision

Done when

  • The plan is specific enough that the Implementer can act without asking follow-up questions
  • Architecture fit has been confirmed against memory/invariants.md
  • No hallucinated symbols, paths, or APIs appear in the plan
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. 2d ago First seen · 31 lines · 0 tokens per session scan A 1f9ae5f47cef

Subscribe to this mod's changes

planner is an agent published in the GitHub repository xhulz/raze (5 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 186 tokens. 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.

Related

Other agents, from other repositories

contract-auditor

Solidity contract specialist for the generate → audit → fix → deploy lifecycle. Use when writing, reviewing, auditing, or deploying smart contracts. Enforces the audit-before-deploy discipline and never deploys without an explicit human acknowledgement.

ChainGPT-org/chaingpt-claude-skill · 51 tokens

deploy-ops

Railway deployment and operations agent — Railway service deploys, health checks, log tailing, infrastructure troubleshooting. Use for deployment and ops tasks.

0xSoftBoi/suwappubot · 33 tokens

webapp-dev

React webapp specialist — Telegram Mini App components, hooks, contexts, pages. Use for any work in webapp/ or packages/shared/.

0xSoftBoi/suwappubot · 32 tokens

attacker

Adversarial reviewer. Reads contract code with one goal — find a way to steal, brick, or grief. Use after a vuln-skill pass to identify exploit chains the skill library may have missed individually.

omermaksutii/RugProof · 45 tokens

suwappu-lead

Heavy cross-service planner (Opus) — use ONLY for genuinely large, multi-service architecture/planning that wants a second Opus brain. Day-to-day routing is done by the main Sonnet conductor directly (see CLAUDE.md "Conductor protocol"); do NOT spawn this agent just to delegate a single-service task.

0xSoftBoi/suwappubot · 72 tokens

bot-dev

Python Telegram bot specialist — handlers, services, models, swap logic, wallet management, WhatsApp, copy trading, perps, token security. Use for any work in bot/, api/, database/, or tests/.

0xSoftBoi/suwappubot · 46 tokens