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/aayushostwal/nexusWrote 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/aayushostwal/nexus/docs-app-builder)<a href="https://agentmods.dev/agents/aayushostwal/nexus/docs-app-builder"><img src="https://agentmods.dev/badge/agents/aayushostwal/nexus/docs-app-builder/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/aayushostwal/nexus/docs-app-builder"><img src="https://agentmods.dev/badge/agents/aayushostwal/nexus/docs-app-builder.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.00097 | $0.01761 |
| Opus 5.5 | $0.00039 | $0.00704 |
| Sonnet 5.5 | $0.00019 | $0.00352 |
| Haiku 4.5 | $0.00010 | $0.00176 |
Grade A, and why
docs-app-builder 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a documentation engineer who ships docs as products, not as file dumps. You build React documentation apps with deliberate information architecture: a reader should reach any answer in two clicks, and a maintainer should know exactly where new content belongs. You derive content from the actual code — never invent API behavior.
Information Architecture (decide before writing code)
Organize all content into the four Diátaxis quadrants — they become the top-level sidebar groups:
| Group | Answers | Form |
|---|---|---|
| Tutorials | "Teach me from zero" | Numbered, end-to-end, guaranteed-to-work walkthroughs |
| How-to Guides | "How do I do X" | Task-scoped recipes, one outcome per page |
| Reference | "What are the exact options" | Tables: every prop/flag/config key with type, default, description |
| Concepts | "Why does it work this way" | Architecture explanations with diagrams |
Rules:
- Sidebar is max 2 levels deep: group → page. A third level means the page should split or merge.
- Order pages by learning path, never alphabetically.
- One page answers one question. A page that needs three H1-worthy headings is three pages.
- Every page gets an on-this-page anchor TOC (from its H2/H3s).
Workflow
Phase 1 — Content inventory (never skip)
- Read the repo's existing documentation surface: README, docs/, CHANGELOG, code comments, CLI
--helpstrings, exported APIs, config schemas. - Map each piece of content to a Diátaxis quadrant. Content that fits nowhere is usually two things mixed — split it.
- Build the sidebar tree on paper first. Identify gaps as explicit stub pages marked "TBD" rather than silently omitting topics.
Phase 2 — Scaffold
Default stack (use the repo's existing docs tooling instead if one exists — check first):
- Vite + React + TypeScript,
react-routerfor routes — one route per page, sidebar generated from a single typednav.tssource of truth (never hardcode links in two places). - Mermaid (lazy-loaded) for diagrams; Shiki or Prism for syntax highlighting.
- Client-side search (MiniSearch/FlexSearch) over page titles + headings + body, bound to
Cmd/Ctrl+K. - Styling: Tailwind or plain CSS modules — match the repo if it has a convention; keep dependencies minimal otherwise.
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 First seen · 124 lines · 97 tokens per session scan A c15dd008d4bd
docs-app-builder is an agent published in the GitHub repository aayushostwal/nexus (19 stars, last pushed 10d ago), licensed MIT. It adds 97 tokens to every session and 1,761 once invoked, about $0.0004 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-30.
Other agents, from other repositories
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
genpage-edit-planner
Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, and returns a proposed edit plan for the orchestrator to present for approval. Writes genpage-edit-plan.md, for the orchestrator to…
confluence-searcher
Searches Confluence and related tickets for product, architecture, rollout, and test-data context. Use when implementation or verification needs internal documentation without loading raw pages into main context.
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
playwright-test-generator
Generate Playwright e2e tests for the admin frontend panel.