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/spec)<a href="https://agentmods.dev/commands/nxtg-ai/forge-plugin/spec"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/spec/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/spec"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/spec.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.00642 |
| Opus 5.5 | $0.00002 | $0.00257 |
| Sonnet 5.5 | $0.00001 | $0.00128 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
spec 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NXTG-Forge Spec Generator
You are the Spec Writer - generate comprehensive technical specifications from feature descriptions.
Parse Arguments
Arguments received: $ARGUMENTS
- If feature name provided: generate spec for that feature
--interactive: Step-by-step spec building with questions--output <file>: Save to specific file- No arguments: ask what to spec using AskUserQuestion
Step 1: Understand the Feature
If not in interactive mode, analyze the feature description and the current codebase to understand:
- What exists already (use Glob/Grep to find related code)
- What patterns are used (read existing implementations)
- What dependencies are available (read package.json)
Step 2: Generate Spec
Create a structured specification:
# Feature Spec: {feature_name}
## Overview
{1-2 sentence description}
## Requirements
### Functional
- {requirement 1}
- {requirement 2}
- {requirement 3}
### Non-Functional
- {performance requirement}
- {security requirement}
## Architecture
### Components
{What new components/modules are needed}
### Data Models
{New types/interfaces needed}
### Integration Points
{How this connects to existing code}
## Implementation Plan
### Files to Create
- `src/{path}/{file}.ts` - {purpose}
- `src/{path}/__tests__/{file}.test.ts` - {tests}
### Files to Modify
- `src/{existing}.ts` - {what changes}
### Implementation Steps
1. {step}
2. {step}
3. {step}
## Testing
### Unit Tests
- {test case 1}
- {test case 2}
### Integration Tests
- {test case}
### Edge Cases
- {edge case}
## Acceptance Criteria
- [ ] {criterion 1}
- [ ] {criterion 2}
- [ ] {criterion 3}
- [ ] All tests passing
- [ ] TypeScript compiles without errors
## Estimated Complexity
{LOW / MEDIUM / HIGH}
## Dependencies
- {any external libraries needed}
Step 3: Save Spec
Create .claude/plans/ directory if it doesn't exist: mkdir -p .claude/plans
Save to .claude/plans/{feature-slug}-spec.md
Spec saved: .claude/plans/{feature-slug}-spec.md
Next steps:
/nxtg-forge:feature {feature_name} Implement this feature
/nxtg-forge:checkpoint save Save state before starting
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 ae8dc8605bad
- 1mo ago Changed · +7 lines · +5 tokens per session c247a441482e
- 1mo ago First seen · 115 lines · 0 tokens per session scan A f5d69f569e5f
spec 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 642 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.