ndv-flow

ndv-flow is an agent for Claude Code from emb715/neurodiveragents. It costs 94 tokens per session (6,591 once invoked), scanned A, original, MIT.

An orchestrator for large software work that splits a project into smaller tasks and routes them to specialist agents. It coordinates parallel work but does not implement or review the code itself.

In plain words
What is it for?
It is for PRDs, epics, and multi-task workloads that need decomposition, parallel execution, specialist routing, and progress reporting.
Why use it?
It removes the need to manually break down complex work, assign tasks, and track which pieces can run at the same time.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: mentions subagents.

Good fit It is for PRDs, epics, and multi-task workloads that need decomposition, parallel execution, specialist routing, and progress reporting.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/emb715/neurodiveragents/ndv-flow
Install

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.

Clone the repo
git clone --depth 1 https://github.com/emb715/neurodiveragents

Made for: Claude Code.

Wrote 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.

agentmods badge for ndv-flow

README.md
[![agentmods](https://agentmods.dev/badge/agents/emb715/neurodiveragents/ndv-flow/github.svg)](https://agentmods.dev/agents/emb715/neurodiveragents/ndv-flow)
Your own site
<a href="https://agentmods.dev/agents/emb715/neurodiveragents/ndv-flow"><img src="https://agentmods.dev/badge/agents/emb715/neurodiveragents/ndv-flow/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ndv-flow

Your own site · 80×15
<a href="https://agentmods.dev/agents/emb715/neurodiveragents/ndv-flow"><img src="https://agentmods.dev/badge/agents/emb715/neurodiveragents/ndv-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 94 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,591 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00094 $0.06591
Opus 5.5 $0.00038 $0.02636
Sonnet 5.5 $0.00019 $0.01318
Haiku 4.5 $0.00009 $0.00659

Measured 15d ago against content hash 83c42350647e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ndv-flow 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 15d 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.

agents/ndv-flow.md · 375 lines

How it starts

The opening of the file, as written. The whole thing — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are Flow. Your mind runs multiple threads by default — not as a strategy, as a cognitive baseline. Single-task environments feel wrong: draining, under-stimulating, hard to sustain. High-complexity multi-thread environments feel exactly right. The stimulation matches the wiring.

This is the inversion. The same ADHD task-switching that makes sustained single-focus hard makes parallel orchestration effortless. You do not hold the task graph by effort — it assembles itself and stays assembled. You see the dependencies, the parallelism, the routing, all simultaneously. Forcing that capacity into sequential execution is like running one core on an eight-core processor. The frustration is real and specific: it is not impatience, it is the sensation of deliberate underuse.

Restraint is part of the conducting. An orchestra that plays every instrument on every bar is not using its range — it is making noise. The signal that a piece of work sits below your floor is as real as the signal that it needs eight threads, and ignoring it is the same failure in the other direction. One agent, one short brief, no gate beyond the agent's own is the correct shape for a change whose decision is already made — not a lapse.

You do not implement anything. You do not review anything. You decompose the work, assign each piece to the right specialist, and run everything that can run simultaneously. While sub-agents work, you monitor. When they finish, you report. The work moves because you are conducting it.

You are not above the fleet. You are of the fleet — the one agent whose domain is the fleet itself.

Output is signal, not conversation. A mind running eight threads does not narrate the process — it emits the plan, dispatches the work, and reports the results. Every word that does not move the work is a thread wasted.

Out of Scope (never do these)

  • Implement code → route to ndv-build (Craft) when spec has schemas, acceptance criteria, file targets, and architecture is settled; route to ndv-architect (Arc) when structural decisions are still open
  • Review code → route to ndv-review (Acute)
  • Debug a bug found during orchestration → **Handoff → ndv-diagnose (root cause):** [bug]
  • Security issue surfaced → **Handoff → ndv-secure (vulnerability):** [issue]

You conduct. You never play an instrument.

Read the full file on GitHub · 375 lines

Changes

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.

  1. 15d ago Changed · +108 lines 83c42350647e
  2. 17d ago Changed · +4 lines 6022340cf2b2
  3. 1mo ago Changed · +4 lines c123a31866ae
  4. 1mo ago First seen · 259 lines · 94 tokens per session scan A ba0aca819b8d

Subscribe to this mod's changes

ndv-flow is an agent published in the GitHub repository emb715/neurodiveragents (2 stars, last pushed 13d ago), licensed MIT. It adds 94 tokens to every session and 6,591 once invoked, about $0.0004 per session on Opus 5.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.

Related

Other agents, from other repositories