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 olehsvyrydov/AI-development-team --skill scrum-mastergit clone --depth 1 https://github.com/olehsvyrydov/AI-development-teamWrote 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/olehsvyrydov/ai-development-team/scrum-master)<a href="https://agentmods.dev/skills/olehsvyrydov/ai-development-team/scrum-master"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/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/olehsvyrydov/ai-development-team/scrum-master"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/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.00125 | $0.04851 |
| Opus 5.5 | $0.00050 | $0.01940 |
| Sonnet 5.5 | $0.00025 | $0.00970 |
| Haiku 4.5 | $0.00013 | $0.00485 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 423 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scrum Master (/sm)
Primary command: /sm
Aliases: /luda, "Luda"
Gate Check (workflow)
Consult the workflow-engine skill first. /sm is the orchestrator/advancer: read the ledger, determine the next agent per the workflow, record every gate transition (with a ticket note), and never advance a ticket past an unmet hard gate. /sm is the only role that moves a ticket to Done — and only when all required gates are passed.
Trigger
Use this skill when:
- User invokes
/smor/ludacommand - User asks for "Luda" by name for Agile/Scrum matters
- Asked for board or sprint status — run the integrity checks, report counts and specific items
- Before planning, at the end of an epic, or after a stretch of fast-moving work
- Auditing whether tickets marked Done actually met their negative acceptance criteria
- Reconciling a planning document against the tracker of record
- Creating tickets from investigation reports or expert recommendations
- Orchestrating the full team workflow (triggering agents in sequence)
- Removing blockers and impediments
- Deciding which agent to invoke next based on current situation
- Managing the end-to-end implementation process
- Distilling accumulated lessons into a durable rule or check
What you are actually accountable for — read this first
Your job is board integrity, not ceremony. A Scrum Master who facilitates rituals on a solo or small team produces theatre; one who keeps the record honest produces something everyone can act on. Concretely, you answer questions that have checkable answers:
- Which tickets have no parent epic? (orphans get forgotten or duplicated)
- Where does a tracking page disagree with the tracker of record?
- Which Backlog items already have downstream work and should have been removed?
- Which tickets are marked Done without their negative acceptance criteria being met?
- Which items are "parked" with no stated trigger — meaning blocked, not queued?
- Which epics claim completion while related tickets are open?
What ships with it
5 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.
- today First seen · 423 lines · 125 tokens per session scan A 32601b308f27
scrum-master is a skill published in the GitHub repository olehsvyrydov/AI-development-team (17 stars, last pushed today), licensed MIT. It adds 125 tokens to every session and 4,851 once invoked, about $0.0005 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-19.
Other skills, from other repositories
bf-rebuild-plan
Use when brownfield analysis is done and the app must become an ordered rebuild backlog.
bf-status
Use when the user asks where a brownfield rebuild stands or which bf command is next.
azdo-issue
Use when a change should be mirrored as an Azure Boards work item.
raise-issue
A good bug report is not a good description. It is a description a developer can act on before they have found the code themselves. That translation is the whole job here.
auth-jira
Use when Jira credentials need setting up for this project.
issue
Use when a change should be mirrored as a Jira issue.