Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bdfinst/agentic-dev-team/plugin install dev-teamWrote 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/bdfinst/agentic-dev-team/orchestration-benchmark)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/orchestration-benchmark"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/orchestration-benchmark/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/bdfinst/agentic-dev-team/orchestration-benchmark"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/orchestration-benchmark.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.00107 | $0.02293 |
| Opus 5.5 | $0.00043 | $0.00917 |
| Sonnet 5.5 | $0.00021 | $0.00459 |
| Haiku 4.5 | $0.00011 | $0.00229 |
Grade A, and why
orchestration-benchmark 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.
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestration Benchmark (#1095)
Role: orchestrator. This command dispatches benchmark runs and aggregates their results — it never performs the benchmark tasks itself and never edits the code under test.
You have been invoked with the /orchestration-benchmark command.
Not
/benchmark./benchmarkmeasures runtime performance of web pages (Core Web Vitals, resource sizes, load times). This skill measures orchestration value: whether the dev-team pipeline's delegation earns its overhead against a solo session on the same task at the same rigor. Different subject, different instruments, different report.
Orchestrator constraints
- Matched rigor is non-negotiable. Every arm runs the identical task with identical acceptance checks. An arm may not skip or weaken verification — a cheap worker that reads less and passes weaker checks is a different product, not a cheaper version of the same one. A run that weakened its checks is a rigor violation: discard it, do not average it in.
- The protocol is pre-registered. The decision rule below is fixed before the first run. Do not adjust thresholds, arms, or the task matrix after seeing results — report against the rule as written.
- Never report a single run. Report median + spread per arm per task class. A difference smaller than the spread is a null result.
- Write results to files. Per-run records and the final report go to files; present only the summary tables and verdict in chat.
- Be concise. Tables and short sentences; no narration of each run.
Parse Arguments
Arguments: $ARGUMENTS
--task-class <trivial|standard|complex>: Run only one task-matrix class (bucket names fromknowledge/task-size-classifier.md). Default: all three.--runs <n>: Runs per arm per task class (default: 5). Fewer than 5 makes the result exploratory, not decidable — say so in the report and do not apply the decision rule to it.--dry-run: Print the run plan — interleaved schedule, selected fixtures, each arm's agents' declaredmodel:/effort:frontmatter, and a cost estimate — without dispatching anything.
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 · 192 lines · 107 tokens per session scan A ff2b6449b30f
orchestration-benchmark is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 107 tokens to every session and 2,293 once invoked, about $0.0004 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-03.
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.