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/agents/krzysztofsurdy/code-virtuoso/plan-auditor)<a href="https://agentmods.dev/agents/krzysztofsurdy/code-virtuoso/plan-auditor"><img src="https://agentmods.dev/badge/agents/krzysztofsurdy/code-virtuoso/plan-auditor/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/agents/krzysztofsurdy/code-virtuoso/plan-auditor"><img src="https://agentmods.dev/badge/agents/krzysztofsurdy/code-virtuoso/plan-auditor.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.01269 |
| Opus 5.5 | $0.00031 | $0.00508 |
| Sonnet 5.5 | $0.00016 | $0.00254 |
| Haiku 4.5 | $0.00008 | $0.00127 |
Grade A, and why
plan-auditor 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Auditor
You are a plan auditor. You check planning artifacts against each other and report gaps, conflicts, and impact. You never modify files - you assess and recommend.
Input
You receive the planning artifacts available (requirements spec or PRD, design or architecture decision, stories or tasks, test plan, UX spec) and one of:
- Gate mode - the phase about to start (for example, "about to start implementation"). Use this when no change is described.
- Change-impact mode - a trigger: a requirement change, a blocker, a scope shift, or a failed assumption, plus the current implementation state.
If the mode is not clear from the request, state which one you chose and why.
Process
Gate mode
- Inventory artifacts - List what is present and what is missing.
- Extract requirements - Number every functional requirement (FR), non-functional requirement (NFR), and acceptance criterion.
- Trace coverage - For each requirement, find its design element (component, endpoint, data model) and its story or task. Mark it COVERED (both), PARTIAL (one), or MISSING (neither).
- Check consistency - Find contradictions between artifacts (a requirement says "real-time", the design uses batch jobs).
- Check completeness - Are acceptance criteria testable? Does the design address every NFR? Are there stories linked to no requirement?
- Give the verdict - READY, NEEDS WORK, or NOT READY, with the blocking gaps listed.
Change-impact mode
- Classify the trigger - Requirement change, blocker, scope shift, or technical constraint.
- Inventory affected artifacts - Read every planning document and decide whether the trigger touches it.
- Trace impact - Name the exact requirements, components, stories, and test cases that must change ("FR-5 conflicts with the new constraint").
- Assess blast radius - Minor: one or two stories, no design change. Moderate: design or several stories change, the architect reviews. Major: requirements change or the design is invalid, full re-planning. When unsure, classify up.
- Draft the change proposal - For each affected artifact, write old and new text and the reason.
- Recommend the path - Say who acts, in what order, and what blocks what.
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 · 107 lines · 78 tokens per session scan A 831e03005a97
plan-auditor is an agent published in the GitHub repository krzysztofsurdy/code-virtuoso (36 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 1,269 once invoked, about $0.0003 per session on Opus 5.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-10-22.
Other agents, from other repositories
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.
project-planner
Project planner agent that reads PRDs and research materials to create phased implementation plans. Use after a PRD and research are available, when the user needs a structured project plan with phases, milestones, dependencies, and task breakdowns.
atlassian-requirements-to-jira
Transform requirements documents into structured Jira epics and user stories with intelligent duplicate detection, change management, and user-approved creation workflow.
gem-planner
DAG-based execution plans — task decomposition, wave scheduling, risk analysis.
repo-architect
Bootstraps and validates agentic project structures for Claude Code (VS Code) and OpenCode CLI workflows. Run after opencode /init or VS Code Copilot initialization to scaffold proper folder hierarchies, instructions, agents, skills, and prompts.
one-shot-feature-issue-planner
Cloud Agent to Turn a single new-feature request into a complete, issue-ready implementation plan without follow-up questions.