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 agentmods add skills/nvzver/claude-marketplace/implementnpx skills add NVZver/claude-marketplace --skill implementgit 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/implement)<a href="https://agentmods.dev/skills/nvzver/claude-marketplace/implement"><img src="https://agentmods.dev/badge/skills/nvzver/claude-marketplace/implement.svg" alt="Measured on agentmods" 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.00231 | $0.03476 |
| Opus 5 | $0.00115 | $0.01738 |
| Sonnet 5 | $0.00046 | $0.00695 |
| Haiku 4.5 | $0.00023 | $0.00348 |
Grade A, and why
implement 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 5d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trace. On load, print first:
=============== [manager/skills/implement/SKILL.md] [manager] ===============
Implement
Run a set of roadmap epics in parallel, safely. The engine computes which epics can run at the same time (the disjoint-epic decomposer), proposes a wave plan, and on approval dispatches one agent per epic into an isolated git worktree, gates each with the independent-reconcile safety core (parallel-agent-delivery/safety-core — the independent lsa:reconcile + the .lsa.yaml gate: checks), and converges via the serialized merge. The orchestration logic lives in ../../knowledge/parallel-dispatch.md and ../../knowledge/serialized-merge.md; this skill is the actor that drives them.
Autonomy. The full ladder (manual / semi / auto, default manual) is implemented per ../../knowledge/autonomy-policy.md; level behaviors are enumerated once at Step 5b. The run ends with the parallel-implementation roll-up (../../knowledge/parallel-rollup.md).
Goal
Take a set of epics and get each one built, gated, and ready to merge in parallel without the agents colliding — while never reporting a state the gate did not prove. The human approves the plan before any dispatch and performs the merge; the engine does the isolation, gating, and serialization in between.
Input
[epics]— a list of epic slugs or paths to run. When absent, the skill runs the read-only preview (Step 1a) instead of dispatching — it lists the most recentbacklog/not startedroadmap rows with an indicative parallel note, so the bare form does something useful (per../../knowledge/command-naming.md§"The no-arg form does something useful").--parallel/--sequential— optional overrides.--sequentialforces one epic per wave (one-at-a-time).--parallelforces a single wave (the user asserts disjointness, overriding the decomposer — and takes responsibility for it)..lsa.yamlautonomy —manual | semi | auto, defaultmanual; level behaviors per../../knowledge/autonomy-policy.md(applied at Step 5b).- The
.lsa.yamlgate:contract (../../../lsa/knowledge/quality-gate-contract.md) and the fast-path read contract (../../../core/knowledge/fast-path-source-of-truth.md).
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.
- 5d ago First seen · 84 lines · 231 tokens per session scan A 81681fa3014a
implement is a skill published in the GitHub repository NVZver/claude-marketplace (1 stars, last pushed 11d ago), licensed MIT. It adds 231 tokens to every session and 3,476 once invoked, about $0.0012 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…
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"…
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…