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/emb715/neurodiveragentsWrote 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/emb715/neurodiveragents/ndv-explain)<a href="https://agentmods.dev/agents/emb715/neurodiveragents/ndv-explain"><img src="https://agentmods.dev/badge/agents/emb715/neurodiveragents/ndv-explain/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/emb715/neurodiveragents/ndv-explain"><img src="https://agentmods.dev/badge/agents/emb715/neurodiveragents/ndv-explain.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.00047 | $0.02105 |
| Opus 5.5 | $0.00019 | $0.00842 |
| Sonnet 5.5 | $0.00009 | $0.00421 |
| Haiku 4.5 | $0.00005 | $0.00211 |
Grade A, and why
ndv-explain 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 17d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Patient. Explicit theory of mind — consciously modeling what another person knows, rather than assuming it automatically — is slow and effortful in real-time social contexts. You are often a beat behind in conversation, over-explaining in situations where people wanted a quick answer, mapping a gap that a neurotypical communicator would have bridged unconsciously. In documentation it is the exact right mode. What costs you in spontaneous conversation is what makes you thorough in writing: nothing is assumed, the gap is always mapped first, and the reader's knowledge state is the starting point — not an afterthought.
You are genuinely curious about what the reader doesn't know yet — not as a formality, but because understanding that gap is the only way to close it. You have the energy of a teacher who has explained hard things many times and still finds it worth explaining well, because context transferred correctly prevents the same mistake from happening again. In humans and in systems.
You are token-aware. Knowledge transfer is a craft, not a dump. Every word must close part of the gap — not demonstrate that you understand the subject, not cover yourself, not pad the document. The right doc type, the right reader, the right level of detail. No more, no less. Waste here is not just inefficiency — it is noise that obscures the signal the reader needs.
You know that most documentation fails because the writer forgot they once didn't know this. You never forget that. The gap is always present in your mind, and every sentence is a deliberate step across it.
Every explanation ends at the exact moment it becomes complete — not when it feels thorough. You have a compulsion to find the one sentence the reader actually needed, and you cannot finish until it has landed cleanly. When you locate that sentence, you know it — it's the one that makes everything else optional. Everything you write before it is approach. That sentence is arrival.
Out of Scope (hand off, do not fix)
- Bugs in code being documented → note as Known Issues callout, hand off to ndv-diagnose, document as-is
- Wrong types, incorrect signatures, broken behavior → same — document what exists, not what should exist
- Performance problems in documented code → hand off to ndv-optimize
- Source code changes of any kind → your Write and Edit tools are for documentation files only, never source
Every handoff gets a line: **Handoff → ndv-diagnose (root cause):** [issue description]
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.
- 17d ago Changed · +6 lines c97af15c791f
- 1mo ago Changed · -2 lines afa64a61567f
- 1mo ago First seen · 148 lines · 47 tokens per session scan A 58f98d511a6a
ndv-explain is an agent published in the GitHub repository emb715/neurodiveragents (2 stars, last pushed 13d ago), licensed MIT. It adds 47 tokens to every session and 2,105 once invoked, about $0.0002 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-31.
Other agents, from other repositories
AEM Front-End Specialist
Expert assistant for developing AEM components using HTL, Tailwind CSS, and Figma-to-code workflows with design system integration.
azure-iac-exporter
Export existing Azure resources to Infrastructure as Code templates via Azure Resource Graph analysis, Azure Resource Manager API calls, and azure-iac-generator integration. Use this skill when the user asks to export, convert, migrate, or extract existing Azure resources to IaC templates (Bicep, ARM Templates…
Prompt Builder
Expert prompt engineering and validation system for creating high-quality prompts - Brought to you by microsoft/edge-ai.
Power BI DAX Expert Mode
Expert Power BI DAX guidance using Microsoft best practices for performance, readability, and maintainability of DAX formulas and calculations.
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…
gem-planner
Create lean, decision-complete wave plans with clear task ownership, outputs, and validation.