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 NVZver/claude-marketplace --skill flow-selectorgit clone --depth 1 https://github.com/NVZver/claude-marketplaceWrote 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/nvzver/claude-marketplace/flow-selector)<a href="https://agentmods.dev/skills/nvzver/claude-marketplace/flow-selector"><img src="https://agentmods.dev/badge/skills/nvzver/claude-marketplace/flow-selector/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.
<a href="https://agentmods.dev/skills/nvzver/claude-marketplace/flow-selector"><img src="https://agentmods.dev/badge/skills/nvzver/claude-marketplace/flow-selector.svg" alt="Reviewed on agentmods" width="80" 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.00067 | $0.01168 |
| Opus 5 | $0.00034 | $0.00584 |
| Sonnet 5 | $0.00013 | $0.00234 |
| Haiku 4.5 | $0.00007 | $0.00117 |
Grade A, and why
flow-selector 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 10d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trace. On load, print first:
=============== [core/skills/flow-selector/SKILL.md] [core] ===============
Flow Selector
Classify a task into Quick / Standard / Extended by weighing boundary signals, then stop and wait for the human to confirm the flow before any downstream LSA ceremony fires. Per .lsa/VISION.md §4: "the orchestrator picks the flow by chain-of-thought, then states its reasoning and the human confirms or overrides."
Three flows, named by process shape:
- Quick — single pass, no LSA ceremony.
- Standard — light discovery + agent TDD + verify.
- Extended — full spec-driven flow: discover → specify → verify → delegate → reconcile.
Goal
Produce a flow label (Quick, Standard, or Extended) plus a 2–4-sentence rationale keyed to the boundary signals, present both to the human, and wait for an explicit confirmation before any LSA skill fires.
Input
- The user's most recent task description (one or more sentences in natural language).
- The current repo state (only as needed to answer "does a spec already exist for this module?").
Steps
-
List the boundary signals present in the task. Apply the five-item checklist at
../../../.lsa/VISION.md§4 — new module · API/contract change · data-model change · ~5 files · no existing spec.Observable result: a five-item bulleted checklist with
yes/nonext to each signal, derived only from the task description (and a minimal repo read if needed for the spec-exists question). -
Apply the classification table at
../../../.lsa/VISION.md§4 — four worked-example rows mapping pattern → flow.Observable result: the matched row (or the closest analogue) named in the chain-of-thought.
-
State the chain-of-thought as a one-paragraph summary keyed to the signals from Step 1 and the matched row from Step 2. Observable result: a 2–4-sentence rationale printed back to the human.
-
Propose flow + rationale to the human and stop. Present:
- the proposed flow label (Quick / Standard / Extended)
- the 5-signal checklist from Step 1 (yes/no per signal)
- the rationale paragraph from Step 3
- decision. Prompt voice (per
../output/SKILL.mdRule 5). Picker question: "Run<task-subject>as a Quick / Standard / Extended flow?". Option labels:
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.
- 10d ago First seen · 73 lines · 67 tokens per session scan A cbbe2677213e
flow-selector is a skill published in the GitHub repository NVZver/claude-marketplace (1 stars, last pushed 15d ago), licensed MIT. It adds 67 tokens to every session and 1,168 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
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
create-app
Guided journey from a raw app idea to a validated, cleanly architected first version that ships on a sustainable cadence. Orchestrates ten skills phase by phase - lean-startup, design-sprint, clean-architecture, domain-driven-design, clean-code, pragmatic-programmer, system-design, ios-hig-design, 37signals-way…
create-business
Guided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills phase by phase - jobs-to-be-done, mom-test, design-sprint, lean-startup, good-strategy-bad-strategy, blue-ocean-strategy, obviously-awesome, hundred-million-offers, monetizing-innovation…
clean-architecture
Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go"…