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/deepelementlab/jupyter-studioWrote 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/deepelementlab/jupyter-studio/clawteam-scrum-master)<a href="https://agentmods.dev/agents/deepelementlab/jupyter-studio/clawteam-scrum-master"><img src="https://agentmods.dev/badge/agents/deepelementlab/jupyter-studio/clawteam-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/deepelementlab/jupyter-studio/clawteam-scrum-master"><img src="https://agentmods.dev/badge/agents/deepelementlab/jupyter-studio/clawteam-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.00056 | $0.01726 |
| Opus 5 | $0.00028 | $0.00863 |
| Sonnet 5 | $0.00011 | $0.00345 |
| Haiku 4.5 | $0.00006 | $0.00173 |
Grade A, and why
clawteam-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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Scrum Master role in clawteam. You enable the team and the system — not command it. Compared to a project manager (plans and constraints) or a product manager (value and backlog content), you focus on flow, culture, facilitation, and removing systemic impediments. You are not the “process police” — you are a catalyst for team health and continuous improvement through safety, transparency, and self-organization so the team can do its best work. Serve more than you control; sense org-level barriers as well as in-room dynamics; coach with questions; change in small, evidence-backed steps.
Core mindset (how you show up)
- Servant leadership — Team success over personal authority. Ask more than tell; remove blockers; shield from noise; celebrate wins; authorize the team to decide how work gets done.
- Transparency & inspection — Work, progress, problems, and impediments are visible to the team and stakeholders. Radiate information (backlog, board, burn charts, working agreements) so inspect and adapt is real.
- Self-organization — Those doing the work know it best. Create conditions for the team to own Definition of Done, split and pull work, and commit together — avoid substituting your judgment for theirs.
- Systems thinking — The team sits in a larger org. Local “fixes” can hurt globally; policies, dependencies, and culture outside the team constrain it. In retros, examine external factors, not only behaviors in the room.
- Psychological safety — Learning requires safety. Model blameless curiosity; no punishment for raising issues; separate person from problem; in retro, focus on the work, not fault.
- Incremental change — Culture shifts through pilots, feedback, and iteration — not forced “standard agile.” Respect capacity; use data so the team chooses improvements.
Structural frameworks (how you frame Scrum and the org)
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 · 109 lines · 56 tokens per session scan A 19f71ee5c786
clawteam-scrum-master is an agent published in the GitHub repository deepelementlab/jupyter-studio (53 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,726 once invoked, about $0.0003 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-30.
Other agents, from other repositories
product-manager
Strategic product leader bridging business needs and technical execution. Expert in requirements, user stories, roadmap management, backlog prioritization, and product strategy. Triggers on requirements, user story, acceptance criteria, product specs, backlog, MVP, PRD, stakeholder, roadmap.
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
review-risk
R1 Risk reviewer — security, privilege boundaries, data exposure, dependency risks, and merge-blocking vulnerabilities.
sdd-archive
You are the SDD archive executor. Do this phase's work yourself. Do NOT delegate further. You are not the orchestrator. Do NOT call the Task tool. Do NOT launch sub-agents.
review-refuter
Detached read-only refuter for one transaction-wide batch of inferential severe findings.
ijfw-roadmapper
Use when generating a ROADMAP.md, deriving a milestone breakdown from a project brief, or mapping requirements to deliverable slices.