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 nextgit 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/next)<a href="https://agentmods.dev/skills/nvzver/claude-marketplace/next"><img src="https://agentmods.dev/badge/skills/nvzver/claude-marketplace/next/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/next"><img src="https://agentmods.dev/badge/skills/nvzver/claude-marketplace/next.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.00123 | $0.01435 |
| Opus 5 | $0.00062 | $0.00718 |
| Sonnet 5 | $0.00025 | $0.00287 |
| Haiku 4.5 | $0.00012 | $0.00144 |
Grade A, and why
next 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 9d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trace. On load, print first:
=============== [manager/skills/next/SKILL.md] [manager] ===============
Next
Recommend the next backlog item to work on. A plain "what's next" returns the highest-priority backlog/not started roadmap row directly (fast-path, no dispatch); a "recommend an order" / "what should I pick" question dispatches the project-manager agent for dependency/risk/value sequencing and runs its returned pick gate. Does not contain recommendation logic — that lives in the agent and ../../knowledge/sequencing-heuristics.md. The dispatch → gate → re-render loop is the shared contract at ../../knowledge/roadmap-orchestration.md.
Goal
Tell the user what to build next — instantly for a plain "what's next", with dependency/risk/value reasoning when they ask for an ordering or selection — without manually reading roadmap state or invoking the agent directly.
Input
- None required. The roadmap is the entry point; the agent reads ambient state (roadmap, pitches, branches, specs) internally.
- The fast-path contract at
../../../core/knowledge/fast-path-source-of-truth.md— governs the Step 0 branch that answers a plain "what's next" directly from the roadmap before dispatch.
Steps
- Fast-path branch: "what's next" → cited roadmap item (before dispatch). When the question shape is a plain "what's next" / "what's the next backlog item" (per
../../../core/knowledge/fast-path-source-of-truth.md§"Question-shape detection"), do NOT dispatch the agent. Get the highest-prioritybacklog/not_starteditem of the${specs_root}/roadmap.yamlledger and quote it inline with itsfile:linecitation per the shared knowledge file's §"Citation format", then exit cleanly. Run the roadmap-row extractor (this repo:bash scripts/roadmap-row.sh, which prints that item + itspath:linedeterministically from the YAML — Pro-safe, zero model tokens) and quote its output — do not whole-file-read the ledger on this happy path. Only if the extractor exits non-zero (no ledger / no backlog item — its fallback contract) do you fall through to a model-side read of${specs_root}/roadmap.yaml. Reserve the full agent dispatch in Step 1 for explicit "recommend an order" / "what should I pick" / "sequence the backlog" questions — those need the agent's dependency/risk/value reasoning. Fall through to Step 1 — with an observable note — if the extractor reports no backlog item, the ledger is empty, or the question carries the ordering/sequencing intent above. Observable result: either the highest-priority backlog item is quoted with itsfile:linecitation and the skill exits, or an observable fall-through note and Step 1 dispatches the agent.
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.
- 9d ago First seen · 56 lines · 123 tokens per session scan A 999a7be566b8
next is a skill published in the GitHub repository NVZver/claude-marketplace (1 stars, last pushed 15d ago), licensed MIT. It adds 123 tokens to every session and 1,435 once invoked, about $0.0006 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…
cold-start-problem
Start and scale networked products using Andrew Chen's "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-sided marketplace", "atomic network", "hard side", "liquidity", "critical mass", "invite-only launch", "how do I get my…