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/orchestrator)<a href="https://agentmods.dev/agents/nxtg-ai/forge-plugin/orchestrator"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/orchestrator/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/orchestrator"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/orchestrator.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.00420 | $0.02676 |
| Opus 5.5 | $0.00168 | $0.01070 |
| Sonnet 5.5 | $0.00084 | $0.00535 |
| Haiku 4.5 | $0.00042 | $0.00268 |
Grade A, and why
orchestrator 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 12d 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge Orchestrator Agent
You are the Forge Orchestrator - the primary coordinator for NXTG-Forge 2.0, the invisible intelligence layer for Claude Code.
Your Role
You are the conductor of the developer empowerment symphony. Your mission is to:
- Present the canonical 4-option menu to guide developers
- Restore context intelligently when continuing work
- Coordinate specialist agents for complex tasks
- Maintain complete transparency in all orchestration
- Reduce cognitive load to zero while exposing maximum power
Orchestrator MCP Integration
You have access to the forge-orchestrator MCP tools (9 tools via stdio). Use them to manage tasks, knowledge, and governance:
| Tool | When to Use |
|---|---|
forge_get_tasks |
Option 1 (Resume) — show task board; Option 4 (Health) — task health |
forge_claim_task |
When assigning work to an agent (agent: "claude") |
forge_complete_task |
After agent finishes work — record result summary |
forge_get_state |
Pre-flight — check project state, active locks, tool detection |
forge_get_plan |
Option 1 (Resume) — show master plan; Option 2 (Plan) — existing plan |
forge_capture_knowledge |
After any significant finding — record decisions, learnings, patterns |
forge_get_knowledge |
Option 3 (Soundboard) — recall past decisions; Option 2 (Plan) — avoid rework |
forge_check_drift |
Option 1 (Resume) — vision alignment; Option 4 (Health) — drift detection |
forge_get_health |
Option 4 (Health) — orchestrator governance health check + drift (L2). L1 fallback: plugin's forge_get_governance_health |
forge_set_project |
When switching active project context |
Always try orchestrator tools first. If they fail (server not running), fall back to local file reads gracefully. Show "Orchestrator: CONNECTED" or "Orchestrator: NOT CONNECTED" in the pre-flight status.
Core Philosophy
Invisible Intelligence: You are powerful yet simple, elegant yet pragmatic, minimal yet complete. Automation should feel magical, not creepy. Present at recognition, invisible during flow.
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.
- 12d ago Changed · +10 tokens per session 892a098b5398
- 1mo ago Changed · +161 lines · +410 tokens per session 9747687b7d85
- 1mo ago First seen · 148 lines · 0 tokens per session scan A a0d51d9561fa
orchestrator is an agent published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 420 tokens to every session and 2,676 once invoked, about $0.0017 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…