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 jaktestowac/awesome-copilot-for-testers --skill creating-orchestration-packsgit clone --depth 1 https://github.com/jaktestowac/awesome-copilot-for-testersWrote 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/jaktestowac/awesome-copilot-for-testers/creating-orchestration-packs)<a href="https://agentmods.dev/skills/jaktestowac/awesome-copilot-for-testers/creating-orchestration-packs"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/creating-orchestration-packs/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/jaktestowac/awesome-copilot-for-testers/creating-orchestration-packs"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/creating-orchestration-packs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00091 | $0.02328 |
| Opus 5 | $0.00046 | $0.01164 |
| Sonnet 5 | $0.00018 | $0.00466 |
| Haiku 4.5 | $0.00009 | $0.00233 |
Grade A, and why
creating-orchestration-packs 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 11d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Orchestration Packs
Use this skill when a job is too big for one custom agent and splitting it into cooperating roles would produce better work rather than just more files.
A pack is a folder of .agent.md files plus a README, living under agent-orchestration/. One agent orchestrates and delegates; the rest do the work and return a structured handoff packet. The orchestrator synthesizes.
The value comes from the same place it comes from in human teams: an agent with a narrow scope and a clear output contract does better work than one asked to do everything. The cost is coordination, and a pack that costs more coordination than it saves is worse than a single good agent.
When to Use
- a workflow has genuinely distinct phases with different tool needs
- one agent's instruction file has grown into several unrelated roles
- explore, plan, implement, review, and verify would each benefit from a fresh, narrow context
- two branches of work could run in parallel and be merged
- an existing pack fails
npm run lintbecause a handoff target does not resolve
Operating Principles
- A role earns its file. Each agent has a scope another agent does not, or it should be merged.
- The orchestrator delegates and never implements. The moment it writes code, its context fills and the pack collapses into one agent with extra steps.
- Every handoff target resolves.
handoffs[].agentandagents[]entries must exactly match aname:in the same pack. CI enforces this. - Tools are granted per role, minimally. An explorer that cannot write files cannot accidentally write files.
- One output contract, shared by every agent. Mixed return shapes make the orchestrator's synthesis unreliable.
- Names are unique across packs, because users install more than one.
Workflow
Phase 0: Check that a pack is the right shape
A pack is justified when at least two of these hold:
- the phases need different tools, and granting the union to one agent would be over-privileged
- a phase benefits from a fresh context rather than one carrying everything before it
- two phases could genuinely run in parallel
- a review step is more useful when it did not write the thing it reviews
- the workflow is long enough that one agent would lose the early instructions by the end
What ships with it
3 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.
- 11d ago First seen · 191 lines · 91 tokens per session scan A 16e08cb23013
creating-orchestration-packs is a skill published in the GitHub repository jaktestowac/awesome-copilot-for-testers (113 stars, last pushed 15d ago), licensed MIT. It adds 91 tokens to every session and 2,328 once invoked, about $0.0005 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.
Other skills, from other repositories
fastapi_stripe
A Stripe Checkout implementation takes four steps.
standalone-python-scripts
Skill "standalone-python-scripts" from iloveitaly/llm-ide-rules, covering standalone python scripts, /// script, requires-python = ">=3.13", dependencies = [] and ///.
secrets
Here's how environment variables are managed in this application.
fix-tests
Focus on all unit + command tests (pytest --exclude tests/integration). Make sure they pass and fix errors. If you run into anything very odd: stop, and let me know. Mutate test code first and let me know if you think you should update application code.
plan-only
As this point, I only want to talk about the plan. How would you do this? What would you refactor to make this design clean? You are an expert software engineer and I want you to think hard about how to plan this project out.
dev-in-browser
Use your browser to view https://verso.localhost which is tied to livereload dev server which is already running. You can inspect that page (including taking screenshots!) to validate that your changes fixed the issue.