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 unrealandychan/clean-code-skill --skill dev-teamgit clone --depth 1 https://github.com/unrealandychan/clean-code-skillWrote 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/unrealandychan/clean-code-skill/dev-team)<a href="https://agentmods.dev/skills/unrealandychan/clean-code-skill/dev-team"><img src="https://agentmods.dev/badge/skills/unrealandychan/clean-code-skill/dev-team/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/unrealandychan/clean-code-skill/dev-team"><img src="https://agentmods.dev/badge/skills/unrealandychan/clean-code-skill/dev-team.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.00060 | $0.01876 |
| Opus 5.5 | $0.00024 | $0.00750 |
| Sonnet 5.5 | $0.00012 | $0.00375 |
| Haiku 4.5 | $0.00006 | $0.00188 |
Grade A, and why
dev-team 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- dev-team — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Team
Run a multi-persona session where PM, Architect, Developer, and QA each respond from their own perspective in a single turn.
This is the preset four-lens review for collaborative design and planning. It is not
adversarial challenge (council), and it is not a free-form team composer
(team-builder selects arbitrary agents; dev-team always runs the same four roles).
When to Activate
The user provides a topic — a feature description, proposal, story, or question. The skill runs all four personas in parallel as independent subagents, then presents their responses together.
Use when:
- Designing a new feature and wanting PM, Architect, Dev, and QA concerns surfaced at once
- Reviewing a proposal before committing to implementation
- Onboarding an initiative and wanting each role to define their first concerns
- User says "what would the team think about this", "give me all perspectives", or "run this by the team"
- Starting a story and wanting role-specific input before writing a single line of code
When NOT to Use
| Condition | Use Instead |
|---|---|
| Ambiguous go/no-go decision with real tradeoffs | council |
| You want to hand-pick which agents participate | team-builder |
| Single-role deep-dive (e.g. architecture only) | the architect agent |
| Code review | the code-reviewer agent or /code-review |
| Structured adversarial challenge | santa-method |
Personas
| Role | Name | Lens |
|---|---|---|
| Product Manager | PM | user value, scope, prioritization, definition of done |
| Architect | Arch | system design, scalability, technical risk, integration points |
| Developer | Dev | implementation complexity, effort, edge cases, technical debt |
| QA Engineer | QA | testability, acceptance criteria, failure modes, regression risk |
All personas are analysis-only: they read the prompt they are given and answer from their role's perspective. They must not edit files, run state-changing commands, or use any tool that modifies the repository or external systems.
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 · 204 lines · 60 tokens per session scan A 727b093c8f82
dev-team is a skill published in the GitHub repository unrealandychan/clean-code-skill (12 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 1,876 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-09.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…