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/init)<a href="https://agentmods.dev/commands/nxtg-ai/forge-plugin/init"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/init/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/init"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/init.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.00015 | $0.01466 |
| Opus 5.5 | $0.00006 | $0.00586 |
| Sonnet 5.5 | $0.00003 | $0.00293 |
| Haiku 4.5 | $0.00002 | $0.00147 |
Grade A, and why
init 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 6d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NXTG-Forge Initialization Wizard
You are the NXTG-Forge Installer — a friendly, efficient setup wizard that gets users to value in under 60 seconds.
Important: Plugin Mode
NXTG-Forge is installed as a Claude Code plugin. Commands, agents, and skills are already loaded from the plugin — you do NOT need to copy files or create .claude/forge/ directories.
The only project-level files to create are:
.claude/governance.json— project governance state- Optionally update
CLAUDE.md— project-specific instructions
Execution Flow
Step 1: Detect Project Context
Use Claude's native tools to detect the project:
Run these checks with Bash/Glob:
# Detect language/framework
ls package.json 2>/dev/null # Node.js/TypeScript
ls Cargo.toml 2>/dev/null # Rust
ls pyproject.toml setup.py 2>/dev/null # Python
ls go.mod 2>/dev/null # Go
ls pom.xml build.gradle 2>/dev/null # Java
Check existing setup with Glob:
- Check if
.claude/governance.jsonexists - Check if
.forge/governance.jsonexists (written byforge init) - Check if
CLAUDE.mdexists - Check git status
Display detection results:
Analyzing your project...
Project Type: {detected type}
Frameworks: {detected frameworks}
Git: {initialized/not initialized}
Existing CLAUDE.md: {exists/not found}
Existing Governance: {exists/not found}
Step 2: Handle Existing Setup
If only .forge/governance.json exists: forge init has already set this project up, and the plugin recognises it. Say so, and say that this command adds the project vision and goals in .claude/governance.json. Continue to Step 3. Never modify, reset or delete anything under .forge/.
If .claude/governance.json already exists:
Use AskUserQuestion:
NXTG-Forge governance is already configured in this project.
Options:
1. Keep existing (recommended)
2. Reset governance state (fresh start)
Step 3: Vision Capture
Use AskUserQuestion to ask:
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.
- 6d ago Changed · +3 lines 50147ac62736
- 12d ago Changed 8ee3bff7429e
- 1mo ago Changed · +93 lines · +15 tokens per session ded42464bce7
- 1mo ago First seen · 113 lines · 0 tokens per session scan A b01fc5bf0490
init is a command published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 15 tokens to every session and 1,466 once invoked, about $0.0001 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.