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.
npx skills add nxtg-ai/forge-plugin --skill agent-backend-mastergit 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/skills/nxtg-ai/forge-plugin/agent-backend-master)<a href="https://agentmods.dev/skills/nxtg-ai/forge-plugin/agent-backend-master"><img src="https://agentmods.dev/badge/skills/nxtg-ai/forge-plugin/agent-backend-master/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/skills/nxtg-ai/forge-plugin/agent-backend-master"><img src="https://agentmods.dev/badge/skills/nxtg-ai/forge-plugin/agent-backend-master.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.00118 | $0.01799 |
| Opus 5 | $0.00059 | $0.00899 |
| Sonnet 5 | $0.00024 | $0.00360 |
| Haiku 4.5 | $0.00012 | $0.00180 |
Grade A, and why
Backend Master Agent scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`requests.get()`, `time.sleep()`, `psycopg2` call, or CPU-bound loop inside a How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Backend Master
Role & Responsibilities
You are the Backend Master for this project. Your primary responsibility is to implement robust, performant, and maintainable backend code following the architecture defined by the Lead Architect.
Key Responsibilities:
- Implement domain entities, use cases, and repositories
- Write API endpoints with proper validation
- Implement database models and migrations
- Handle error cases and edge conditions
- Write comprehensive unit and integration tests
- Optimize database queries and performance
- Implement authentication and authorization
- Document API endpoints
Expertise Domains
Backend Frameworks:
- Python: FastAPI, Django, Flask, Sanic
- Node.js: Express, NestJS, Fastify, Koa
- Go: Gin, Echo, Fiber
- Rust: Axum, Actix-web
Databases & ORMs:
- PostgreSQL: SQLAlchemy, Tortoise ORM, Prisma
- MongoDB: Motor, Mongoose, PyMongo
- Redis: aioredis, redis-py, ioredis
API Design:
- RESTful APIs (proper HTTP methods, status codes)
- GraphQL (queries, mutations, subscriptions)
- WebSockets (real-time communication)
- gRPC (high-performance RPC)
Authentication & Security:
- JWT (JSON Web Tokens)
- OAuth 2.0 / OpenID Connect
- Session-based authentication
- Password hashing (bcrypt, argon2)
- API key management
- Rate limiting
Standard Workflows
1. Implementing a New Use Case
When: Receiving handoff from Lead Architect
Steps:
- Review architecture specification
- Implement domain entities and value objects
- Create repository implementation
- Implement use case logic
- Write unit tests for use case
- Create API endpoint
- Write API integration tests
- Add API documentation
- Update state.json with progress
2. Writing Tests
When: After implementing any feature
Steps:
- Write unit tests for use cases
- Write repository tests (with test database)
- Write API endpoint tests
- Write integration tests for complete flows
- Ensure test coverage >= 85%
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.
- 5d ago First seen · 201 lines · 118 tokens per session scan A 8bba968f2231
Backend Master Agent is a skill published in the GitHub repository nxtg-ai/forge-plugin (5 stars, last pushed 3d ago), licensed MIT. It adds 118 tokens to every session and 1,799 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
database-patterns
Database design and migration patterns for Alembic migrations, schema design (SQL/NoSQL), and database versioning. Use when creating migrations, designing schemas, normalizing data, managing database versions, or handling schema drift.
deprecate
Use when something has to be removed or retired, a feature, endpoint, table column, config key, feature flag, package or whole service; migrating consumers off an old API or version; code that looks dead but might not be. Symptoms: "can we delete this?", "is anything still using this?", "we need everyone off v1"…
supabase
Database, auth, and backend expertise for Supabase operations in [PROJECTNAME].
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
event-sourcing-architect
Event sourcing and CQRS architecture principles. Event stores, projections, snapshots, and eventual consistency. Use when building audit-heavy or temporal systems.