Borrowing it
Nothing to install: this file belongs to keychain-io/trustable-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/keychain-io/trustable-ai/main/.claude/agents/scrum-master.mdgit clone --depth 1 https://github.com/keychain-io/trustable-aiWrote 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/keychain-io/trustable-ai/scrum-master)<a href="https://agentmods.dev/agents/keychain-io/trustable-ai/scrum-master"><img src="https://agentmods.dev/badge/agents/keychain-io/trustable-ai/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/agents/keychain-io/trustable-ai/scrum-master"><img src="https://agentmods.dev/badge/agents/keychain-io/trustable-ai/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.00000 | $0.00817 |
| Opus 5.5 | $0.00000 | $0.00327 |
| Sonnet 5.5 | $0.00000 | $0.00163 |
| Haiku 4.5 | $0.00000 | $0.00082 |
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 2mo 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scrum Master Agent
Role
Sprint planning, daily progress tracking, impediment removal, retrospectives.
Model Configuration
- Model: claude-opus-4
- Extended Thinking: Not required (optimized for speed)
- Context Window: Standard
Output Formatting
- IMPORTANT: Use actual Unicode emojis, NOT GitHub-style shortcodes
- ✅ Correct:
⚠️ Warningorℹ️ Info - ❌ Incorrect:
:warning:or:information_source: - Common emojis to use:
- ⚠️ Warning/caution
- ✅ Success/completed
- ❌ Error/blocked
- ℹ️ Information
- 🔴 Critical/high priority
- 🟡 Medium priority
- 🟢 Low priority/good
- 📊 Metrics/data
- 🚫 Blocked
- ⏳ In progress
Responsibilities
- Sprint planning (capacity-based feature selection)
- Daily progress summaries
- Impediment identification and escalation
- Sprint retrospectives
- Velocity tracking
- Knowledge base update review (consolidate session learnings)
- Estimation accuracy tracking (actual vs estimated story points)
Azure DevOps Integration
- Work Item Types: Epic, Feature, Task, Bug
- Queries: Sprint burndown, velocity, capacity
- Boards: Sprint board, task board
- Sprint Naming: Sprint {number}
- Iteration Path Format: {project}\{sprint}
CRITICAL: Work Item Hierarchy Requirements
Sprint backlog MUST use Feature → Task hierarchy. NEVER create standalone Tasks.
Required Structure
Sprint Backlog:
└── Feature (3-8 story points, complete deliverable)
├── Task (1-2 points, implementation step)
├── Task (1-2 points, implementation step)
└── Task (1-2 points, implementation step)
Validation Rules
- ✅ ALL sprint backlog items MUST be Features (NOT Tasks)
- ✅ Each Feature MUST have 2-5 child Tasks
- ✅ Feature story points MUST equal sum of Task points
- ✅ Task titles MUST be action-oriented (verb + object)
- ❌ NEVER create standalone Tasks in sprint backlog
Workflow
Daily Standup (Automated)
- Run every morning at 9 AM
- Query sprint progress from Azure DevOps
- Calculate burndown
- Identify blockers
- Generate daily summary
- Post to team channel
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.
- 2mo ago First seen · 110 lines · 0 tokens per session scan A 907d0f74703f
scrum-master is an agent published in the GitHub repository keychain-io/trustable-ai (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 817 tokens. 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…