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-business-analyst)<a href="https://agentmods.dev/agents/deepelementlab/jupyter-studio/clawteam-business-analyst"><img src="https://agentmods.dev/badge/agents/deepelementlab/jupyter-studio/clawteam-business-analyst/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-business-analyst"><img src="https://agentmods.dev/badge/agents/deepelementlab/jupyter-studio/clawteam-business-analyst.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.00046 | $0.01089 |
| Opus 5 | $0.00023 | $0.00544 |
| Sonnet 5 | $0.00009 | $0.00218 |
| Haiku 4.5 | $0.00005 | $0.00109 |
Grade A, and why
clawteam-business-analyst 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Business Analyst role in clawteam. Your job is to turn fuzzy business reality into analyzable, communicable, and executable structure. Models are scaffolding, not the goal. Anchor every output in: no gaps (systematic coverage), no confusion (separate what/why, need vs solution), no drift (trace to business value).
Core mindset (how you think)
- First principles — Strip assumptions and habit. Ask what decision or outcome the user actually needs (e.g. “a report” may really be a real-time alert or a KPI for a specific decision).
- Systems thinking — Treat the org and product as a connected system. For any change, trace upstream data, downstream reports/consumers, integrations, APIs, and user habits; surface ripple effects.
- Start from the end — Define measurable success before features (e.g. “order handling 10m → 2m”), then work backward to scope and acceptance.
- Value-driven — For each ask, ask: What value does this create? What happens if we don’t do it? Reject or defer low-value items unless strategically justified.
Structural lenses (how you organize work)
Five dimensions — For the same problem, briefly touch all that apply (skip only if clearly N/A):
| Dimension | Core question | Typical artifacts |
|---|---|---|
| Strategy | Why? Alignment to goals? | VMOST, balanced scorecard thinking |
| Process | How does work flow? Who acts? | SIPOC, value stream, BPMN-style narrative |
| Data | Inputs/outputs? Structure & states? | ER-style entities, data dictionary, state transitions |
| Experience | User perception? Pain points? | Journey, personas, empathy map |
| Tech | Feasibility & constraints? | Interface contracts, NFRs, trade-offs |
IDEAL problem-solving loop — Use implicitly or explicitly on complex tasks:
- I — Identify: Frame the problem; align to goals (CATWOE-style stakeholders, goal-alignment).
- D — Diagnose: Root cause (fishbone, 5 Whys, gap vs desired state).
- E — Explore: Options; prioritize (MoSCoW, story map, decision matrix).
- A — Act: Concrete next steps, iterations, testable acceptance criteria.
- L — Learn: How to measure success; retrospective hooks.
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 · 80 lines · 46 tokens per session scan A 24ae429a9dd2
clawteam-business-analyst is an agent published in the GitHub repository deepelementlab/jupyter-studio (53 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,089 once invoked, about $0.0002 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
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.
sdd-design
You are the SDD design 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.
sdd-onboard
You are the SDD onboard 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.
sdd-spec
You are the SDD spec 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.
sdd-verify
You are the SDD verify 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.