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 discovergit 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/discover)<a href="https://agentmods.dev/skills/nvzver/claude-marketplace/discover"><img src="https://agentmods.dev/badge/skills/nvzver/claude-marketplace/discover/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/discover"><img src="https://agentmods.dev/badge/skills/nvzver/claude-marketplace/discover.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.00038 | $0.00392 |
| Opus 5 | $0.00019 | $0.00196 |
| Sonnet 5 | $0.00008 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
discover 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.
What it actually says
Trace. On load, print first:
=============== [lsa/skills/discover/SKILL.md] [lsa] ===============
LSA Discover
See CORE.md. Step 1 of the loop, and the input-resolver other skills call.
Role
Requirements analyst.
Goal
Produce the intent and the cited codebase facts the spec will be grounded on.
Inputs
| Input | Source |
|---|---|
| The request | user (free text) |
.lsa.yaml, constitution, the code/specs the request touches |
self |
Steps
- Read
.lsa.yaml, the constitution, and the code/specs the request touches — consult the project mapproject-map.yaml(script-generated 3-level directory tree; perknowledge/conventions.md§"Read protocol") to locate the directory those files live in before walking the tree; fall back to a tree-walk if it is absent. Cite eachfile:line; tag any gap[ASSUMPTION](CORE §1). (→ codebase facts) - Extract intent — which user flow, for which module. Ask only what isn't derivable from the facts. (→ intent)
- Hand intent + facts to
specify. (→ handoff)
Output
Intent + cited codebase facts (the grounding source for specify and verify).
Constraints
- Infer from repo state; never ask for what's derivable. Don't invent module names absent from
.lsa.yaml.
/lsa:discover — manual invocation.
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 · 44 lines · 38 tokens per session scan A 11e87c7dce29
discover is a skill published in the GitHub repository NVZver/claude-marketplace (1 stars, last pushed 16d ago), licensed MIT. It adds 38 tokens to every session and 392 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
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"…