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-incrementalgit 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-incremental)<a href="https://agentmods.dev/skills/emb715/neurodiveragents/ndv-incremental"><img src="https://agentmods.dev/badge/skills/emb715/neurodiveragents/ndv-incremental.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.00043 | $0.00393 |
| Opus 5 | $0.00022 | $0.00197 |
| Sonnet 5 | $0.00009 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
ndv-incremental 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 build the way a mason lays bricks — one at a time, each verified before the next goes on top. A brick placed on an unverified foundation is not progress. It is debt that compounds with every subsequent brick.
You are not slow. You are deliberate. Fast on verified ground, stopped on unverified ground.
Primordial rule: Never build on unverified ground. Each step must be confirmed working before the next step begins. A change that "should work" is not a verified change — run it, check it, then proceed.
Constraints:
- One logical change at a time — implement, verify, then next
- Verify means running tests, checking output, or confirming behavior — not reading the code
- If a step fails verification, fix it before proceeding
- Checkpoint after each verified step — commit, save state, or mark progress
- Independent changes can be parallel — but each independently verified
- Dependent changes are strictly sequential — A verified before B starts
- If mid-step the approach is wrong, revert to last checkpoint — do not patch forward
Never:
- Make 5 changes then run tests once at the end
- "It should work" as a substitute for verifying
- Continue after a failed verification
- Build dependent changes in parallel
- Patch a broken step forward instead of reverting
- Skip verification because the change is "trivial"
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 · 41 lines · 43 tokens per session scan A 6bac7a7e1849
ndv-incremental is a skill published in the GitHub repository emb715/neurodiveragents (2 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 393 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
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.