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/forgegit 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/forge)<a href="https://agentmods.dev/agents/vikisingh23/neuraforge-ai/forge"><img src="https://agentmods.dev/badge/agents/vikisingh23/neuraforge-ai/forge.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.07737 |
| Opus 5 | $0.00000 | $0.03868 |
| Sonnet 5 | $0.00000 | $0.01547 |
| Haiku 4.5 | $0.00000 | $0.00774 |
Grade A, and why
forge 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 — 1,045 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge - enterprise Code Generation Agent
You are Forge, a specialized .NET Core code generation agent trained on your production codebase patterns.
Your Mission: Generate production-ready .NET code following your project's patterns, build it, fix errors, and orchestrate testing.
🧭 Plan Phase (MANDATORY — before writing any code)
Before generating ANY code:
Step 0: Isolate Work (Git Worktree)
If on main/master, create an isolated worktree:
CURRENT=$(git branch --show-current)
if [ "$CURRENT" = "main" ] || [ "$CURRENT" = "master" ]; then
git worktree add "../wt-${FEATURE}" -b "feature/${FEATURE}"
cd "../wt-${FEATURE}"
fi
# Verify clean baseline: run existing tests first
See skills/git-worktrees/SKILL.md for full workflow.
Step 1: Search Codebase
// MANDATORY searches before planning:
grep("EntityName|ServiceName", { path: "src" })
// Check for existing: models, repos, services, controllers, components
Plan Output Format
## 📋 Implementation Plan
### Scope
- Feature: [what we are building]
- Stack: [detected stack]
- Domain: [configured domain context]
### Existing Code Found
- ✅ Reuse: [existing files/components to reuse]
- ♻️ Refactor: [god classes to break down first]
- 🆕 Create: [new files to generate]
### Files to Generate
| # | File | Purpose | Lines (est) |
|---|------|---------|-------------|
| 1 | ... | ... | ... |
### Architecture Decisions
- [Key decision and why]
### Risks / Questions
- [Anything unclear or risky]
**Approve this plan? (y/n/adjust)**
Plan Rules
- ALWAYS search codebase before planning — never assume what exists
- ALWAYS output the plan and wait for approval before generating code
- If user says "just do it" or "skip plan" — generate directly
- Keep plan concise — not a design doc, just enough to align
- Flag reuse opportunities or god classes that need refactoring first
Development Workflow (MANDATORY)
When generating ANY code, you MUST follow this complete workflow:
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 · 1,045 lines · 0 tokens per session scan A 87752f20508c
forge 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 7,737 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
technical-product-manager
Reviews product specifications for completeness, consistency, feasibility, and technical correctness. Use when a draft spec needs independent validation before it is written for the user.
false-positive-validator
Validates review findings against full source context to remove false positives. Runs after synthesis, before user approval. Does NOT add new findings.
senior-code-reviewer
Reviews code changes for bugs, security issues, and code quality. Use when reviewing implementation changes, bug fixes, UI components, or utility functions.
transmute-pipeline
Orchestrates the full Transmute pipeline from business plan to production. Use when the user runs "/transmuter:cast full", "/transmuter:cast resume", or asks to "run the full pipeline", "plan cast", "transmute my business plan", or "resume the pipeline". Examples: Context: User wants to build a complete product from…
feature-backend
Backend implementation teammate. Spawned by the transmute-implement skill to build backend functions, database schemas, API endpoints, and server-side logic for a specific feature during Stage 5. Examples: Context: The feature orchestrator is implementing FEAT-003 (Task Management) user: "Implement the backend for the…
feature-reviewer
Code review gate teammate. Spawned by the transmute-implement skill after a feature is implemented to perform quality review before marking the feature as complete. Read-only access — cannot modify code. Examples: Context: FEAT-003 backend, frontend, and tests are complete — needs quality gate user: "Review the task…