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/junghwayang/oh-my-codex/teamnpx skills add junghwaYang/oh-my-codex --skill teamgit clone --depth 1 https://github.com/junghwaYang/oh-my-codexWrote 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/junghwayang/oh-my-codex/team)<a href="https://agentmods.dev/skills/junghwayang/oh-my-codex/team"><img src="https://agentmods.dev/badge/skills/junghwayang/oh-my-codex/team.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.00000 | $0.00379 |
| Opus 5 | $0.00000 | $0.00189 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
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 4d 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.
What it actually says
Team Skill
Canonical multi-agent orchestration with staged pipeline.
When to Use
- Complex features requiring multiple specialists
- Coordinated parallel work
- Tasks needing plan → execute → verify cycles
- Team-based development workflows
When NOT to Use
- Simple single-file changes
- Quick fixes (use eco)
- Solo exploration tasks
Pipeline Stages
team-plan → team-prd → team-exec → team-verify → team-fix (loop)
1. team-plan
- Analyze task requirements
- Break into workstreams
- Assign agent roles
2. team-prd
- Create detailed specifications
- Define acceptance criteria
- Document dependencies
3. team-exec
- Execute in parallel
- Coordinate between agents
- Track progress
4. team-verify
- Run tests
- Check acceptance criteria
- Validate integration
5. team-fix (loop)
- Address failures
- Iterate until passing
- Max 3 fix attempts
Agent Assignment
Task Type → Primary Agent → Support Agents
────────────────────────────────────────────────────────
Feature Development → Fullstack → Frontend, Backend, Tester
API Design → Backend → Architect, Docs
UI Implementation → Frontend → Designer, Tester
Bug Investigation → Debugger → Analyst, Tester
Refactoring → Refactorer → Reviewer, Tester
Security Audit → Security → Reviewer, Analyst
Usage
team: build a user dashboard with analytics
team 3:executor fix all TypeScript errors
team: implement payment processing with Stripe
Configuration
Agents communicate through shared task lists and can:
- Read/write to shared documents
- Signal completion or blockers
- Request help from other agents
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.
- 4d ago First seen · 76 lines · 0 tokens per session scan A a664eeb1100c
team is a skill published in the GitHub repository junghwaYang/oh-my-codex (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 379 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…