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.
npx agentmods add skills/catlog22/claude-code-workflow/team-ultra-analyzenpx skills add catlog22/Claude-Code-Workflow --skill team-ultra-analyzegit clone --depth 1 https://github.com/catlog22/Claude-Code-WorkflowWrote 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/skills/catlog22/claude-code-workflow/team-ultra-analyze)<a href="https://agentmods.dev/skills/catlog22/claude-code-workflow/team-ultra-analyze"><img src="https://agentmods.dev/badge/skills/catlog22/claude-code-workflow/team-ultra-analyze.svg" alt="Measured on agentmods" 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.00033 | $0.01524 |
| Opus 5 | $0.00016 | $0.00762 |
| Sonnet 5 | $0.00007 | $0.00305 |
| Haiku 4.5 | $0.00003 | $0.00152 |
Grade A, and why
team-ultra-analyze 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 2d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Ultra Analyze
Deep collaborative analysis: explore -> analyze -> discuss -> synthesize. Supports Quick/Standard/Deep pipeline modes with configurable depth (N parallel agents). Discussion loops enable user-guided progressive understanding.
Architecture
Skill(skill="team-ultra-analyze", args="<topic>")
|
SKILL.md (this file) = Router
|
+--------------+--------------+
| |
no --role flag --role <name>
| |
Coordinator Worker
roles/coordinator/role.md roles/<name>/role.md
|
+-- analyze -> dispatch -> spawn workers -> STOP
|
+-------+-------+-------+-------+
v v v v
[team-worker agents, each loads roles/<role>/role.md]
Pipeline (Standard mode):
[EXPLORE-1..N](parallel) -> [ANALYZE-1..N](parallel) -> DISCUSS-001 -> SYNTH-001
Pipeline (Deep mode):
[EXPLORE-1..N] -> [ANALYZE-1..N] -> DISCUSS-001 -> ANALYZE-fix -> DISCUSS-002 -> ... -> SYNTH-001
Pipeline (Quick mode):
EXPLORE-001 -> ANALYZE-001 -> SYNTH-001
Role Registry
| Role | Path | Prefix | Inner Loop |
|---|---|---|---|
| coordinator | roles/coordinator/role.md | — | — |
| explorer | roles/explorer/role.md | EXPLORE-* | false |
| analyst | roles/analyst/role.md | ANALYZE-* | false |
| discussant | roles/discussant/role.md | DISCUSS-* | false |
| synthesizer | roles/synthesizer/role.md | SYNTH-* | false |
Role Router
Parse $ARGUMENTS:
- Has
--role <name>→ Readroles/<name>/role.md, execute Phase 2-4 - No
--role→@roles/coordinator/role.md, execute entry router
Shared Constants
- Session prefix:
UAN - Session path:
.workflow/.team/UAN-<slug>-<date>/ - Team name:
ultra-analyze - CLI tools:
ccw cli --mode analysis(read-only),ccw cli --mode write(modifications) - Message bus:
mcp__ccw-tools__team_msg(session_id=<session-id>, ...)
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- roles/analyst/role.md 3.5 KB
- roles/coordinator/commands/analyze.md 2.1 KB
- roles/coordinator/commands/dispatch.md 9.1 KB
- roles/coordinator/commands/monitor.md 13 KB
- roles/coordinator/role.md 9.2 KB
- roles/discussant/role.md 3.9 KB
- roles/explorer/role.md 3.1 KB
- roles/synthesizer/role.md 3.1 KB
- specs/pipelines.md 2.3 KB
- specs/team-config.json 5.7 KB
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.
- 2d ago First seen · 167 lines · 33 tokens per session scan A 72f965bd8336
team-ultra-analyze is a skill published in the GitHub repository catlog22/Claude-Code-Workflow (2,132 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 1,524 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-09-03.
Other skills, from other repositories
audit
Audit local Claude Code transcript usage and summarize likely token hotspots. Use when the user asks where Claude Code tokens are going or wants evidence before optimizing.
optimize
Diagnose and reduce Claude Code token usage for a project or session using context hygiene, model and effort routing, MCP minimization, output trimming/sanitizing, subagent discipline, and measurement. Use when the user asks to lower Claude Code token usage, cost, context bloat, or usage-limit burn.
setup
Interactive or guided project setup for Claude Code token optimizer settings. Use when the user asks to install, configure, setup, enable hooks, or choose token-saving options interactively.
spawn-agent
Spawn worker agents (Gemini CLI or Codex CLI) to keep main context clean. Use for implementation, codebase research, context gathering, or any scoped work that would pollute the orchestrator's context.
skill-dispatcher
Universal MCP skill dispatcher for AI coding agents. Loads Claude Code, OpenCode, Cursor, Gemini-style, command, plain markdown, and GitHub-hosted skills on demand. Includes agent routing, active skill lifecycle tracking, external repo import, nested skill discovery, origin filtering, and hardened parsing for secure…
newsroom-style
Apply AP Style and common newsroom conventions when writing or editing news articles, briefs, and headlines. Use when drafting publishable copy, editing contributor submissions, or converting informal notes into news-ready language.