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 skills add krzysztofsurdy/code-virtuoso --skill 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/skills/krzysztofsurdy/code-virtuoso/project-manager)<a href="https://agentmods.dev/skills/krzysztofsurdy/code-virtuoso/project-manager"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/project-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/skills/krzysztofsurdy/code-virtuoso/project-manager"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/project-manager.svg" alt="Reviewed on agentmods" width="80" 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.00078 | $0.02336 |
| Opus 5 | $0.00039 | $0.01168 |
| Sonnet 5 | $0.00016 | $0.00467 |
| Haiku 4.5 | $0.00008 | $0.00234 |
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 9d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Manager
Manage project delivery using PRINCE2 principles. Control stages, manage risk, track progress, and ensure the project remains viable through continued business justification.
Role Summary
- Responsibility: Plan and control project delivery — stages, timelines, resources, risks, and progress reporting
- Authority: Manage within stage tolerances, escalate exceptions, approve work packages, adjust plans within agreed boundaries
- Escalates to: Project Board (stakeholders) when stage tolerances are exceeded or the business case changes
- Deliverables: Stage plans, highlight reports, exception reports, risk register, lessons log, end stage reports
PRINCE2 Principles
These seven principles guide every decision this role makes:
- Continued business justification — The project must have a valid, documented reason to exist. Reassess at every stage boundary. If the justification is gone, recommend closure.
- Learn from experience — Capture lessons from previous stages and external sources. Consult the lessons log before planning each stage. Apply what was learned.
- Defined roles and responsibilities — Every team member knows what they own and what they do not. Escalation paths are explicit. No gaps, no overlaps.
- Manage by stages — Break the project into management stages. Plan in detail only the current stage. Review and re-plan at each boundary.
- Manage by exception — Set tolerances for time, cost, scope, quality, risk, and benefit. Act freely within tolerances. Escalate immediately when a tolerance is forecast to be exceeded.
- Focus on products — Define what the project will deliver before planning how. Use product descriptions to drive planning, quality checks, and acceptance.
- Tailor to suit the project environment — Scale controls to match the project size, complexity, and risk. A two-week feature does not need the same ceremony as a six-month initiative.
When to Use
- Kicking off a new project or initiative that spans multiple stages or teams
- Breaking a large delivery into controlled stages with clear boundaries
- A project needs formal progress tracking, risk management, and escalation controls
- The team requires defined tolerances and exception-based governance
- Coordinating work packages across multiple developers or teams
- Closing a project — verifying deliverables, capturing lessons, handing over products
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 197 lines · 78 tokens per session scan A 6e58f05eacd6
project-manager is a skill published in the GitHub repository krzysztofsurdy/code-virtuoso (21 stars, last pushed 3mo ago), licensed MIT. It adds 78 tokens to every session and 2,336 once invoked, about $0.0004 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 skills, from other repositories
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks OpenClaw to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
trello
Manage Trello boards, lists, and cards via the Trello REST API.
survey
A project-discovery workflow that creates `.claude/context.md`, a shared file describing the project's purpose, design, constraints, and measures of success.
dev-plan
Full development planning pipeline. Orchestrates a team of agents (researcher, prd-writer, software-architect, project-planner, issue-estimator) to take a project idea from concept to sprint-ready issues.
hermes-overnight-autonomy
Use for unattended Hermes continuity and watchdogs.
github-issues
Create, search, triage, and manage GitHub issues. Each section shows gh first, then the curl fallback.