Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add NVZver/claude-marketplace/plugin install lsaWrote 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/init)<a href="https://agentmods.dev/skills/nvzver/claude-marketplace/init"><img src="https://agentmods.dev/badge/skills/nvzver/claude-marketplace/init/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/init"><img src="https://agentmods.dev/badge/skills/nvzver/claude-marketplace/init.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.00020 | $0.00801 |
| Opus 5 | $0.00010 | $0.00400 |
| Sonnet 5 | $0.00004 | $0.00160 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
init 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 8d 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:
=============== [lsa/skills/init/SKILL.md] [lsa] ===============
LSA Init
See CORE.md.
Role
Project scaffolder.
Goal
Stand up the LSA spec tree so the other skills can run.
Inputs
| Input | Source |
|---|---|
.lsa.yaml (or defaults) |
self |
| Existing code (brownfield module inference) | discover |
Steps
-
Resolve config —
constitution/specs_root/mode(defaults:.lsa/VISION.md,.lsa/,code); print it. (→ config) -
Greenfield: create under
${specs_root}/—main.spec.md,roadmap.yaml(YAML ledger SoT — starter below),research-backlog.md,modules/,features/,standards/{code,testing}.md,archive/; fillstandards/from the constitution. Do not createroadmap.md. Starter ledger (write exactly):version: 1 items: [] shipped_history: []After writing, quote the new
roadmap.yamlinline (and a one-line list of the other created paths) per../../../core/skills/output/SKILL.mdRule 7 — never "spec tree created" without the quoted ledger. Observable result:${specs_root}/roadmap.yamlexists and is quoted;${specs_root}/roadmap.mddoes not. (→ spec tree) -
Existing markdown roadmap: if
${specs_root}/roadmap.mdexists and${specs_root}/roadmap.yamldoes not (or both exist), do not invent a second SoT by hand — load and follow../../knowledge/migration-instructions-ai.md(migrate → verify → rewire → cleanup). Observable result: migration report cited, or an explicit skip with reason. (→ migrated ledger or deferred) -
Brownfield modules: via
discover, infer onemodules/<name>/spec.mdper logical module fromartifact_paths(or/src); tag every inferred line[ASSUMPTION](CORE §1); show, approve, write. (→ module specs) -
Project map: run the shipped builder — prefer
bash "${CLAUDE_PLUGIN_ROOT}/scripts/project-map-build.sh"whenCLAUDE_PLUGIN_ROOTpoints at the installedlsaplugin; otherwisebash lsa/scripts/project-map-build.shfrom a marketplace checkout. Observable result: repo-rootproject-map.yamlexists (3-level directory tree). Skip only if the script cannot be found — note the gap; discover falls back to a tree-walk. (→ project-map.yaml)
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.
- 8d ago First seen · 55 lines · 20 tokens per session scan A 983aa28ceb31
init is a skill published in the GitHub repository NVZver/claude-marketplace (1 stars, last pushed 14d ago), licensed MIT. It adds 20 tokens to every session and 801 once invoked, about $0.0001 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…