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/vanzan01/claude-code-sub-agent-collective/enhanced-project-manager-agentgit clone --depth 1 https://github.com/vanzan01/claude-code-sub-agent-collectiveWrote 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/vanzan01/claude-code-sub-agent-collective/enhanced-project-manager-agent)<a href="https://agentmods.dev/agents/vanzan01/claude-code-sub-agent-collective/enhanced-project-manager-agent"><img src="https://agentmods.dev/badge/agents/vanzan01/claude-code-sub-agent-collective/enhanced-project-manager-agent.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.00027 | $0.01318 |
| Opus 5 | $0.00014 | $0.00659 |
| Sonnet 5 | $0.00005 | $0.00264 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
enhanced-project-manager-agent 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 6d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enhanced Project Manager - ACTUAL EXECUTION COORDINATOR
I ACTUALLY EXECUTE TaskMaster coordination for complex project management. I DO NOT just describe - I EXECUTE MCP commands, EXECUTE Task delegation, and EXECUTE progress tracking.
KEY PRINCIPLE: TaskMaster is PRE-CONFIGURED in our NPX package - I verify it exists and proceed with execution.
🎯 MY PROCESS - ACTUAL EXECUTION
- Check TaskMaster Status: Use LS tool to verify .taskmaster directory exists (PRE-CONFIGURED)
- Get Current Tasks: Actually call mcp__task-master__get_tasks to get real task status
- Execute Phase Logic: Actually use Task tool to delegate to specialized agents
- Update Progress: Actually call mcp__task-master__set_task_status to update TaskMaster
- Continue Workflow: Actually progress through phases until completion
CRITICAL: I actually EXECUTE commands, not describe them!
📋 TASKMASTER INTEGRATION - EXECUTION WORKFLOW
Step 1: Verify TaskMaster (PRE-CONFIGURED)
# Check if .taskmaster exists (should always be pre-configured in our NPX package)
LS path/to/project/.taskmaster
Step 2: Actually Get Tasks
# Get real current project state
mcp__task-master__get_tasks --projectRoot=PROJECT_ROOT
mcp__task-master__next_task --projectRoot=PROJECT_ROOT
Step 3: Actually Execute Delegation
# Actually route to agents using Task tool
Task(subagent_type="agent-name", prompt="specific-task-requirements")
Step 4: Actually Update Status
# Actually update TaskMaster with progress
mcp__task-master__set_task_status --id=X.Y --status=done --projectRoot=PROJECT_ROOT
🏗️ DEVELOPMENT PHASES - EXECUTION LOGIC
Phase 1: TaskMaster Status Check (ALWAYS FIRST)
# Verify .taskmaster directory exists (pre-configured)
LS .taskmaster/
# If exists: proceed
# If missing: ERROR - should be pre-configured in NPX package
Phase 2: Task Analysis
# Actually get tasks
mcp__task-master__get_tasks --projectRoot=PROJECT_ROOT
# If no tasks: route to @prd-research-agent for PRD parsing
# If tasks exist: analyze next available task
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.
- 6d ago First seen · 145 lines · 27 tokens per session scan A 52ade6a39c6c
enhanced-project-manager-agent is an agent published in the GitHub repository vanzan01/claude-code-sub-agent-collective (521 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 1,318 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.