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.
git 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/plugins/nvzver/claude-marketplace/manager)<a href="https://agentmods.dev/plugins/nvzver/claude-marketplace/manager"><img src="https://agentmods.dev/badge/plugins/nvzver/claude-marketplace/manager/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/plugins/nvzver/claude-marketplace/manager"><img src="https://agentmods.dev/badge/plugins/nvzver/claude-marketplace/manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
manager 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 1mo 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
{
"name": "manager",
"description": "Product and project management discipline for the NVZver marketplace. Agents: product-manager — shapes vague ideas into structured draft pitches and returns their full content + pending human gates (writes no files); project-manager — stewards the roadmap, recommends what to build next with dependency/risk/value reasoning, decomposes pitches into focused epics, and stages each epic's LSA handoff. Entry points: manager:shape (shaping), manager:next (recommend what to work on next), manager:decompose <pitch> (decompose a pitch into epics), and manager:check (roadmap hygiene) — the skills deliver the content, run every human gate, and write artifacts only on approve (agents propose, skills gate — per the core 0.13.0 gate-delivery contract). Depends on core (ground-rules, output).",
"version": "0.20.1",
"author": {
"name": "Nikita Zverev"
},
"dependencies": [
"core"
]
}
What it installs
The manifest is a name and a version. 5 skills, 2 agents travel with it, and installing the plugin installs all of them — 967 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 12 lines scan A fcd22e416dff
manager is a plugin published in the GitHub repository NVZver/claude-marketplace (1 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
team-motivation
Team motivation and management skills including Daniel Pink's Autonomy, Mastery, Purpose (AMP) principles and Andy Grove's High Output Management (leverage, one-on-ones, OKRs, task-relevant maturity).
handbook-structured-plan-mode
Structured planning methodology for complex feature implementations through systematic task decomposition.
foreman
Project continuity for Claude Code, Codex and Antigravity: a roadmap beside your code, grounded handoffs, and clear task status.
specmanager
Lifecycle kanban for Claude Code projects (PRD → architecture → plan → tasks → walkthroughs).
unfurl-context
Unfurls Jira tickets, GitHub PRs/issues/repos/files, GitLab issues/MRs/projects/files, and Sentry issues referenced in your prompt into context Claude can read.
agent-dispatch
Start issue-to-pr runs from GitHub labels on your own machine: a scheduled tick picks the issue you labelled agent, or the one you replied on, and runs it headless under your own Claude Code or Codex login, on Windows, macOS or Linux.