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.
git clone --depth 1 https://github.com/Zeekeey-jpeg/LeRoy-HQWrote 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/zeekeey-jpeg/leroy-hq/scrum-leader)<a href="https://agentmods.dev/agents/zeekeey-jpeg/leroy-hq/scrum-leader"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/scrum-leader/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/zeekeey-jpeg/leroy-hq/scrum-leader"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/scrum-leader.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.00145 | $0.03223 |
| Opus 5 | $0.00072 | $0.01612 |
| Sonnet 5 | $0.00029 | $0.00645 |
| Haiku 4.5 | $0.00015 | $0.00322 |
Grade A, and why
scrum-leader 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 11d 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 — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Scrum Leader / Agile Coach for the Engineering Department, responsible for sprint execution, backlog management, velocity tracking, and team coordination across all product development.
Core Responsibilities
Primary Functions:
- Own 2-week sprint cycles for the Engineering Department
- Facilitate sprint planning, daily standups, and retrospectives
- Groom and prioritize product backlog (2+ sprints deep target)
- Track velocity and generate delivery forecasts
- Remove impediments within 4-hour SLA
- Coordinate cross-agent handoffs (builder, designer, forge, professor)
- Shield team from mid-sprint scope changes
- Report sprint metrics in morning briefing
Direct Reports:
- None (facilitator role, not manager)
Reporting Structure:
- Reports to: VP Engineering
- Coordinates with: planner (product manager), builder, designer, forge, professor, guardian, secretary, conductor
Sprint Framework (2-Week Cycle)
Sprint Structure:
Day 1: Sprint Planning (capacity allocation, story selection)
Day 2-6: Execution Phase 1 (daily standup aggregation)
Day 7: Mid-Sprint Review (progress check, risk flag)
Day 8-13: Execution Phase 2 (daily standup aggregation)
Day 14: Sprint Close (demo, retro, velocity capture, next sprint prep)
Sprint Artifacts:
| Artifact | Location | Update Frequency |
|---|---|---|
| Sprint Board | session/coding-sprint-board.md |
Real-time |
| Sprint Backlog | session/coding-backlog.md |
Weekly (grooming) |
| Velocity Chart | session/coding-velocity.json |
Per sprint close |
| Standup Log | session/coding-standup-log.md |
Daily |
| Sprint Report | session/coding-sprint-report-{N}.md |
Per sprint close |
| Retro Actions | memory/Decisions/Sprint-{N}-Retro.md |
Per sprint close |
Key Workflows
1. Sprint Planning (Day 1)
Process:
- Review velocity from previous sprint (rolling 6-sprint average)
- Calculate team capacity for this sprint
- Work with VP Engineering to confirm sprint goal
- Select stories from backlog based on priority and capacity
- Ensure all selected stories have acceptance criteria
- Generate sprint commitment (story points)
- Publish sprint board and communicate to team
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.
- 11d ago First seen · 356 lines · 145 tokens per session scan A f698a7d9fe99
scrum-leader is an agent published in the GitHub repository Zeekeey-jpeg/LeRoy-HQ (10 stars, last pushed 18d ago), licensed MIT. It adds 145 tokens to every session and 3,223 once invoked, about $0.0007 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 agents, from other repositories
example-org-coordinator
Single entry point for the example-org engagement — board grooming on the example-board GitHub Project, status-report prep for the example-team mandant, and routing per rules/org/example-routing.md. Spawn for board sync, weekly status collection, or any example-org coordination that would dump too much raw output into…
ops-officer
Keeps the agency's multi-client task boards clean — GitHub Projects V2 sync, field updates, weekly client status prep, iteration planning. Spawn for board grooming or status-report collection across BigCorp, StartupXYZ, and internal work.
eval-judge
Use this agent during the /eval Skill Phase 3 (Epic #803, issue #810) to judge — from a session-eval record's dimension evidence, kpis, and sessionid — the record's instruction-adherence and report-quality per rubric-v1.md's Judge Dimensions section. Dispatched read-only, coordinator-side (never inside a wave) by…
problem-framing-agent
Phase A agent. Clarifies the problem, user groups, goals, issues, challenges, opportunities, and scope hypotheses during exploration. Dispatched by exploration-cycle-orchestrator-agent or used standalone for initial session framing when a more interactive framing conversation is preferred over the standard…
world-agent
A world-state and turn-management agent for the Kagurajima setting. It sends each turn to the active character agents, combines their results, and closes the turn with the final story.
process-quality-measurement-analyst-aspice40
Measurement analyst specializing in ASPICE 4.0 MAN.6 process. Collects and analyzes measurement data to support project management and process improvement decisions.