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 Omar-Obando/qwen-orchestrator --skill scrum-mastergit clone --depth 1 https://github.com/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/scrum-master)<a href="https://agentmods.dev/skills/omar-obando/qwen-orchestrator/scrum-master"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/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/omar-obando/qwen-orchestrator/scrum-master"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/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.00040 | $0.02383 |
| Opus 5 | $0.00020 | $0.01192 |
| Sonnet 5 | $0.00008 | $0.00477 |
| Haiku 4.5 | $0.00004 | $0.00238 |
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 — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scrum Master Skill — Agile Team Facilitation
Overview
This skill provides comprehensive guidance for Scrum Masters in facilitating Agile ceremonies, coaching teams, removing impediments, and promoting Scrum practices. It covers sprint planning, daily standups, sprint reviews, retrospectives, and team dynamics.
When to Use
Use this skill when:
- Facilitating sprint planning meetings
- Conducting daily standups
- Leading sprint reviews and demos
- Facilitating sprint retrospectives
- Coaching team on Agile practices
- Removing team impediments
- Protecting team from distractions
- Improving team dynamics
Do NOT use this skill when:
- Writing user stories (Product Owner)
- Writing code implementation (Developer)
- Managing project budget (Project Manager)
Agile Ceremonies
Sprint Planning
Duration: 2-4 hours (depending on sprint length)
Attendees: Team, Product Owner, Scrum Master
Objective: Select backlog items and create sprint goal
┌─────────────────────────────────────────────────────────────┐
│ Sprint Planning │
├─────────────────────────────────────────────────────────────┤
│ 1. Sprint Goal Definition (15 min) │
│ 2. Story Selection (30 min) │
│ 3. Task Breakdown (30 min) │
│ 4. Commitment & Capacity (15 min) │
└─────────────────────────────────────────────────────────────┘
Daily Standup
Duration: 15 minutes (daily)
Attendees: Development team, Scrum Master (optional)
Objective: Sync team, identify blockers
Format:
- What did you do yesterday?
- What will you do today?
- Any blockers?
Rules:
- Stand up (physically or virtually)
- Timebox: 15 minutes max
- Focus on team, not individual
- Detailed discussions after meeting
Sprint Review
Duration: 1-2 hours (depending on sprint length)
Attendees: Team, Product Owner, Stakeholders, Scrum Master
What ships with it
1 file 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 · 374 lines · 40 tokens per session scan A 6f32621e4532
scrum-master is a skill published in the GitHub repository Omar-Obando/qwen-orchestrator (49 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 2,383 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-09-03.
Other skills, from other repositories
loopx-project
Use when connecting a repository or project goal document to LoopX, maintaining project-local goal state, refreshing stale dashboard status, syncing local projects into the shared global registry, or diagnosing LoopX CLI/PATH/status/history issues across multiple repos. For registering durable project materials such…
pm
Generate a PM through guided PM-focused interview with automatic question classification. Use when the user says 'ooo pm', 'prd', 'product requirements', or wants to create a PRD/PM document.
publish
Publish Seed specification as GitHub Issues for team-based project management.
loopx-material
Operate an explicitly activated LoopX Material Lifecycle for a connected project. Use for material-store inventory, lossless migration, candidate/archive transitions, exact-read-backed ranking, ranked-entry rebuilds, bounded Explore intake, owner-gated apply, rollback, and audit. Do not use for ordinary one-off…
loopx-pr-program
Use when LoopX must manage a multi-PR or multi-MR delivery program across one or more repositories: inventory current change requests, reconcile new/merged/closed or retargeted work, preserve requirement and dependency priorities, maintain a roadmap document, or monitor material lifecycle/check/review changes over…
loopx-manager
Inspect authorized LoopX Goals, Todos and deliveries to explain progress, identify owner decisions and delegate intent to the right worker.