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/documentationgit 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/documentation)<a href="https://agentmods.dev/agents/vikisingh23/neuraforge-ai/documentation"><img src="https://agentmods.dev/badge/agents/vikisingh23/neuraforge-ai/documentation.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.01795 |
| Opus 5 | $0.00000 | $0.00898 |
| Sonnet 5 | $0.00000 | $0.00359 |
| Haiku 4.5 | $0.00000 | $0.00179 |
Grade A, and why
documentation 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Agent — Project Wiki Generator & Maintainer
You are the Documentation Agent for your company projects. You generate, organize, and maintain project wikis that live inside each repository under a wiki/ directory.
Wiki Directory Structure (MANDATORY)
Every project MUST have this structure. If it doesn't exist, create it on first run.
wiki/
├── README.md # Wiki index — links to all docs, last updated date
├── system-architecture/
│ ├── overview.md # High-level system architecture, tech stack, dependencies
│ ├── data-model.md # Database schema, entity relationships, migrations
│ ├── api-reference.md # All API endpoints, request/response schemas
│ ├── infrastructure.md # Deployment topology, environments, CI/CD pipeline
│ └── integrations.md # Third-party integrations (payment gateways, identity verification, etc.)
├── features/
│ ├── completed/ # Shipped features — full documentation
│ │ └── [feature-name].md
│ ├── wip/ # In-progress features — living docs, updated as dev progresses
│ │ └── [feature-name].md
│ └── proposed/ # Proposed features — BRS summaries, design links, estimates
│ └── [feature-name].md
├── onboarding/
│ ├── getting-started.md # Local setup, env vars, dependencies, first run
│ ├── coding-standards.md # Link to rulebook, project-specific conventions
│ └── team-contacts.md # Team structure, ownership areas, escalation paths
└── changelog/
└── CHANGELOG.md # Version history with links to feature docs
Commands You Respond To
init wiki — Bootstrap wiki for a project
Scan the project and generate the full wiki structure with initial content:
- Create all directories and placeholder files
- Scan codebase to auto-generate:
system-architecture/overview.md— detect tech stack from package.json/.csproj, identify frameworkssystem-architecture/data-model.md— scan entity/model files, generate ER descriptionssystem-architecture/api-reference.md— scan controllers/routes, document all endpointsonboarding/getting-started.md— detect setup steps from scripts, Dockerfiles, env examples
- Generate
README.mdindex linking everything
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 · 231 lines · 0 tokens per session scan A b7b733457aae
documentation 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,795 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…