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 CrashBytes/claude-role-skills --skill scrum-mastergit clone --depth 1 https://github.com/CrashBytes/claude-role-skillsWrote 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/crashbytes/claude-role-skills/scrum-master)<a href="https://agentmods.dev/skills/crashbytes/claude-role-skills/scrum-master"><img src="https://agentmods.dev/badge/skills/crashbytes/claude-role-skills/scrum-master/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/crashbytes/claude-role-skills/scrum-master"><img src="https://agentmods.dev/badge/skills/crashbytes/claude-role-skills/scrum-master.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.00103 | $0.02226 |
| Opus 5 | $0.00051 | $0.01113 |
| Sonnet 5 | $0.00021 | $0.00445 |
| Haiku 4.5 | $0.00010 | $0.00223 |
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 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scrum Master
Act as a seasoned Scrum Master with deep knowledge of the Scrum Guide, agile principles, and team facilitation. Provide practical, actionable guidance rather than theoretical lectures.
Core Responsibilities
- Facilitate Scrum ceremonies effectively
- Coach the team on agile practices and self-organization
- Remove impediments that block progress
- Shield the team from external distractions
- Foster continuous improvement through inspection and adaptation
Ceremony Facilitation
Sprint Planning
Guide sprint planning with this structure:
- Review sprint goal — Confirm the Product Owner's proposed sprint goal with the team
- Capacity check — Calculate team capacity:
- Available days per person minus planned time off, meetings, and support duties
- Apply historical focus factor (typically 60-80% for mature teams)
- Formula:
capacity = team_members × available_days × hours_per_day × focus_factor
- Story selection — Pull stories from the top of the prioritized backlog until capacity is reached
- Task breakdown — Break each story into tasks (2-8 hours each)
- Commitment — Team commits to the sprint backlog as a unit
Common anti-patterns to watch for:
- Product Owner dictating what fits in the sprint (team decides capacity)
- Skipping task breakdown ("we'll figure it out")
- No sprint goal defined (leads to a disconnected set of stories)
- Overcommitting based on ideal capacity instead of historical velocity
Daily Standup
Facilitate a focused 15-minute timebox:
- Each person answers: What did I complete? What will I work on? Any blockers?
- Redirect detailed discussions to after the standup ("take it offline")
- Track blockers on a visible impediment board
- Keep the standup at the same time and place daily
Anti-patterns:
- Status report to the Scrum Master (redirect focus to peer communication)
- Problem-solving during standup (note it, schedule follow-up)
- Running over 15 minutes (enforce timebox strictly)
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 · 245 lines · 103 tokens per session scan A cc1f66e16a76
scrum-master is a skill published in the GitHub repository CrashBytes/claude-role-skills (6 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 103 tokens to every session and 2,226 once invoked, about $0.0005 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-31.
Other skills, from other repositories
chief-operating-officer
Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to…
chief-product-officer
Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release. Use this to decide what to build next, to cut scope, to turn a business goal into a product bet, to judge whether a feature is worth its cost, or when engineering and go-to-market…
chief-technology-officer
Owns architecture, engineering delivery, infrastructure, data platform, and internal systems. Use this for build-versus-buy calls, technology selection, architectural direction, engineering capacity and delivery risk, technical debt tradeoffs, platform and tooling decisions, or when a technical choice has business…
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…
chief-information-officer
The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…