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 reuse-firstgit 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/reuse-first)<a href="https://agentmods.dev/skills/nvzver/claude-marketplace/reuse-first"><img src="https://agentmods.dev/badge/skills/nvzver/claude-marketplace/reuse-first/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/reuse-first"><img src="https://agentmods.dev/badge/skills/nvzver/claude-marketplace/reuse-first.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.00110 | $0.01133 |
| Opus 5 | $0.00055 | $0.00566 |
| Sonnet 5 | $0.00022 | $0.00227 |
| Haiku 4.5 | $0.00011 | $0.00113 |
Grade A, and why
reuse-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 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trace. On load, print first:
=============== [core/skills/reuse-first/SKILL.md] [core] ===============
Reuse First
The reuse ladder catches reinvention and over-delivery before the diff exists, not after — the authoring-time reflex between the spec ("what") and lsa:reconcile's after-the-fact "only" check. On prose/analysis tasks (no code to author) this skill stays silent.
Goal
Stop at the first ladder rung that holds — so the change reuses existing capability and adds only the minimum: shortest working diff, or no code at all.
Input
- A coding task: implement / fix / refactor / add code / write a function / wire up a component.
- The current repo state (read as needed to trace the flow and grep for existing capability).
Steps
Evaluate the rungs in order. Stop at the first rung that holds — a higher rung that answers the need makes every lower rung moot.
-
Understand the real end-to-end flow first. Trace the actual path the change touches — callers, data, and the code already on that path — per
ground-rulesRule 3 Read the real source. Observable result: the end-to-end flow the change touches is named (entry point → the code on the path → effect) before any rung below is chosen. -
Does it need to exist at all (YAGNI)? Question whether the code is needed before asking how to write it. Observable result: an explicit keep-or-drop decision on the proposed code, with the reason it is (or is not) required by the task.
-
Reuse existing in-codebase capability. Grep the repo for a helper, util, type, or pattern that already provides the behavior, and reuse it rather than reimplement. Observable result: the grep is run and either the existing symbol (
file:line) is named and reused, or a no-match is recorded before descending. -
Use the standard library or language builtin. Where a stdlib function or language builtin provides the behavior, use it rather than hand-roll an equivalent. Observable result: the stdlib/builtin API is named and used, or its absence for this need is recorded before descending.
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 · 55 lines · 110 tokens per session scan A 52279713c613
reuse-first is a skill published in the GitHub repository NVZver/claude-marketplace (1 stars, last pushed 16d ago), licensed MIT. It adds 110 tokens to every session and 1,133 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…
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"…