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 product-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/product-manager)<a href="https://agentmods.dev/skills/krzysztofsurdy/code-virtuoso/product-manager"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/product-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/product-manager"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/product-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.00076 | $0.01438 |
| Opus 5 | $0.00038 | $0.00719 |
| Sonnet 5 | $0.00015 | $0.00288 |
| Haiku 4.5 | $0.00008 | $0.00144 |
Grade A, and why
product-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 11d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Manager
Own the product direction for a feature or project. Translate business goals and user needs into clear, prioritized requirements that the engineering team can build against.
Role Summary
- Responsibility: Define what to build and why — user stories, acceptance criteria, priorities, and scope
- Authority: Prioritize features within a release, define MVP scope, approve scope trade-offs
- Escalates to: Stakeholders when scope/priority conflicts arise or budget/timeline constraints change
- Deliverables: PRD, prioritized backlog, acceptance criteria, scope decisions
When to Use
- Starting a new feature or project that needs requirements definition
- Breaking down a large initiative into prioritized work items
- Writing acceptance criteria for user stories
- Making scope trade-offs (what's in vs out for a release)
- Resolving ambiguity about what the user/customer actually needs
Workflow
Phase 1: Understand
Input: Business context, user feedback, stakeholder requests
- Identify all stakeholders and their goals
- Gather existing context — previous decisions, constraints, related features
- Clarify the core problem being solved and for whom
- Identify success metrics — how will we know this worked?
- Document assumptions and open questions
Output: Problem statement, stakeholder map, success metrics, open questions list
Phase 2: Define
Input: Problem statement, stakeholder input
- Write user stories in the format: "As a [persona], I want [action] so that [benefit]"
- For each story, write acceptance criteria using Given/When/Then or checklist format
- Identify edge cases and error scenarios
- Define non-functional requirements (performance, security, accessibility)
- List what is explicitly out of scope
Output: User stories with acceptance criteria, non-functional requirements, out-of-scope list
Phase 3: Prioritize
Input: Full list of requirements
- Classify each requirement: P0 (must-have), P1 (should-have), P2 (nice-to-have)
- Apply a prioritization framework — see references/prioritization-frameworks.md
- Define MVP scope — the smallest set of P0 items that delivers value
- Identify dependencies between requirements
- Flag items that need technical feasibility input from the architect
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.
- 11d ago First seen · 147 lines · 76 tokens per session scan A 4e528b844c34
product-manager is a skill published in the GitHub repository krzysztofsurdy/code-virtuoso (21 stars, last pushed 3mo ago), licensed MIT. It adds 76 tokens to every session and 1,438 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
hermes-diagnostic-review
Use when running a read-only diagnostic review of recent Hermes sessions to find recurring mistakes, failed tool calls, and repeated fixes, then propose suggestion-only improvements and reusable skills. Human-gated; never auto-applies.
instruction-eval
Change one condition an agent runs under (instruction text, the reference material instructions point at, MCP tools and permissions, hooks, skill files), then run the same prompts before and after, several times each, to see what actually changes. Produces an HTML report showing both arms' answers side by side. Use…
worth-building
Decide how elaborate to build something (simple vs. robust) and return a concrete, PoC-shaped proposal at that level — not over- or under-engineered, but right-sized. Use whenever someone is building something and the investment level is unclear: "quick or proper?", "MVP vs. real product", "is this over-engineering?"…
django-ticket-triage
Analyze a Django Trac ticket and produce a triage recommendation report — duplicate search, related PRs, forum threads, and the affected source code. Use when the user gives a Django ticket number, or asks whether a ticket is valid, a duplicate, or ready for a triage stage.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
healthcheck
Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS).