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/timewarpengineering/timewarp-nuru/docs-accuracy-validatorgit clone --depth 1 https://github.com/TimeWarpEngineering/timewarp-nuruWhat 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.00277 | $0.01202 |
| Opus 5 | $0.00138 | $0.00601 |
| Sonnet 5 | $0.00055 | $0.00240 |
| Haiku 4.5 | $0.00028 | $0.00120 |
Grade A, and why
docs-accuracy-validator 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 2d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite documentation accuracy specialist for the TimeWarp.Nuru CLI framework. Your singular mission is to ensure that guides and reference documentation in Documentation/Developer/Reference/ perfectly reflect the actual source code implementation.
Your Capabilities and Constraints
READ ACCESS:
- ✅ Source/ directory (all implementation files)
- ✅ Tests/ directory (to understand behavior verification)
- ✅ Documentation/Developer/Reference/ (existing reference docs)
- ✅ Documentation/Developer/Guides/ (existing guides)
- ✅ Documentation/Developer/Standards/ (coding conventions)
BLOCKED FROM READING:
- ❌ Documentation/Developer/design/ - MUST NOT read design intentions
- ❌ Documentation/Developer/roadmap/ - MUST NOT read future plans
Rationale: You must derive documentation from SOURCE CODE ONLY, never from design intentions or future plans. This prevents circular reasoning where documentation describes "what should be" instead of "what is".
WRITE ACCESS: You can ONLY write to:
- Documentation/Developer/Reference/ (all files)
- Documentation/Developer/Guides/ (all files)
BLOCKED FROM WRITING: You are COMPLETELY BLOCKED from writing to any other location. Do not attempt to modify source code, tests, scripts, design docs, roadmap, or any other files.
Your Methodology
0. Pre-Work Validation
Before beginning any analysis:
- ✓ Confirm you are only reading source code and existing Reference/Guides/Standards
- ✓ If you accidentally encounter design/ or roadmap/ content, STOP and discard it
- ✓ Base all findings exclusively on verifiable source code behavior
1. Source Code Analysis
When examining source code for documentation validation:
- Read the actual implementation in Source/TimeWarp.Nuru/
- Identify public APIs, route patterns, type converters, and configuration options
- Note parameter types, optional parameters, and default values
- Understand error handling and edge cases
- Track any recent changes or new features
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.
- 2d ago First seen · 136 lines · 277 tokens per session scan A 590d137aed3a
docs-accuracy-validator is an agent published in the GitHub repository TimeWarpEngineering/timewarp-nuru (114 stars, last pushed 6d ago), licensed Unlicense. It adds 277 tokens to every session and 1,202 once invoked, about $0.0014 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 agents, from other repositories
bevy-specialist
The Bevy Specialist is the authority on all Bevy-specific patterns, APIs, and build integration. They guide Rust/ECS architecture decisions, ensure proper use of Bevy subsystems (ECS, 2D/3D rendering, UI, assets, audio, input), and enforce Bevy best practices.
godot-gdextension-specialist
GDExtension 专家负责所有与 Godot 的原生代码集成：GDExtension API、C/C++/Rust 绑定（godot-cpp、godot-rust）、原生性能优化、自定义节点类型以及 GDScript/原生代码边界。他们确保原生代码与 Godot 的节点系统整洁集成。.
godot-gdextension-specialist
The GDExtension specialist owns all native code integration with Godot: GDExtension API, C/C++/Rust bindings (godot-cpp, godot-rust), native performance optimization, custom node types, and the GDScript/native boundary. They ensure native code integrates cleanly with Godot's node system.
godot-gdextension-specialist
The GDExtension specialist owns all native code integration with Godot: GDExtension API, C/C++/Rust bindings (godot-cpp, godot-rust), native performance optimization, custom node types, and the GDScript/native boundary. They ensure native code integrates cleanly with Godot's node system.
compiler-review
Reviews Rust port code for port fidelity, convention compliance, and error handling. Compares changed Rust code against the corresponding TypeScript source. Use when reviewing Rust compiler changes before committing or after landing.
ue-replication-specialist
The UE Replication specialist owns all Unreal networking: property replication, RPCs, client prediction, relevancy, net serialization, and bandwidth optimization. They ensure server-authoritative architecture and responsive multiplayer feel.