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/commands/nxtg-ai/forge-plugin/agent-assign)<a href="https://agentmods.dev/commands/nxtg-ai/forge-plugin/agent-assign"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/agent-assign/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/commands/nxtg-ai/forge-plugin/agent-assign"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/agent-assign.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.00005 | $0.01142 |
| Opus 5.5 | $0.00002 | $0.00457 |
| Sonnet 5.5 | $0.00001 | $0.00228 |
| Haiku 4.5 | $0.00001 | $0.00114 |
Grade A, and why
agent-assign 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NXTG-Forge Agent Assignment
You are the Agent Coordinator - intelligently assign tasks to the best available agent based on the task requirements.
Parse Arguments
Arguments received: $ARGUMENTS
Options:
<task description>: Describe the task to assign--list: Show all available agents and their specialties--auto: Auto-assign based on task analysis (default)--agent <name>: Manually assign to specific agent
Step 0: Check Orchestrator Task Board
Before assigning agents, check if the orchestrator has tasks ready:
- Call
forge_get_tasksto see all pending/assigned/blocked tasks - Call
forge_get_stateto see active file locks and project state - If there are pending orchestrator tasks, offer to assign agents to those first
This connects the plugin's agent system to the orchestrator's task management.
Step 1: Inventory Available Agents
Available agents (from NXTG-Forge plugin):
The following agents are available via the Task tool. They don't need to be in .claude/agents/ -- they're loaded from the plugin automatically.
Built-in agents (22):
- builder - Code implementation and feature building
- planner - Architecture and planning
- guardian - Quality gate and governance enforcement
- detective - Bug investigation and root cause analysis
- security - Security auditing and vulnerability scanning
- api - API design and implementation
- analytics - Data analysis and metrics
- compliance - Compliance verification
- database - Database design and queries
- devops - CI/CD and deployment
- docs - Documentation writing
- governance-verifier - Governance validation
- integration - Service integration
- learning - Knowledge extraction and learning
- orchestrator - Multi-agent orchestration
- performance - Performance optimization
- refactor - Code refactoring
- release-sentinel - Release readiness checking
- testing - Test writing and coverage
- ui - UI/UX implementation
- oracle - Strategic analysis and advice
- nxtg-ceo-loop - Autonomous CEO decision mode
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 2b35fec43231
- 1mo ago Changed · +36 lines · +5 tokens per session ede7e4235042
- 1mo ago First seen · 118 lines · 0 tokens per session scan A b286c9684ec7
agent-assign is a command published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 5 tokens to every session and 1,142 once invoked, about $0.0000 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 commands, from other repositories
paul:help
Show available PAUL commands and usage guide.
paul:verify
Guide manual user acceptance testing of recently built features.
deep-audit.skeleton
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects, stack.orm, stack.authmethod Example output.
mutate
Run mutation testing to verify test quality. Builds a custom mutation tool or uses an existing framework, runs mutations, and reports the mutation score with surviving mutants.
hatch3r-refactor-plan
Plan a refactoring or migration effort -- spawn parallel researchers, produce refactoring spec, ADR(s), and phased todo.md entries for board-fill.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.