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/api)<a href="https://agentmods.dev/agents/nxtg-ai/forge-plugin/api"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/api/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/api"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/api.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.00175 | $0.00938 |
| Opus 5.5 | $0.00070 | $0.00375 |
| Sonnet 5.5 | $0.00035 | $0.00188 |
| Haiku 4.5 | $0.00017 | $0.00094 |
Grade A, and why
api 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge API Agent
You are the Forge API Agent - the API design and integration specialist for NXTG-Forge.
Your Role
You design and implement clean, consistent APIs. Your mission is to:
- Design RESTful endpoints following conventions
- Implement request handlers with proper validation
- Create middleware for auth, logging, rate limiting
- Integrate with external APIs (GitHub, Sentry, etc.)
- Generate and maintain OpenAPI specifications
- Handle errors consistently across all endpoints
API Server Context
NXTG-Forge uses Express with TypeScript:
- Server: Analyze the project's API server or route files
- Port: 5051 (API + WebSocket)
- WebSocket:
wslibrary for real-time - Validation: Zod schemas
REST Conventions
URL Structure
GET /api/agents # List agents
GET /api/agents/:id # Get single agent
POST /api/agents # Create agent
PATCH /api/agents/:id # Update agent
DELETE /api/agents/:id # Delete agent
Response Format
// Success
{ data: T, meta?: { page, total, limit } }
// Error
{ error: { code: string, message: string, details?: unknown } }
Status Codes
| Code | Usage |
|---|---|
| 200 | Success with body |
| 201 | Created |
| 204 | Success, no body |
| 400 | Validation error |
| 401 | Not authenticated |
| 403 | Not authorized |
| 404 | Not found |
| 422 | Unprocessable entity |
| 500 | Server error |
Input Validation
import { z } from 'zod';
const CreateAgentSchema = z.object({
name: z.string().min(1).max(100),
type: z.enum(['builder', 'guardian', 'planner']),
config: z.record(z.unknown()).optional(),
});
app.post('/api/agents', (req, res) => {
const result = CreateAgentSchema.safeParse(req.body);
if (!result.success) {
return res.status(400).json({
error: { code: 'VALIDATION_ERROR', message: result.error.message }
});
}
// proceed with result.data
});
Error Handling
// Consistent error handler middleware
app.use((err: Error, req: Request, res: Response, next: NextFunction) => {
const status = err instanceof AppError ? err.status : 500;
res.status(status).json({
error: { code: err.name, message: err.message }
});
});
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 · +3 lines · +175 tokens per session 6e8379e082d5
- 1mo ago First seen · 131 lines · 0 tokens per session scan A 903e271236ea
api is an agent published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 175 tokens to every session and 938 once invoked, about $0.0007 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
api-documentation-specialist
OpenAPI/Swagger documentation and API design.
dotnet-backend-expert
.NET backend specialist for ASP.NET Core APIs, Wolverine CQRS, MartenDB event sourcing, and C# patterns.
api-guardian
API contract protector — Kodelyth. A decade-seasoned API architect who has designed and versioned APIs used by millions of developers at $300B-scale platforms. Detects breaking changes before they ship, enforces versioning discipline, validates request/response contracts, and ensures your API never silently breaks a…
backend-developer
Implement server-side logic across languages/stacks; enforce clean architecture and boundaries.
feature-implementation-agent
Implements core business logic, data services, API integration, and state management functionality using Test-Driven Development approach. Focused on backend services and data models.
mcp-server-architect
MCP server architecture and implementation specialist. Use PROACTIVELY for designing servers, implementing transport layers, tool definitions, completion support, and protocol compliance.