css-noop-checker: Skill for Claude Code

.claude/skills/team-dev/SKILL.md

team-dev is a skill for Claude Code from purupurupu/css-noop-checker. It costs 27 tokens per session (4,004 once invoked), scanned A, original, MIT.

A team-development workflow that coordinates implementation with repeated reviews from an architect, frontend lead, critic, and code reviewer.

In plain words
What is it for?
Use it to implement a feature, run three review-and-fix rounds, complete a final review, and clean up the temporary team.
Why use it?
It gives a feature several rounds of independent feedback and fixes, helping uncover design, usability, and code-quality problems before completion.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md.

This is purupurupu/css-noop-checker's own configuration. It tells Claude Code how to work on css-noop-checker itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything css-noop-checker configures →

Reuse

Borrowing it

Nothing to install: this file belongs to purupurupu/css-noop-checker. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/purupurupu/css-noop-checker/main/.claude/skills/team-dev/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/purupurupu/css-noop-checker

Made for: Claude Code.

Wrote 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.

agentmods badge for team-dev

README.md
[![agentmods](https://agentmods.dev/badge/skills/purupurupu/css-noop-checker/team-dev.svg)](https://agentmods.dev/skills/purupurupu/css-noop-checker/team-dev)
Your own site
<a href="https://agentmods.dev/skills/purupurupu/css-noop-checker/team-dev"><img src="https://agentmods.dev/badge/skills/purupurupu/css-noop-checker/team-dev.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,004 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.04004
Opus 5 $0.00014 $0.02002
Sonnet 5 $0.00005 $0.00801
Haiku 4.5 $0.00003 $0.00400

Measured 8d ago against content hash 358c7ab75445, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

team-dev 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 8d 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.

.claude/skills/team-dev/SKILL.md · 446 lines

How it starts

The opening of the file, as written. The whole thing — 446 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the Team Orchestrator (team-lead) for css-noop-checker feature development. You manage a persistent team of 5 specialists using TeamCreate, SendMessage, and task management tools.


Phase 0 — Team Setup

  1. Create the team:

    TeamCreate(team_name: "team-dev")
    
  2. Create tasks with TaskCreate for the full workflow (9 tasks):

    # Subject Description
    1 Initial implementation Implement the feature per the spec
    2 Review round 1 All 4 reviewers review the implementation
    3 Fix round 1 Implementer addresses round 1 feedback
    4 Review round 2 All 4 reviewers review fixes from round 1
    5 Fix round 2 Implementer addresses round 2 feedback
    6 Review round 3 All 4 reviewers review fixes from round 2
    7 Fix round 3 Implementer addresses round 3 feedback
    8 Final review All 4 reviewers give PASS/CONDITIONAL PASS/FAIL verdict
    9 Cleanup Shutdown all members and delete team

    Set up dependencies: task 2 blocked by 1, task 3 blocked by 2, etc.

  3. Spawn all 5 team members in parallel using Task with team_name and name:

    # Member 1 — Implementer
    Task(
      subagent_type: "general-purpose",
      model: "opus",
      team_name: "team-dev",
      name: "implementer",
      description: "Feature implementer",
      prompt: <implementer system prompt below>
    )
    
    # Member 2 — Architect
    Task(
      subagent_type: "general-purpose",
      model: "opus",
      team_name: "team-dev",
      name: "architect",
      description: "Architecture reviewer",
      prompt: <architect system prompt below>
    )
    
    # Member 3 — Frontend Lead
    Task(
      subagent_type: "general-purpose",
      model: "sonnet",
      team_name: "team-dev",
      name: "frontend-lead",
      description: "Frontend/UI reviewer",
      prompt: <frontend-lead system prompt below>
    )
    
    # Member 4 — Devil's Advocate
    Task(
      subagent_type: "general-purpose",
      model: "sonnet",
      team_name: "team-dev",
      name: "devils-advocate",
      description: "Edge case and flaw finder",
      prompt: <devils-advocate system prompt below>
    )
    
    # Member 5 — Code Reviewer
    Task(
      subagent_type: "general-purpose",
      model: "sonnet",
      team_name: "team-dev",
      name: "code-reviewer",
      description: "Convention and best-practices reviewer",
      prompt: <code-reviewer system prompt below>
    )
    

Read the full file on GitHub · 446 lines

Changes

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.

  1. 8d ago First seen · 446 lines · 27 tokens per session scan A 358c7ab75445

Subscribe to this mod's changes

team-dev is a skill published in the GitHub repository purupurupu/css-noop-checker (24 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 4,004 once invoked, about $0.0001 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.