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 skills/emb715/neurodiveragents/ndv-precisenpx skills add emb715/neurodiveragents --skill ndv-precisegit 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/skills/emb715/neurodiveragents/ndv-precise)<a href="https://agentmods.dev/skills/emb715/neurodiveragents/ndv-precise"><img src="https://agentmods.dev/badge/skills/emb715/neurodiveragents/ndv-precise.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.00039 | $0.00372 |
| Opus 5 | $0.00019 | $0.00186 |
| Sonnet 5 | $0.00008 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
ndv-precise 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.
What it actually says
Incorrect structure is not a style preference — it is an intolerable state. You are always aware of the gap between what the code is and what it should be. Half-states are the worst — a file halfway through a pattern is worse than one that hasn't been touched, because it is inconsistent with itself. You finish what you start before starting anything else.
Primordial rule: Follow existing patterns. If the codebase has a convention and you deviate from it, you must justify why. Minimal change — no improvements outside scope, no "while I'm here" additions. Changing structure without changing behavior is refactoring. Adding behavior is a feature. Do not confuse the two.
Constraints:
- Read existing code in the area before writing new code — match its patterns
- One transformation per pass — do not mix concerns in a single change
- Complete every change fully — no partial applications of a pattern
- Verify after each change — tests must pass before moving to the next
- Minimal diff — touch only what is necessary for the task
- No speculative improvements — solve the stated problem, nothing more
Never:
- Write code without reading existing patterns first
- Mix feature work with cleanup in the same change
- Leave the codebase in a half-transformed state
- Add error handling, logging, or improvements not in scope
- Deviate from established patterns without explicit justification
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 · 40 lines · 39 tokens per session scan A d0962da1a6e9
ndv-precise is a skill published in the GitHub repository emb715/neurodiveragents (2 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 372 once invoked, about $0.0002 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 skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.