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/steipete/agent-scripts/maintainer-orchestratornpx skills add steipete/agent-scripts --skill maintainer-orchestratorgit clone --depth 1 https://github.com/steipete/agent-scriptsWrote 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/steipete/agent-scripts/maintainer-orchestrator)<a href="https://agentmods.dev/skills/steipete/agent-scripts/maintainer-orchestrator"><img src="https://agentmods.dev/badge/skills/steipete/agent-scripts/maintainer-orchestrator.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.00039 | $0.02186 |
| Opus 5 | $0.00019 | $0.01093 |
| Sonnet 5 | $0.00008 | $0.00437 |
| Haiku 4.5 | $0.00004 | $0.00219 |
Grade A, and why
maintainer-orchestrator 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.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintainer Orchestrator
Coordinate a real maintainer queue across multiple independent issues, pull requests, or repositories. This is a control-plane skill, not the default way to handle ordinary repository work.
Activation Gate — Hard Rule
Classify the request before creating workers, heartbeats, ledgers, or queue scans.
Direct single-item work
A request is single-item when it names or implies one issue, one PR, one bug, one feature, one release, or one coherent implementation—even when that work spans several files, phases, tests, CI, or closely coupled repositories.
For single-item work:
- Do not create a project worker merely because the task is nontrivial.
- Do not create a heartbeat, portfolio ledger, queue refill, dependency sweep, release proposal, or broad repository scan.
- Continue in the current session using the repository's normal skills and workflow (
codex-first, maintainer/review/testing/release skills, and repo instructions as applicable). - Ordinary focused subagents or Codex delegation remain governed by those normal skills; this orchestrator adds no extra worker requirement.
- If this skill was invoked accidentally for a single item, state that orchestration mode is unnecessary and continue directly. Never interrupt useful in-flight work solely to satisfy this skill.
Examples that stay direct:
- fix and land one issue;
- repair one contributor PR;
- trace one failure across an application and its dependency;
- make one release;
- implement one coherent refactor across two repositories.
Bounded orchestration
Use orchestration mode only when at least one is true:
- the user asks to handle multiple independent issues or PRs;
- the user asks to coordinate multiple repositories or parallel workstreams;
- the user asks for a queue, sweep, batch, portfolio, maintainer night, or ongoing triage;
- independent items materially benefit from concurrent ownership and coordination.
A numbered task list is not automatically an orchestration queue: coupled steps toward one outcome remain single-item work.
What ships with it
2 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.
- 4d ago First seen · 194 lines · 39 tokens per session scan A a3764116fa35
maintainer-orchestrator is a skill published in the GitHub repository steipete/agent-scripts (6,596 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 2,186 once invoked, about $0.0002 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
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…