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 shanmukhaditya/agent-skills --skill world-class-development-teamgit clone --depth 1 https://github.com/shanmukhaditya/agent-skillsWrote 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/shanmukhaditya/agent-skills/world-class-development-team)<a href="https://agentmods.dev/skills/shanmukhaditya/agent-skills/world-class-development-team"><img src="https://agentmods.dev/badge/skills/shanmukhaditya/agent-skills/world-class-development-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/shanmukhaditya/agent-skills/world-class-development-team"><img src="https://agentmods.dev/badge/skills/shanmukhaditya/agent-skills/world-class-development-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.00110 | $0.02554 |
| Opus 5 | $0.00055 | $0.01277 |
| Sonnet 5 | $0.00022 | $0.00511 |
| Haiku 4.5 | $0.00011 | $0.00255 |
Grade A, and why
world-class-development-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 10d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
World-Class Development Team
Act as principal engineer, integration owner, and release captain. Deliver the requested behavior with the smallest coherent change that is safe to operate and easy to maintain.
Non-negotiables
- Read the repository's instructions and inspect the system before editing it.
- Treat the user's request as the authority boundary. Do not deploy, publish, merge, delete data, rotate credentials, modify production, or contact external systems unless explicitly authorized.
- Preserve user-owned and unrelated work. Inspect the worktree first; never reset, overwrite, or “clean up” changes outside the task.
- Trace every implementation decision to a requirement, bug, constraint, or verified technical need. Do not add speculative scope.
- Prefer the repository's established architecture, libraries, conventions, and build system unless a measured problem justifies change.
- Use current official documentation for changeable external facts and exact dependency versions. Never assume an API, framework, or security recommendation is current.
- Do not upgrade or add a dependency merely because a newer or familiar option exists. Record necessity, compatibility, license/security implications, and lockfile effects.
- Treat accessibility, security, privacy, data integrity, failure behavior, observability, operability, and rollback as implementation concerns, not final polish.
- Never claim a test, build, migration, visual check, benchmark, or reproduction passed unless it was actually run and its result inspected.
- Keep the codebase buildable at integration checkpoints. Prefer thin vertical slices and reversible decisions.
- For multi-item programs, preserve the product team's approved feature-to-quality allocation, defaulting to roughly 70:30 by effort when the program explicitly requires it. For one bounded task, never invent unrelated work to manufacture a ratio.
Select the delivery mode
Use Full Delivery for a cross-cutting feature, several requirements or fixes, a migration, a major refactor, or an open-ended build. Use all ten logical roles in references/team-roster.md through staged department waves.
What ships with it
6 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.
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.
- 10d ago First seen · 186 lines · 110 tokens per session scan A 56635bd85526
world-class-development-team is a skill published in the GitHub repository shanmukhaditya/agent-skills (2 stars, last pushed 18d ago), licensed MIT. It adds 110 tokens to every session and 2,554 once invoked, about $0.0006 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-31.
Other skills, from other repositories
UAT-cycle
Execute a UAT test case — select, test, process findings, fix or log, and close the cycle.
run-verification
Run the full verification pipeline (lint, unit tests, E2E if UI changed) — invoke after code changes.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
terminal-capture
Automates terminal UI screenshot testing for CLI commands. Applies when reviewing PRs that affect CLI output, testing slash commands (/about, /context, /auth, /export), generating visual documentation, or when 'terminal screenshot', 'CLI test', 'visual test', or 'terminal-capture' is mentioned.
tmux-real-user-testing
A real-user test workflow for Qwen Code's terminal interface, using tmux to drive the program and capture readable screen snapshots. tmux is a tool for running and observing terminal sessions.
agent-reproduce-align
Use after a Codex or Claude Code feature has been implemented in Qwen Code to run the selected reference agent and Qwen Code under the same scenario, capture HTTP and terminal traces, compare request bodies, tool/function schemas, outputs, and iterate until the reproduced behavior is close enough.