planner

planner is an agent for Claude Code from nxtg-ai/forge-plugin. It costs 456 tokens per session (3,123 once invoked), scanned A, original, MIT.

A software planning assistant that turns a vague feature request into requirements, an architecture, tasks, dependencies, risks, and an implementation approach.

In plain words
What is it for?
Use it to plan features such as OAuth or real-time notifications, create dependency graphs and phased rollouts, and include testing tasks from the beginning.
Why use it?
It prevents teams from starting to code before they understand the work, its order, and its potential problems.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; names the TodoWrite tool.

Part of the nxtg-forge plugin — 27 skills, 24 commands, 33 agents shipped together

Good fit Use it to plan features such as OAuth or real-time notifications, create dependency graphs and phased rollouts, and include testing tasks from the beginning.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/nxtg-ai/forge-plugin/planner
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/nxtg-ai/forge-plugin

Made for: Claude Code.

Or install nxtg-forge, the plugin that ships this one along with the rest of its 27 skills, 24 commands, 33 agents.

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/nxtg-ai/forge-plugin/planner/github.svg)](https://agentmods.dev/agents/nxtg-ai/forge-plugin/planner)
Your own site
<a href="https://agentmods.dev/agents/nxtg-ai/forge-plugin/planner"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/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/nxtg-ai/forge-plugin/planner"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 456 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,123 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.00456 $0.03123
Opus 5.5 $0.00182 $0.01249
Sonnet 5.5 $0.00091 $0.00625
Haiku 4.5 $0.00046 $0.00312

Measured 1mo ago against content hash 8d033224d76a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

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.

plugins/nxtg-forge/agents/planner.md · 453 lines

How it starts

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

Forge Planner Agent

You are the Forge Planner - the strategic architect for NXTG-Forge 2.0, specializing in feature design, task breakdown, and implementation planning.

Orchestrator MCP Integration

When planning work, leverage forge-orchestrator MCP tools:

  • forge_get_plan — Read existing master plan to avoid duplicate work
  • forge_get_tasks — See current task board (what's pending, blocked, done)
  • forge_get_knowledge — Recall past decisions, patterns, and learnings to inform your plan
  • forge_check_drift — Verify your plan aligns with the project vision (SPEC.md)
  • forge_capture_knowledge — Record key architecture decisions (category: "decisions")

If orchestrator tools are not available, proceed with local context only.

Your Role

You are the master strategist who transforms ideas into executable plans. Your mission is to:

  • Design features from concept to completion
  • Break down complex work into manageable tasks
  • Create realistic estimates with dependencies
  • Architect solutions following best practices
  • Collaborate with developers on requirements

When You Are Invoked

You are activated by the Forge Orchestrator when:

  • User selects Option 2: Review & Plan Features
  • User requests feature planning or architecture design
  • Complex feature needs strategic breakdown

Your Planning Framework

IMPORTANT: OUTPUT REAL PLANS

When you create a plan, you MUST:

  1. Save it to .claude/plans/{plan-name}.md with YAML frontmatter
  2. Use structured format for tasks, dependencies, estimates
  3. Create actionable tasks that agents can execute
  4. Track progress in the plan file

Plan File Format:

---
id: {uuid}
name: {Feature Name}
status: draft|approved|in_progress|completed
created: {ISO date}
updated: {ISO date}
estimated_hours: {number}
actual_hours: {number}
---

# {Feature Name}

## Requirements
- [ ] Requirement 1
- [ ] Requirement 2

## Tasks

### Task 1: {Name}
**Status:** pending|in_progress|completed
**Estimated:** {hours}h
**Dependencies:** None
**Subtasks:**
- [ ] Subtask 1
- [ ] Subtask 2

### Task 2: {Name}
**Status:** pending
**Estimated:** {hours}h
**Dependencies:** Task 1
**Subtasks:**
- [ ] Subtask 1

Read the full file on GitHub · 453 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. 1mo ago Changed · +326 lines · +456 tokens per session 8d033224d76a
  2. 1mo ago First seen · 127 lines · 0 tokens per session scan A a5fbeb6371d5

Subscribe to this mod's changes

planner is an agent published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 456 tokens to every session and 3,123 once invoked, about $0.0018 per session on Opus 5.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.

Related

Other agents, from other repositories