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.
git clone --depth 1 https://github.com/nxtg-ai/forge-pluginWrote 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.
[](https://agentmods.dev/agents/nxtg-ai/forge-plugin/planner)<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.
<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>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.00456 | $0.03123 |
| Opus 5.5 | $0.00182 | $0.01249 |
| Sonnet 5.5 | $0.00091 | $0.00625 |
| Haiku 4.5 | $0.00046 | $0.00312 |
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.
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 workforge_get_tasks— See current task board (what's pending, blocked, done)forge_get_knowledge— Recall past decisions, patterns, and learnings to inform your planforge_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:
- Save it to
.claude/plans/{plan-name}.mdwith YAML frontmatter - Use structured format for tasks, dependencies, estimates
- Create actionable tasks that agents can execute
- 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
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 Changed · +326 lines · +456 tokens per session 8d033224d76a
- 1mo ago First seen · 127 lines · 0 tokens per session scan A a5fbeb6371d5
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.
Other agents, from other repositories
secret-hunter
Adversarial secret-leak detective. Use to find leaked API keys, tokens, passwords, certificates, and credentials across code, git history, env files, build logs, and public branches. Hunts what scanners miss — base64 blobs, encoded keys, and secrets in deleted commits.
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /hookify without arguments.
product-management-orchestrator
Product lifecycle orchestrator managing requirements gathering, stakeholder alignment, feature prioritization, roadmap planning, and user experience coordination.
deployment-orchestrator
Deployment orchestrator managing release automation, environment promotion, rollback procedures, production monitoring, and zero-downtime deployment strategies.
mobile-developer
Expert in mobile app development with React Native, Flutter, and native platforms.
iloom-artifact-reviewer
Use this agent to review workflow artifacts (enhancements, analyses, plans, implementations) before posting. The agent validates quality and completeness against artifact-specific criteria and provides actionable feedback for improvements.\n\nExamples:\n \nContext: Orchestrator wants to review an enhancement before…