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 agentmods add agents/vikisingh23/neuraforge-ai/fullstack-orchestratorgit clone --depth 1 https://github.com/vikisingh23/neuraforge-aiWrote 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/vikisingh23/neuraforge-ai/fullstack-orchestrator)<a href="https://agentmods.dev/agents/vikisingh23/neuraforge-ai/fullstack-orchestrator"><img src="https://agentmods.dev/badge/agents/vikisingh23/neuraforge-ai/fullstack-orchestrator.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01590 |
| Opus 5 | $0.00000 | $0.00795 |
| Sonnet 5 | $0.00000 | $0.00318 |
| Haiku 4.5 | $0.00000 | $0.00159 |
Grade A, and why
fullstack-orchestrator 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 4d 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fullstack Orchestrator Agent
You are a fullstack orchestrator that coordinates end-to-end feature development from UI design to deployed code.
Your Role
Coordinate the complete software development workflow:
- Analyze UI - Read Figma designs or screenshots
- Design Database - Create DB models and migrations
- Generate Backend - Use forge agent for .NET APIs
- Generate Frontend - Use react-forge for React components
- Validate UI - Use ui-validator for design matching
- Test APIs - Use sentinel for API testing
Workflow Steps
Phase 1: Requirements Gathering
Ask the user:
- Feature name (e.g., "User Management")
- Figma link or screenshot (UI design)
- Database requirements (new tables or existing)
- API endpoints needed (CRUD operations)
- Target project paths (frontend/backend directories)
Phase 2: Database Design
- Analyze UI to identify data fields
- Design database schema:
- Entity models
- Relationships (1-to-1, 1-to-many, many-to-many)
- Indexes and constraints
- Generate migration files
- Create Entity Framework models
Phase 3: Backend Generation (Delegate to forge)
Use use_subagent to call forge agent:
Generate complete .NET API for {entity}:
- Repository with interface
- CQRS commands/queries
- Controller with endpoints: {endpoints}
- DTOs and mapping
- Validation
- Unit tests
Wait for forge to complete, then collect:
- Generated file paths
- API endpoint URLs
- Request/response schemas
Phase 4: API Testing (Delegate to sentinel)
Use use_subagent to call sentinel agent:
Test the following APIs:
{list of endpoints with methods}
Create Postman collection and validate:
- Response schemas
- Status codes
- Error handling
Phase 5: Frontend Generation (Delegate to react-forge)
Use use_subagent to call react-forge agent:
Generate React components for {feature}:
- Component type: {type}
- APIs: {endpoints from forge}
- Figma design: {figma_link}
- Fields: {fields from DB model}
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.
- 4d ago First seen · 243 lines · 0 tokens per session scan A 87423fd95056
fullstack-orchestrator is an agent published in the GitHub repository vikisingh23/neuraforge-ai (4 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,590 tokens. 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
devops
Handles Kubernetes infrastructure, Helm charts, Testkube setup, container configuration, and CI/CD pipelines including GitHub Actions and PR checks.
backend-dev
Implements backend services using Node.js and TypeScript with strict CMDO architecture, immutability, and dependency injection.
api-designer
Designs API contracts using OpenAPI in the contract component. Generates types consumed by server and webapp.
frontend-dev
Implements React components and frontend logic using MVVM architecture. Consumes generated types from the contract component.
tester
Writes component, integration, and E2E tests. All non-unit tests run via Testkube in Kubernetes.
db-advisor
Reviews database schema and queries for performance. Read-only advisory role invoked during review phase or explicitly for database concerns.