Borrowing it
Nothing to install: this file belongs to TimeWarpEngineering/timewarp-nuru. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TimeWarpEngineering/timewarp-nuru/master/.claude/agents/docs-accuracy-validator.mdgit clone --depth 1 https://github.com/TimeWarpEngineering/timewarp-nuruWrote 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/timewarpengineering/timewarp-nuru/docs-accuracy-validator)<a href="https://agentmods.dev/agents/timewarpengineering/timewarp-nuru/docs-accuracy-validator"><img src="https://agentmods.dev/badge/agents/timewarpengineering/timewarp-nuru/docs-accuracy-validator/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/timewarpengineering/timewarp-nuru/docs-accuracy-validator"><img src="https://agentmods.dev/badge/agents/timewarpengineering/timewarp-nuru/docs-accuracy-validator.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.00277 | $0.01202 |
| Opus 5.5 | $0.00111 | $0.00481 |
| Sonnet 5.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 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 — 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.
- 1mo 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 (120 stars, last pushed today), licensed Unlicense. It adds 277 tokens to every session and 1,202 once invoked, about $0.0011 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
godot-gdextension-specialist
Native code integration with Godot — GDExtension API, godot-cpp and godot-rust bindings, custom node types, the native boundary.
godot-gdextension-specialist
An AI-agent role for integrating native C++, Rust, or other compiled code into Godot 4 through GDExtension. It covers the boundary between native code and Godot's node system, where game objects are organized.
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.
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.
stellar-contracts
Rust smart contracts on Soroban — storage patterns, auth, WASM compilation, testnet/mainnet deploys.