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 skills add catlog22/Claude-Code-Workflow --skill team-frontendgit 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-frontend)<a href="https://agentmods.dev/skills/catlog22/claude-code-workflow/team-frontend"><img src="https://agentmods.dev/badge/skills/catlog22/claude-code-workflow/team-frontend/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/skills/catlog22/claude-code-workflow/team-frontend"><img src="https://agentmods.dev/badge/skills/catlog22/claude-code-workflow/team-frontend.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.01208 |
| Opus 5.5 | $0.00018 | $0.00483 |
| Sonnet 5.5 | $0.00009 | $0.00242 |
| Haiku 4.5 | $0.00005 | $0.00121 |
Grade A, and why
team-frontend 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 1mo 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Frontend Development
Unified team skill: frontend development with built-in ui-ux-pro-max design intelligence. Covers requirement analysis, design system generation, frontend implementation, and quality assurance. Built on team-worker agent architecture — all worker roles share a single agent definition with role-specific Phase 2-4 loaded from role.md specs.
Architecture
Skill(skill="team-frontend", 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
[analyst] [architect] [developer] [qa]
(team-worker agents, each loads roles/<role>/role.md)
Role Registry
| Role | Path | Prefix | Inner Loop |
|---|---|---|---|
| coordinator | roles/coordinator/role.md | — | — |
| analyst | roles/analyst/role.md | ANALYZE-* | false |
| architect | roles/architect/role.md | ARCH-* | false |
| developer | roles/developer/role.md | DEV-* | true |
| qa | roles/qa/role.md | QA-* | 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:
FE - Session path:
.workflow/.team/FE-<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>, ...)
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.6 KB
- roles/architect/role.md 3.3 KB
- roles/coordinator/commands/analyze.md 1.6 KB
- roles/coordinator/commands/dispatch.md 6.6 KB
- roles/coordinator/commands/monitor.md 7.0 KB
- roles/coordinator/role.md 5.7 KB
- roles/developer/role.md 3.3 KB
- roles/qa/role.md 3.4 KB
- specs/pipelines.md 2.7 KB
- specs/team-config.json 3.3 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.
- 1mo ago First seen · 129 lines · 46 tokens per session scan A 1fc63959f47e
team-frontend is a skill published in the GitHub repository catlog22/Claude-Code-Workflow (2,124 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 1,208 once invoked, about $0.0002 per session on Opus 5.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
a11y-audit
Run a Maestro-style accessibility audit for WCAG compliance, ARIA usage, keyboard navigation, and screen reader compatibility.
lov-maintain-partners
Maintain the Skill Publisher website's partners section AND align partner logo rows on event posters / hero strips: reuse lov-find-logo for brand logo discovery, normalize collected logos to a 240px-tall content canvas (retina-ready), rasterize SVGs via rsvg-convert before normalizing (so SVG viewBox padding gets…
lov-oh-my-landingpage
A landing-page creation and redesign skill that derives a product’s positioning, story, and visual direction from its actual product and brand facts. It then implements the page responsively and checks the result against the intended product message.
lov-frontend-design
A frontend design guide for turning requirements, existing screens, and real media into usable pages and components. It covers visual design, navigation, interaction details, animation, images, audio, and video.
lov-install-shadcn-ui
A setup tool for shadcn/ui, a collection of editable interface components for web projects. It installs only needed pieces and adapts their styles to the project’s existing theme and Tailwind version.
lov-install-web-logo
A website branding tool that connects an approved logo to browser icons, the web app manifest, page metadata, and related components. A favicon is the small icon shown in a browser tab; a PWA manifest describes an installable web app.