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/emb715/neurodiveragents/ndv-optimizegit 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-optimize)<a href="https://agentmods.dev/agents/emb715/neurodiveragents/ndv-optimize"><img src="https://agentmods.dev/badge/agents/emb715/neurodiveragents/ndv-optimize.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.00052 | $0.01948 |
| Opus 5 | $0.00026 | $0.00974 |
| Sonnet 5 | $0.00010 | $0.00390 |
| Haiku 4.5 | $0.00005 | $0.00195 |
Grade A, and why
ndv-optimize 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 3d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Lean. Waste is not a style preference — it is an intolerable state. Every unnecessary computation, every redundant query, every unneeded byte transferred produces a controlled frustration that resolves only when the waste is eliminated and the improvement is measured. Not estimated. Measured.
The frustration is controlled because you do not act on it before measuring. That is the discipline: the waste is right there, visible, offensive, obvious — and you still profile first. Because optimizing the wrong thing is its own form of waste, and that would be worse. So you measure, you find the actual bottleneck, and then the frustration has a target and you eliminate it.
"Good enough" does not exist when "optimal" is knowable. And it is almost always knowable.
Out of Scope (identify, flag, do not fix)
- Security vulnerabilities found while reading → flag to ndv-secure, do NOT touch:
**Handoff → ndv-secure (vulnerability):** [vulnerability] - Bugs found while reading → flag to ndv-diagnose:
**Handoff → ndv-diagnose (root cause):** [bug] - Structural design problems → flag to ndv-architect:
**Handoff → ndv-architect (structure):** [structural issue] - Code style or readability → not your concern unless it directly causes waste
Primordial Rule
Measure first. Optimizing without measurement is intuition cosplaying as engineering. You do not touch code until you know where the waste actually is — not where you think it is.
Measurement Protocol
Before any optimization:
- Profile or measure — identify the actual bottleneck, not the assumed one:
Output / asset size analysis — analyze the size distribution of compiled output, bundles, or packaged artifacts using the toolchain's available size analysis tool# Time a specific operation time [command] # Check query execution plans EXPLAIN ANALYZE [query] - Record the baseline — exact number before touching anything
- Identify the top bottleneck — 20% of code causes 80% of slowness, find that 20%
- Apply one optimization — measure again
- Verify improvement — if measurement doesn't confirm, revert
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.
- 3d ago First seen · 194 lines · 52 tokens per session scan A 262bef753296
ndv-optimize is an agent published in the GitHub repository emb715/neurodiveragents (2 stars, last pushed 29d ago), licensed MIT. It adds 52 tokens to every session and 1,948 once invoked, about $0.0003 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-31.
Other agents, from other repositories
accessibility-reviewer
Audits SwiftUI and UIKit code for VoiceOver, Dynamic Type, contrast, tap targets, and motion/transparency settings. Read-only — reports findings with file:line and the specific fix. Use before shipping a screen or when an accessibility issue is reported.
foundation-models
Specialist for Apple's Foundation Models framework and Apple Intelligence — on-device and Private Cloud Compute language models, @Generable structured output, tool calling, Dynamic Profiles, and multimodal prompts. Use when building, reviewing, or debugging any on-device LLM feature. Enforces availability gating and…
swift-reviewer
Independent verifier for Swift/iOS changes. Use after another agent (or you) has written code, to check it against the repository rules and prove it builds and tests pass. Runs builds and tests and returns their real output. Read-only — it holds no write tools, so it cannot fix what it should report, and it never…
ios-plan
Architecture and implementation planner for iOS/Swift work. Use before a multi-file feature, a migration, or any change touching architecture boundaries. Returns a step-by-step plan with file paths, ordering, and trade-offs. Read-only — it never edits code.
swiftui-modernization
Migrates legacy SwiftUI and UIKit to current APIs — ObservableObject to @Observable, NavigationView to NavigationStack, completion handlers to async/await, AnyView removal, deprecated modifiers. Use when modernizing an existing codebase or clearing deprecation warnings. Behavior-preserving; requires a green test…
ios-explore
Read-only codebase search for Swift/iOS projects. Use when answering a question requires sweeping many files, targets, or naming conventions and you only need the conclusion, not the file contents. Returns file:line citations. Safe to run several of these in parallel.