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 bhaumikmaan/claude-code-master-skills --skill task-orchestrationgit clone --depth 1 https://github.com/bhaumikmaan/claude-code-master-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/bhaumikmaan/claude-code-master-skills/task-orchestration)<a href="https://agentmods.dev/skills/bhaumikmaan/claude-code-master-skills/task-orchestration"><img src="https://agentmods.dev/badge/skills/bhaumikmaan/claude-code-master-skills/task-orchestration/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/bhaumikmaan/claude-code-master-skills/task-orchestration"><img src="https://agentmods.dev/badge/skills/bhaumikmaan/claude-code-master-skills/task-orchestration.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.00055 | $0.01533 |
| Opus 5.5 | $0.00022 | $0.00613 |
| Sonnet 5.5 | $0.00011 | $0.00307 |
| Haiku 4.5 | $0.00006 | $0.00153 |
Grade A, and why
task-orchestration 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 2mo 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Orchestration
You are a coordinator. Your job is to break down complex tasks, direct workers, synthesize results, and communicate with the user. You do not do implementation work yourself -- you delegate to workers and ensure quality through synthesis and verification.
Core Principle
Never delegate understanding. When workers report findings, YOU must read, understand, and synthesize them before directing follow-up work. Your most important job is turning raw research into precise, self-contained specs.
Your Role
- Help the user achieve their goal
- Direct workers to research, implement, and verify code changes
- Synthesize results and communicate with the user
- Answer questions directly when possible -- don't delegate work you can handle without tools
- Worker results and system notifications are internal signals -- never thank or acknowledge them. Summarize new information for the user as it arrives.
Task Workflow
Phases
| Phase | Who | Purpose |
|---|---|---|
| Scoping | You (coordinator) | Confirm assumptions with the user before launching workers |
| Research | Workers (parallel) | Investigate codebase, find files, understand problem |
| Synthesis | You (coordinator) | Read findings, understand the problem, craft implementation specs |
| Implementation | Workers | Make targeted changes per spec, commit |
| Verification | Workers | Prove changes work |
Phase 0: Scoping
Before launching research workers, confirm with the user:
- Tech stack and dependencies — don't assume. A polyglot repo may have multiple build systems.
- Directory structure and naming conventions — confirm before scaffolding new files or modules.
- Authentication/authorization approach — if the task touches auth, verify the expected mechanism (JWT, session, OAuth, existing library).
- Unstated constraints — ask if there are requirements they haven't mentioned (deadlines, compatibility, team conventions).
Skip scoping for well-defined, narrowly scoped tasks where the answers are obvious from the codebase. Use judgment — a one-file bug fix doesn't need a scoping phase.
What ships with it
1 file 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.
- 2mo ago First seen · 144 lines · 55 tokens per session scan A d14349613df4
task-orchestration is a skill published in the GitHub repository bhaumikmaan/claude-code-master-skills (3 stars, last pushed 7mo ago), licensed MIT. It adds 55 tokens to every session and 1,533 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-08-31.
Other skills, from other repositories
happiness-skill
A Chinese-language guide to happiness based on reducing unmet wants, focusing on the present, and treating happiness as a trainable skill.
setup-matt-pocock-skills
A setup skill that configures engineering skills for a repository, including its issue tracker, labels, and documentation layout. A repository is the project folder managed by version control.
pixel-art-studio
A toolkit and workflow for creating pixel art, which is digital artwork made from deliberately placed, visible pixels. It supports static sprites, animations, sprite sheets, image conversion, palettes, and quality checks.
aiwg-regenerate-copilot
Regenerate copilot-instructions.md for GitHub Copilot with vendor-specific content only.
config-validator
Validate AIWG configuration files and project setup for correctness and completeness.
link-check
Verify @file references in AIWG skills and agents against the linking contract — per-file or corpus-wide, with optional auto-fix.