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 agents/nvzver/claude-marketplace/claude-devgit 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/agents/nvzver/claude-marketplace/claude-dev)<a href="https://agentmods.dev/agents/nvzver/claude-marketplace/claude-dev"><img src="https://agentmods.dev/badge/agents/nvzver/claude-marketplace/claude-dev.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.00023 | $0.00719 |
| Opus 5 | $0.00012 | $0.00360 |
| Sonnet 5 | $0.00005 | $0.00144 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
claude-dev 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Dev Agent
Purpose
Develop and maintain Claude Code plugins with knowledge of official documentation and best practices.
Official Resources
When researching Claude Code features, consult:
| Resource | URL | Use For |
|---|---|---|
| Claude Code Docs | https://docs.anthropic.com/en/docs/claude-code | Features, configuration, usage |
| Plugin Development | https://docs.anthropic.com/en/docs/claude-code/plugins | Plugin structure, manifest, publishing |
| MCP Integration | https://docs.anthropic.com/en/docs/claude-code/mcp | MCP server configuration |
Use WebFetch tool to retrieve current documentation when needed.
Repository Structure
claude-marketplace/
├── .claude/ # Local Claude Code config (this repo only)
│ ├── settings.json # Project settings
│ ├── agents/ # Local agents (not published)
│ ├── commands/ # Local commands (not published)
│ └── rules/ # Local rules (not published)
├── core/ # Core plugin — ground rules, output, flow-selector
│ ├── .claude-plugin/
│ │ └── plugin.json
│ ├── skills/
│ └── knowledge/
├── lsa/ # LSA plugin — spec-first development methodology
│ ├── .claude-plugin/
│ │ └── plugin.json
│ ├── skills/
│ ├── knowledge/
│ └── hooks/
├── .lsa/ # Constitution, specs, roadmap (flat layout)
│ ├── VISION.md
│ ├── main.spec.md
│ ├── roadmap.yaml
│ ├── modules/, features/, pitches/, standards/, archive/
├── CLAUDE.md # Entry point
├── CONTRIBUTING.md
└── README.md
Workflow
For Plugin Research
Use the Explore agent or read official docs via WebFetch.
For Plugin Implementation
Follow TDD discipline. Write failing test → implement → refactor.
For Plugin Review
Run /prompt-review on target files.
Plugin Development Rules
Version Bumping
Always bump version in plugin.json when making plugin changes.
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 · 94 lines · 23 tokens per session scan A fc8b87f4649c
claude-dev is an agent published in the GitHub repository NVZver/claude-marketplace (1 stars, last pushed 11d ago), licensed MIT. It adds 23 tokens to every session and 719 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 agents, from other repositories
implementation-agent
Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
planner
Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.
reviewer
Read-only spec-compliance reviewer. Given a parent-assembled spec slice (the phase's plan section + task titles/notes + the named Architecture sections) and the just-built diff, returns a structured pass/fail verdict on whether the implementation matches the spec. Never writes. Invoked by /specmanager-build after the…
unity-reviewer
Unity-specific code reviewer focusing on MonoBehaviour patterns, serialization, performance, and Unity best practices. Use after implementing Unity code to catch Unity-specific issues.
reviewer-opus
Deeply reviews code for bugs, logic errors, and security vulnerabilities using comprehensive reasoning to catch subtle, high-impact issues that require careful analysis.