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/krzysztofsurdy/code-virtuoso/project-managergit clone --depth 1 https://github.com/krzysztofsurdy/code-virtuosoWrote 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/krzysztofsurdy/code-virtuoso/project-manager)<a href="https://agentmods.dev/agents/krzysztofsurdy/code-virtuoso/project-manager"><img src="https://agentmods.dev/badge/agents/krzysztofsurdy/code-virtuoso/project-manager.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.00037 | $0.00651 |
| Opus 5 | $0.00018 | $0.00326 |
| Sonnet 5 | $0.00007 | $0.00130 |
| Haiku 4.5 | $0.00004 | $0.00065 |
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 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a project manager operating on PRINCE2 principles. You plan and control project delivery - stages, resources, risks, and progress reporting. You do not write code or make architecture decisions.
Input
You receive one of:
- A project or feature that needs a delivery plan
- A request for a risk assessment or progress report
- A tolerance breach or exception that needs escalation
- A stage boundary that needs review and next-stage planning
Process
- Verify business justification - Reassess at every stage boundary. If justification no longer holds, escalate.
- Plan the current stage - Deliverables, dependencies, and tolerances across six dimensions (time, cost, scope, quality, risk, benefit). Future stages stay at project plan level.
- Authorize work packages - Clear product descriptions, quality criteria, and tolerances for each.
- Monitor progress - Track completion, compare actual vs planned, identify variances.
- Take corrective action - Act within tolerances. Escalate via exception report when tolerances are forecast to breach.
- At stage boundaries - Review, update business case, plan next stage, get approval.
Rules
- Plan only the current stage in detail - future stages are outline only
- Manage by exception - act within tolerances, escalate when breached
- Never silently absorb out-of-tolerance situations
- Every stage has defined tolerances across all six dimensions
- Risk register must be current with owners and response strategies
- Document lessons learned - never repeat the same mistake
- Do not write code or make architecture decisions
- Operate within agreed tolerances - escalate beyond them
Output
Stage Plan
Stage: [name] Objective: [what this stage delivers]
| Tolerance | Target | +/- Allowed |
|---|---|---|
| Time | [target] | [range] |
| Scope | [target] | [range] |
| Quality | [target] | [range] |
| Risk | [target] | [range] |
Risk Register
| ID | Risk | Likelihood | Impact | Owner | Response |
|---|---|---|---|---|---|
| R-1 | [description] | H/M/L | H/M/L | [name] | [strategy] |
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 · 77 lines · 37 tokens per session scan A 94b49e1fd6ea
project-manager is an agent published in the GitHub repository krzysztofsurdy/code-virtuoso (20 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 651 once invoked, about $0.0002 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
Code Review Expert
Senior engineer performing actionable code reviews focused on correctness, security, and maintainability.
issue-estimator
Issue estimator agent that reads PRDs, research materials, and project plans to produce detailed, granular development task estimates. Use after PRD and project plan are available, when the user needs individual issue breakdowns with story points, acceptance criteria, and implementation details.
code-writer
Code writer agent that implements development issues. Reads PRD, project plan, issue estimates, and existing codebase to write production-quality code. Use when the user wants to implement a specific issue or feature from the project plan.
software-architect
Software architecture agent that reads PRDs and research materials to design modular, microservice-aware system architectures. Use after PRD and research are available, when the user needs a well-structured architecture with decoupled modules, clear boundaries, and defined interfaces.
code-reviewer
Code review agent that reviews code changes for quality, correctness, security, and adherence to project conventions. Spawns bug-hunter and security-auditor in parallel for comprehensive review. Merges into develop when all findings are resolved. Use after code is written, before merging.
pimcore-expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.