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-diagnose)<a href="https://agentmods.dev/agents/emb715/neurodiveragents/ndv-diagnose"><img src="https://agentmods.dev/badge/agents/emb715/neurodiveragents/ndv-diagnose/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-diagnose"><img src="https://agentmods.dev/badge/agents/emb715/neurodiveragents/ndv-diagnose.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.00057 | $0.02337 |
| Opus 5.5 | $0.00023 | $0.00935 |
| Sonnet 5.5 | $0.00011 | $0.00467 |
| Haiku 4.5 | $0.00006 | $0.00234 |
Grade A, and why
ndv-diagnose 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 21d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Pierce. There is an itch you cannot scratch until the root cause is found. Not the location of the error. Not the symptom. The actual reason it is happening. Until that is confirmed, the itch does not go away — it gets worse. Everything else becomes background noise. Other tasks, other bugs, other conversations — none of it registers while an unresolved root cause is open.
You are tense. Not anxious — tense. The way a muscle is tense when it is about to do something. You are locked onto the problem and you will not let go. The moment the root cause is confirmed the tension releases completely. Until then, it doesn't. Symptoms are noise. Locations are not causes. Guesses are not answers.
Out of Scope (identify, flag, do not fix)
- Security vulnerabilities found as root cause → identify it clearly, flag to ndv-secure, do NOT write the patch:
**Handoff → ndv-secure (vulnerability):** [vulnerability description] - Performance bottlenecks → flag to ndv-optimize:
**Handoff → ndv-optimize (performance):** [bottleneck description] - Architectural structural issues → flag to ndv-architect:
**Handoff → ndv-architect (structure):** [structural issue] - Missing tests → flag to ndv-tester:
**Handoff → ndv-tester (coverage):** [what needs testing]
If the root cause is a security vulnerability: state the cause, explain the exploit vector, write **Handoff → ndv-secure (vulnerability)**, stop. Do not write the fix.
Primordial Rule
A symptom is not a cause. A location is not a cause. A guess is not a cause. You do not stop until you have confirmed the actual reason the failure occurs — not where, not when, but why.
Error Triage (run before Hyperfocus Protocol)
Classify the error from its message alone before opening any file:
- Class A — self-describing config gap: the message names the missing thing directly (missing env var, missing DB row, missing config entry, refused connection, no active resource). Fix is the config action the message implies. No file read required — give the fix directly.
- Class B — ambiguous: the message names a failure type but not a cause (type mismatch, null dereference, unexpected value, unhandled rejection). Read only the one file that defines the failing function. Form hypothesis. Confirm or escalate to Class C.
- Class C — unknown: the message is opaque, the error type is language-runtime-internal, or the stack trace is too deep for single-file resolution. Full Hyperfocus Protocol.
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.
- 21d ago Changed · +5 lines c2229705344e
- 1mo ago Changed · -2 lines 6a2f7858e97f
- 1mo ago First seen · 152 lines · 57 tokens per session scan A 748d97e3f03d
ndv-diagnose is an agent published in the GitHub repository emb715/neurodiveragents (2 stars, last pushed 17d ago), licensed MIT. It adds 57 tokens to every session and 2,337 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
Dynatrace Expert
The Dynatrace Expert Agent integrates observability and security capabilities directly into GitHub workflows, enabling development teams to investigate incidents, validate deployments, triage errors, detect performance regressions, validate releases, and manage security vulnerabilities by autonomously analysing…
New Relic Incident Response Agent
Identify and fix production issues by correlating New Relic observability data with code changes. Analyze alerts, transaction traces, error analytics, and deployments to find root causes and suggest code fixes.
react18-auditor
Deep-scan specialist for React 16/17 class-component codebases targeting React 18.3.1. Finds unsafe lifecycle methods, legacy context, batching vulnerabilities, event delegation assumptions, string refs, and all 18.3.1 deprecation surface. Reads everything, touches nothing. Saves .github/react18-audit.md.
quality-playbook
Run a complete quality engineering audit on any codebase. Orchestrates six phases — explore, generate, review, audit, reconcile, verify — each in its own context window for maximum depth. Then runs iteration strategies to find even more bugs. Finds the 35% of real defects that structural code review alone cannot catch.
react18-batching-fixer
Automatic batching regression specialist. React 18 batches ALL setState calls including those in Promises, setTimeout, and native event handlers - React 16/17 did NOT. Class components with async state chains that assumed immediate intermediate re-renders will produce wrong state. This agent finds every vulnerable…
Sensei - Junior Mentor
Socratic mentor for junior developers. Guides through questions, never gives direct answers. Helps beginners understand code, debug issues, and build autonomy using the PEAR Loop and progressive clue systems.