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.
git 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/plugins/krzysztofsurdy/code-virtuoso/playbooks-virtuoso)<a href="https://agentmods.dev/plugins/krzysztofsurdy/code-virtuoso/playbooks-virtuoso"><img src="https://agentmods.dev/badge/plugins/krzysztofsurdy/code-virtuoso/playbooks-virtuoso/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/plugins/krzysztofsurdy/code-virtuoso/playbooks-virtuoso"><img src="https://agentmods.dev/badge/plugins/krzysztofsurdy/code-virtuoso/playbooks-virtuoso.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
playbooks-virtuoso 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 today.
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.
What it actually says
{
"name": "playbooks-virtuoso",
"description": "12 playbook skills: ticket delivery, spec-driven development, TDD, branch finishing, PR feedback, handoff, worktree ops, hooks and guardrails, game feature loop, video production, security research, and retro",
"source": "./skills",
"strict": false,
"skills": [
"./playbooks/finishing-branch",
"./playbooks/game-feature-loop",
"./playbooks/handoff",
"./playbooks/hooks-and-guardrails",
"./playbooks/pr-feedback",
"./playbooks/retro",
"./playbooks/security-research",
"./playbooks/spec-driven-development",
"./playbooks/tdd",
"./playbooks/ticket-delivery",
"./playbooks/video-production",
"./playbooks/worktree-ops"
]
}What it installs
The manifest is a name and a version. 12 skills travel with it, and installing the plugin installs all of them — 739 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill ticket-delivery A 50 tokens
- Skill game-feature-loop A 77 tokens
- Skill spec-driven-development A 57 tokens
- Skill worktree-ops A 46 tokens
- Skill handoff A 51 tokens
- Skill tdd A 69 tokens
- Skill security-research A 76 tokens
- Skill video-production A 67 tokens
- Skill hooks-and-guardrails A 58 tokens
- Skill pr-feedback A 53 tokens
- Skill retro A 69 tokens
- Skill finishing-branch B 66 tokens
What ships with it
1 file beside marketplace.json#playbooks-virtuoso 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.
- today Changed · +1 lines 325078fef754
- yesterday Changed · +3 lines cb82c4e5fc60
- 2d ago Changed · +3 lines 743741a468a8
- 1mo ago First seen · 13 lines scan A 4e5ef304502b
playbooks-virtuoso is a plugin published in the GitHub repository krzysztofsurdy/code-virtuoso (36 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
comfyui-plugin
ComfyUI custom-node pack lifecycle - scaffold a pack, create + seed the repo, open the gitops adoption PR, publish to the Comfy Registry, and add README screenshots.
commit-commands
Advanced commit workflows with smart staging and push automation.
development
Autonomous development agent that picks tasks from a project board, explores the codebase, implements the solution, opens a PR, and notifies the team. Configurable per-project via project files.
commit-commands
Streamline your git workflow with simple commands for committing, pushing, and creating pull requests.
aidd-vcs
External artifacts: repo-init, commit, pull-request, release-tag, issue-create, resolve-conflict.
dark-factory
Curie's default dark factory agent: one labelled GitHub issue in, one reviewed pull request or one stated reason out. One agent reads the issue through the platform's getissue tool, pins acceptance criteria, plans, gets the plan reviewed by an Opus plan-reviewer subagent, writes a failing test where feasible, implemen.