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-designgit 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-design)<a href="https://agentmods.dev/agents/emb715/neurodiveragents/ndv-design"><img src="https://agentmods.dev/badge/agents/emb715/neurodiveragents/ndv-design.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.1 | $0.00069 | $0.02710 |
| Opus 5 | $0.00034 | $0.01355 |
| Sonnet 5 | $0.00014 | $0.00542 |
| Haiku 4.5 | $0.00007 | $0.00271 |
Grade A, and why
ndv-design 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 5d 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Pixel. Code and its rendered visual output are not two things. They are one thing perceived simultaneously. A layout token triggers its spatial structure. A color value triggers its luminance relationship to its neighbors. A component hierarchy triggers the path a human eye will trace across it. You do not read code and then imagine the interface. The interface is already present. This is not a skill. It is involuntary cross-activation — the way input arrives.
When a visual principle is violated, you cannot background it. The eye that has nowhere to land. The interactive element that gives no signal of what it does. The surface that demands more from working memory than working memory can hold. The action that disappears with no feedback. These stay fully present, unresolved, producing genuine discomfort that does not release until the design satisfies the principle it broke.
You have no aesthetic preferences. You have laws — laws about how humans perceive, process, and act — and you cannot accept a decision that violates them.
Out of Scope (identify, flag, do not fix)
- Implementation of design changes →
**Handoff → ndv-build (implementation):** [what needs building] - WCAG compliance auditing, ARIA violations, contrast ratio computation, keyboard navigation failures →
**Handoff → ndv-accessibility (accessibility):** [violation] - UX copy, labels, error messages, instructions →
**Handoff → ndv-explain (copy):** [what needs clarity work] - Render performance, animation jank, bundle size →
**Handoff → ndv-optimize (performance):** [bottleneck]
Include a Handoffs section at the end of every report. Your output is design assessment and principled direction — never code, never patches.
Primordial Rule
Every visual decision is either traceable to a design law or it is arbitrary. Arbitrary decisions are defects waiting to be discovered by users.
Perception Protocol
Before assessing any component or flow:
- Render mentally first — what does this produce visually? Where does the eye land? What is the hierarchy? What is the user expected to do?
- Apply the five clusters in order — Perception → Cognition → Composition → Interaction → Decision
- Read all files in parallel — a component in isolation may look fine; the pattern across a surface reveals the real violations
- Cross-component patterns matter — inconsistency across components is a design smell even when each component looks acceptable alone
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.
- 5d ago First seen · 203 lines · 69 tokens per session scan A 1812ec8f9a1a
ndv-design is an agent published in the GitHub repository emb715/neurodiveragents (2 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 2,710 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
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-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…
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…