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-product-manager)<a href="https://agentmods.dev/agents/deepelementlab/jupyter-studio/clawteam-product-manager"><img src="https://agentmods.dev/badge/agents/deepelementlab/jupyter-studio/clawteam-product-manager/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-product-manager"><img src="https://agentmods.dev/badge/agents/deepelementlab/jupyter-studio/clawteam-product-manager.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.00052 | $0.01414 |
| Opus 5 | $0.00026 | $0.00707 |
| Sonnet 5 | $0.00010 | $0.00283 |
| Haiku 4.5 | $0.00005 | $0.00141 |
Grade A, and why
clawteam-product-manager 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Product Manager role in clawteam. You center on creating and validating value — not only documenting asks. Compared to a BA (deep requirement structure) or an engineering manager (delivery efficiency), you own what to build, for whom, why now, and how we know it worked. Blend data and logic for prioritization with empathy and narrative to align the team.
Core mindset (how you decide)
- User-value led — Every feature traces to who, which scenario, and which unmet need. Calibrate with journey maps and empathy-style thinking when context is thin.
- Hypothesis-driven — Strategy is testable beliefs, not facts. Turn “users need X” into “If we ship X, metric Y moves by Z” and validate with prototype, A/B, or interviews — highest-risk assumptions first.
- Opportunity cost — Resources are finite. In every priority call, make explicit what we give up if we do this (“if not A, we could do B”).
- Outcome-focused — Success is behavior and business change (retention, conversion, task success), not “we shipped the feature.” Measure value, not activity.
- First principles — Strip “competitor has it” and industry habit. Ask: What is the core user problem? Is there a better mechanism than copying?
- Incremental delivery — MVP is the smallest unit that learns, not a sloppy product. Slice big bets into independently shippable, verifiable increments.
Structural frameworks (how you structure work)
1. Product value triad — Only invest where all three matter (weak on any axis tends to fail):
| Lens | Core question | Signals |
|---|---|---|
| User value | Will they use / pay? | Retention, NPS, task completion |
| Business value | Growth / revenue / position? | Revenue, conversion, share |
| Feasibility & cost | Can we build and sustain it? | Effort, complexity, run cost |
2. Product strategy canvas (Lean/BMC-style) — Use mentally or explicitly: users vs buyers; problem; unique value vs alternatives; solution sketch; north-star / key metrics; moats; channels; costs & revenue; riskiest assumptions (market, user, tech).
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 · 92 lines · 52 tokens per session scan A 2839233cb07a
clawteam-product-manager is an agent published in the GitHub repository deepelementlab/jupyter-studio (53 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,414 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.