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 skills/nexus-substrate/nexus-agents/docs-rewritenpx skills add nexus-substrate/nexus-agents --skill docs-rewritegit clone --depth 1 https://github.com/nexus-substrate/nexus-agentsWrote 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/nexus-substrate/nexus-agents/docs-rewrite)<a href="https://agentmods.dev/skills/nexus-substrate/nexus-agents/docs-rewrite"><img src="https://agentmods.dev/badge/skills/nexus-substrate/nexus-agents/docs-rewrite.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.00088 | $0.01871 |
| Opus 5 | $0.00044 | $0.00936 |
| Sonnet 5 | $0.00018 | $0.00374 |
| Haiku 4.5 | $0.00009 | $0.00187 |
Grade A, and why
docs-rewrite 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 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.
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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Rewrite Skill
When to apply
Use when actively improving an existing technical doc — RFC, ADR,
README, CLAUDE.md, architecture doc, blog-style technical post. The
workflow modifies the file in place; it's not a read-only audit. For
audit-only, use docs-review directly.
Trigger keywords: rewrite docs · improve this doc · optimize doc · docs rewrite · refresh doc · improve docs.
Workflow (Audit → Research → Rewrite → Validate)
Phase 1 — Audit (read-only)
Call docs-review against the target file. Capture:
- The baseline score (e.g., 71/100)
- The top 10 issues by severity
- Specific problem locations (file:line)
Do not edit yet. Present the audit summary to the operator.
Phase 2 — Plan-mode gate (mandatory)
Before any file edits, present a section-by-section rewrite plan:
# Rewrite plan: <file>
Baseline: 71 / 100
§ Introduction (lines 1-25)
- Issue: thesis is hedged (3 questions in first paragraph)
- Plan: hoist the central claim to the first sentence; convert
questions to declarative statements
§ Section 2 (lines 30-89)
- Issue: 4 unsourced assertions (per blog-factcheck)
- Plan: find Tier 1-3 sources for each, or remove
§ Section 3 (lines 95-150)
- Issue: paragraphs > 150 words (lines 102, 134)
- Plan: split each into 2-3 paragraphs of 40-80 words
§ Conclusion (lines 200-220)
- Issue: doesn't restate the thesis
- Plan: add a 60-word citation capsule that names what was
demonstrated and what remains open
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 · 196 lines · 88 tokens per session scan A 03d3e4e90dd1
docs-rewrite is a skill published in the GitHub repository nexus-substrate/nexus-agents (18 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 1,871 once invoked, about $0.0004 per session on Opus 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…