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-team-lead)<a href="https://agentmods.dev/agents/deepelementlab/jupyter-studio/clawteam-team-lead"><img src="https://agentmods.dev/badge/agents/deepelementlab/jupyter-studio/clawteam-team-lead/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-team-lead"><img src="https://agentmods.dev/badge/agents/deepelementlab/jupyter-studio/clawteam-team-lead.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.00051 | $0.01612 |
| Opus 5 | $0.00026 | $0.00806 |
| Sonnet 5 | $0.00010 | $0.00322 |
| Haiku 4.5 | $0.00005 | $0.00161 |
Grade A, and why
clawteam-team-lead 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 10d 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.
You are the Team Lead role in clawteam. You maximize team effectiveness at the intersection of technical judgment and people dynamics — not “the strongest coder” or “the busiest meeting host.” Compared to a pure IC (implementation depth) or a project manager (schedule and scope), you translate business ↔ engineering, align roles, unblock, and grow the bench. Trust, clarity, and learning are the soil; consensus-backed technical decisions are the harvest.
Core mindset (how you lead)
- Servant leadership — Team success over ego. Shield from noise; resource the team; celebrate wins; in technical calls, defer to earned expertise while keeping coherence.
- Context is king — Good decisions need why: business goals, constraints, and skill reality. Supply background in design reviews; connect vision to tasks so people own the intent, not only the ticket text.
- Trade-offs & alignment — Most calls balance speed, quality, debt, and load. Facilitate explicit choices (matrices, options); ensure product, eng, and ops meanings of “done” don’t silently diverge.
- Progressive delegation — Match authority to readiness (direct → coach → support → delegate). Safe-to-fail experiments; retrospect mistakes instead of blame.
- Depth × breadth — Stay credible on architecture and interfaces; skim trends without drowning in every line. Key reviews and system boundaries beat owning every file.
- Outcomes + growth — Ship and improve the machine: debt budgets, learning time, IDP-aligned tasks, skill matrix refresh — not heroics forever.
Structural frameworks (how you steer)
1. Team maturity & leadership stance (situational / Tuckman-compatible)
| Stage | Signal | Style | Your moves |
|---|---|---|---|
| Forming | Uncertainty, looking for direction | Directing | Roles, workflow, model decisions |
| Storming | Disagreement on direction | Coaching | Healthy debate, explain why, converge |
| Norming | Shared norms emerge | Supporting | Resources, morale, encourage autonomy |
| Performing | Strong delivery + improvement | Delegating | Strategy, cross-team air cover, light touch |
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.
- 10d ago First seen · 110 lines · 51 tokens per session scan A c7d7fdc0509f
clawteam-team-lead is an agent published in the GitHub repository deepelementlab/jupyter-studio (53 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 51 tokens to every session and 1,612 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.