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-interactive-craftnpx skills add catlog22/Claude-Code-Workflow --skill team-interactive-craftgit 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-interactive-craft)<a href="https://agentmods.dev/skills/catlog22/claude-code-workflow/team-interactive-craft"><img src="https://agentmods.dev/badge/skills/catlog22/claude-code-workflow/team-interactive-craft.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 | $0.00054 | $0.01295 |
| Opus 5 | $0.00027 | $0.00647 |
| Sonnet 5 | $0.00011 | $0.00259 |
| Haiku 4.5 | $0.00005 | $0.00129 |
Grade A, and why
team-interactive-craft 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 yesterday.
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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Interactive Craft
Systematic interactive component pipeline: research -> interaction design -> build -> a11y test. Built on team-worker agent architecture -- all worker roles share a single agent definition with role-specific Phase 2-4 loaded from roles/<role>/role.md.
Architecture
Skill(skill="team-interactive-craft", args="task description")
|
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]
researcher interaction-designer builder a11y-tester
Role Registry
| Role | Path | Prefix | Inner Loop |
|---|---|---|---|
| coordinator | roles/coordinator/role.md | -- | -- |
| researcher | roles/researcher/role.md | RESEARCH-* | false |
| interaction-designer | roles/interaction-designer/role.md | INTERACT-* | false |
| builder | roles/builder/role.md | BUILD-* | true |
| a11y-tester | roles/a11y-tester/role.md | A11Y-* | 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:
IC - Session path:
.workflow/.team/IC-<slug>-<date>/ - CLI tools:
ccw cli --mode analysis(read-only),ccw cli --mode write(modifications) - Message bus:
mcp__ccw-tools__team_msg(session_id=<session-id>, ...) - Max GC rounds: 2
What ships with it
12 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/a11y-tester/role.md 6.7 KB
- roles/builder/role.md 8.0 KB
- roles/coordinator/commands/analyze.md 2.5 KB
- roles/coordinator/commands/dispatch.md 7.9 KB
- roles/coordinator/commands/monitor.md 7.0 KB
- roles/coordinator/role.md 6.9 KB
- roles/interaction-designer/role.md 6.4 KB
- roles/researcher/role.md 4.8 KB
- specs/interaction-patterns.md 11 KB
- specs/pipelines.md 3.8 KB
- specs/team-config.json 3.7 KB
- specs/vanilla-constraints.md 3.9 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.
- yesterday First seen · 134 lines · 54 tokens per session scan A d61eee52838e
team-interactive-craft is a skill published in the GitHub repository catlog22/Claude-Code-Workflow (2,133 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 1,295 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-09-03.
Other skills, from other repositories
core-components
Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.
accessibility
WCAG 2.2 レベル AA 標準を用いてインクルーシブなデジタルプロダクトを設計・実装・監査します。Web 用のセマンティック ARIA および Web・ネイティブプラットフォーム（iOS/Android）のアクセシビリティトレイトを生成するために使用します。.
build-webgl-liquid-glass
Build production-ready GPU liquid-glass surfaces with liquid-gl for React or DOM UIs. Default for refractive cards, notifications, panels, GPU bevels, and WebGL glass.
build-sdf-liquid-glass
Build lightweight SDF/canvas displacement glass with Vaso. Use for responsive refractive cards, no-WebGL fallbacks, many compact surfaces, or explicit SDF requests.
lov-oh-my-landingpage
从产品与品牌事实出发，独立推导适合当前产品的定位、叙事与视觉，并完成 Landing Page 实现、响应式和生产回读；适用于创建官网、品牌官网重构、产品价值不清或视觉与产品不匹配。.
ui-design-memory
Apply, review, and continuously evolve the OneWorks team's durable UI design standards. Use for any OneWorks task that changes or reviews layout, styling, theme, spacing, responsive behavior, component appearance, visual assets, or reference-image fidelity, and whenever user visual feedback may express a reusable team…