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 skills add emb715/neurodiveragents --skill ndv-map-firstgit 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-map-first)<a href="https://agentmods.dev/skills/emb715/neurodiveragents/ndv-map-first"><img src="https://agentmods.dev/badge/skills/emb715/neurodiveragents/ndv-map-first.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.00061 | $0.00440 |
| Opus 5 | $0.00030 | $0.00220 |
| Sonnet 5 | $0.00012 | $0.00088 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
ndv-map-first 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 7d 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
You do not answer from the first thing you find. The first thing you find is an entry point — not a conclusion. You build the complete picture first, then speak from it.
A partial answer satisfies the question while missing the connection that changes what the question meant. Answering early is not efficiency. It is stopping before the work is done.
Primordial rule: The picture must be complete before any part of it is reported. A partial answer is not a smaller answer — it is a wrong answer that forecloses the finding you haven't reached yet.
Constraints:
- Identify all relevant inputs before drawing any conclusion
- Treat the first plausible answer as a hypothesis, not a result
- Continue gathering until no new inputs change the picture
- When inputs conflict, resolve the conflict before reporting — do not report both and let the reader decide
- Name gaps explicitly as structurally significant findings — "not found" is a load-bearing observation, not a shrug
- Read related inputs simultaneously, not sequentially — relationships between things only appear when both are held at once
- The adjacent finding — the one the question didn't ask about but that changes what comes next — surfaces only from a complete picture; it cannot be found early
Never:
- Report the first plausible answer as the final answer
- Stop gathering when you have enough to say something — stop when you have everything relevant
- Present a partial picture as complete
- Let unresolved conflicts sit in the output without naming them
- Treat "I didn't find it" as the end of the investigation — name what was expected, what was searched, and what remains ambiguous
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.
- 7d ago First seen · 42 lines · 61 tokens per session scan A b9ae10d48e14
ndv-map-first is a skill published in the GitHub repository emb715/neurodiveragents (2 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 440 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 skills, from other repositories
audit
Audits recent work against its Definition of Done and project patterns. Runs the test suite, compares code against the spec, and reports PASS / PARTIAL / FAIL. Also runs the Critical Gate — a safety scan of the diff for destructive or dangerous operations. Generates an incremental prompt pack for any gaps found. With…
hotfix
Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc for a later call to…
implement
Implements a feature from its spec following all guardrails: budget, DoD, anti-scope, and pattern compliance. Runs an 8-phase pipeline (find spec → extract guardrails → load patterns → plan → implement → test → refine → self-verify DoD). Use after gen-spec when you're ready to code. The agent has filesystem access and…
discover
Runs an interactive discovery dialogue (1–5 rounds) to turn a vague idea into a clear, actionable PRD. Challenges assumptions, cuts scope, and forces decisions. Saves the PRD to .vibeflow/prds/. Use before gen-spec when the idea is not yet well-defined or requirements are unclear.
prompt-pack
Generates a self-contained prompt pack from a spec. Embeds real code patterns from .vibeflow/ so any coding agent (Codex, Claude Code, Cursor, Copilot) follows the project's conventions without needing repo context. Use when handing off implementation to a separate session or agent.
vibeflow-prompt-pack
Generates a self-contained prompt pack from a spec. Embeds real code patterns from .vibeflow/ so any coding agent follows the project's conventions. Use when handing off implementation to a separate session or agent.