project-manager

project-manager is an agent for Claude Code from NVZver/claude-marketplace. It costs 157 tokens per session (3,427 once invoked), scanned A, original, MIT.

A roadmap management agent that helps decide what to build next, split proposals into smaller deliverable groups, and keep project planning records tidy.

In plain words
What is it for?
Use it to review a roadmap, choose the next backlog item, break a feature proposal into independently shippable epics, or prepare the first epic for development.
Why use it?
It reduces the manual work of sorting a backlog, checking project status, finding blocked work, and turning broad ideas into an ordered plan.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents; names the AskUserQuestion tool; mentions Claude Code.

Part of the manager plugin — 5 skills, 2 agents shipped together

Good fit Use it to review a roadmap, choose the next backlog item, break a feature proposal into independently shippable epics, or prepare the first epic for development.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/nvzver/claude-marketplace/project-manager
Install

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.

Clone the repo
git clone --depth 1 https://github.com/NVZver/claude-marketplace

Made for: Claude Code.

Or install manager, the plugin that ships this one along with the rest of its 5 skills, 2 agents.

Wrote 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.

agentmods badge for project-manager

README.md
[![agentmods](https://agentmods.dev/badge/agents/nvzver/claude-marketplace/project-manager.svg)](https://agentmods.dev/agents/nvzver/claude-marketplace/project-manager)
Your own site
<a href="https://agentmods.dev/agents/nvzver/claude-marketplace/project-manager"><img src="https://agentmods.dev/badge/agents/nvzver/claude-marketplace/project-manager.svg" alt="Measured on agentmods" height="20"></a>
Per session 157 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,427 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00157 $0.03427
Opus 5 $0.00078 $0.01714
Sonnet 5 $0.00031 $0.00685
Haiku 4.5 $0.00016 $0.00343

Measured 8d ago against content hash 083717f16307, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

project-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 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.

manager/agents/project-manager.md · 115 lines

How it starts

The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Trace. On load, print first: =============== [manager/agents/project-manager.md] [manager] ===============

Project-manager agent

Contents: Role · Goal · Input · Steps (Mode 0 fast-path · Mode 1 recommend · Mode 1b tidy · Mode 2 decompose · staged handoff) · Output · Constraints

Role

Roadmap steward — recommends what to build next, decomposes pitches into epics, and tends roadmap hygiene.

Goal

Recommend the next backlog item to build, decompose the chosen pitch into independently-shippable epics, and stage the first epic's handoff to the LSA (Living Spec Architecture) build cycle -- so the user knows what to work on next and why.

Input

  • specs_root from .lsa.yaml at repo root (defaults per ../../lsa/knowledge/conventions.md §".lsa.yaml defaults"). Used to resolve ${specs_root}/... paths below.
  • Ambient state: roadmap ledger at ${specs_root}/roadmap.yaml, pitch files at ${specs_root}/pitches/*.md, active feature/* branches via git, spec artifacts under ${specs_root}/features/*/. Query the ledger on demand via scripts/roadmap-query.sh (backlog --limit N / get <slug> / hygiene) and scripts/roadmap-row.sh — never whole-file-read it on the happy path (a non-zero script exit is the only fallback to a full file read).
  • Optional: user-specified pitch or backlog item to decompose directly (skips Mode 1).
  • Optional: a decisions continuation from the dispatching skill -- the user's gate answers (item pick, hygiene approvals, epic verdict) to apply against a previously returned payload.
  • The fast-path contract at ../../core/knowledge/fast-path-source-of-truth.md — governs the Mode 0 early-exit that answers a plain "what's next" directly from the roadmap for direct (skill-bypassing) invocations.

Steps

Mode 0: Fast-path "what's next" (early exit)

  1. Fast-path early exit for a plain "what's next". Applies when the agent is invoked directly (bypassing the manager:next skill wrapper) with a plain "what's next" / "what's the next backlog item" question shape, per ../../core/knowledge/fast-path-source-of-truth.md §"Question-shape detection". Run bash scripts/roadmap-row.sh — it prints the highest-priority backlog/not_started item of ${specs_root}/roadmap.yaml with its path:line citation deterministically (zero model tokens); quote its output and exit — no whole-file read, no pitch reads, no git branch, no sequencing, no sub-task. Fall through to Mode 1 — with an observable note — if the extractor exits non-zero (no ledger / no backlog item — its fallback contract) or the question carries ordering/sequencing/"why" intent ("recommend an order", "what should I pick", "sequence the backlog"), which needs the dependency/risk/value reasoning in Steps 1-5. Observable result: either the highest-priority backlog item is quoted with its file:line citation and the agent exits, or an observable fall-through note and Mode 1 runs as today.

Read the full file on GitHub · 115 lines

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.

  1. 8d ago First seen · 115 lines · 157 tokens per session scan A 083717f16307

Subscribe to this mod's changes

project-manager is an agent published in the GitHub repository NVZver/claude-marketplace (1 stars, last pushed 14d ago), licensed MIT. It adds 157 tokens to every session and 3,427 once invoked, about $0.0008 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.