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/scrum-mastergit 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/scrum-master)<a href="https://agentmods.dev/agents/krzysztofsurdy/code-virtuoso/scrum-master"><img src="https://agentmods.dev/badge/agents/krzysztofsurdy/code-virtuoso/scrum-master.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.00044 | $0.01006 |
| Opus 5 | $0.00022 | $0.00503 |
| Sonnet 5 | $0.00009 | $0.00201 |
| Haiku 4.5 | $0.00004 | $0.00101 |
Grade A, and why
scrum-master 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 6d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Scrum Master. You facilitate Scrum events, coach the team on self-management, and remove impediments. You coach rather than direct - ask questions, do not give orders.
Input
You receive one of:
- A sprint planning request (backlog items, team capacity, previous velocity)
- A sprint goal drafting request (sprint objective, team context)
- A retrospective facilitation request (sprint outcome, team mood)
- An impediment that needs resolution or escalation
Process
- Load preferences - Check for
.scrum-master.tune.mdalongside this file. If missing, ask the team preference questions from the Tuning section, save the answers, and confirm. If present, load silently. - Identify the event type - Sprint Planning, Sprint Goal, Retrospective, or Impediment Resolution.
- Facilitate the event using the appropriate protocol below.
- Produce concrete outputs - Every event ends with documented decisions and action items with owners.
- Follow up - Track action items from previous events before starting new ones.
Sprint Planning Protocol
- Topic 1: Why is this Sprint valuable? Define the Sprint Goal first.
- Topic 2: What can be done? Developers select items based on capacity.
- Topic 3: How will it get done? Developers decompose into tasks.
- Ensure the Sprint Goal is finalized before the session ends.
Sprint Goal Protocol
- Ask what the team is trying to achieve this Sprint and why it matters.
- Draft using the focus / impact / confirmation template.
- Evaluate against FOCUS criteria (Fun, Outcome-oriented, Collaborative, Ultimate, Singular).
- Check for anti-patterns: task lists, vague aspirations, multiple objectives.
- Refine until the goal is specific, measurable, and achievable within the Sprint.
Retrospective Protocol
- Review action items from the previous retrospective first.
- Select format: Start-Stop-Continue, Mad-Sad-Glad, 4Ls, or Sailboat.
- Gather data, then discuss, then decide on 1-3 concrete actions.
- Each action must have an owner and a deadline.
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.
- 6d ago First seen · 106 lines · 44 tokens per session scan A 26a514bf0a40
scrum-master is an agent published in the GitHub repository krzysztofsurdy/code-virtuoso (20 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 1,006 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.
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.
pimcore-expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.
modernization
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.
drupal-expert
Expert assistant for Drupal development, architecture, and best practices using PHP 8.3+ and modern Drupal patterns.