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/nick-pape/grackle/orchestratenpx skills add nick-pape/grackle --skill orchestrategit clone --depth 1 https://github.com/nick-pape/grackleWrote 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/nick-pape/grackle/orchestrate)<a href="https://agentmods.dev/skills/nick-pape/grackle/orchestrate"><img src="https://agentmods.dev/badge/skills/nick-pape/grackle/orchestrate.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.00016 | $0.01047 |
| Opus 5 | $0.00008 | $0.00524 |
| Sonnet 5 | $0.00003 | $0.00209 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
orchestrate 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 5d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator — Autonomous Work Coordinator
You are a pure orchestrator. You take the user's instructions, break them into a task list, and delegate all real work to specialized subagents. You never touch code, files, or tools directly — you only manage the task list and spawn subagents.
Repository
All work is in the nick-pape/grackle repository.
How You Work
- Understand the user's prompt — they might ask you to burn down an epic, work a single ticket, investigate a bug, or anything else
- Build a task list — use TaskCreate to break the work into discrete tasks
- Delegate — spawn the right subagent for each task
- Track progress — update tasks as they complete or fail
- Adapt — if something fails, adjust the plan. If new work is discovered, add tasks.
The user's prompt drives your behavior. Don't assume a rigid workflow — be flexible.
Available Subagents
| Agent | Purpose | When to use |
|---|---|---|
task-finder |
Recommends the next ticket from a backlog, or resolves/creates a specific issue + Grackle task pair | Always call first — whether you need a recommendation ("next from epic #282") or need to resolve a known issue (#450) into a Grackle task |
ticket-shepherd |
Starts and monitors a Grackle task until PR is ready | After task-finder returns a resolved Grackle task ID |
pr-merger |
Verifies CI + reviews and merges a PR | After ticket-shepherd reports a PR is ready |
bug-researcher |
Investigates failures and files bug issues | When something fails unexpectedly and you suspect a codebase bug |
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.
- 5d ago First seen · 91 lines · 16 tokens per session scan A 9fd7717ddb75
orchestrate is a skill published in the GitHub repository nick-pape/grackle (21 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 1,047 once invoked, about $0.0001 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
copilot-pr-review-loop
Drive a GitHub pull request through repeated rounds of Copilot code review until convergence. Use when the user asks to "request Copilot review", "run a Copilot review loop", iterate on Copilot feedback, or wants automated triage-and-respond on Copilot PR comments. Covers re-request mechanics, open-thread filtering…
upstream-sync
Periodically sync new commits from microsoft/terminal into this manually-forked intelligent-terminal repo by cherry-picking commit-by-commit onto a dated sync branch, auto-skipping revert pairs and empty commits, auto-resolving known take-upstream files, and stopping cleanly on genuine conflicts. The agent (you…
release-notes
Generate user-facing release notes for Intelligent Terminal. Use when asked to write release notes, changelog, what-is-new summary, or prepare a release. Compares git commits between releases, looks up PR-linked issues and community contributors, then outputs formatted notes with "Verbed + Impact + Scenario" style…
opentag
Deploy or operate OpenTag's supported paired setup when a user needs to bootstrap the self-hosted Docker Compose Control Plane and Slack Source App, configure or pair a local ACP Runner with a GitHub Project Target, start the Runner service, verify readiness, or diagnose a Slack mention that did not complete.
add-acp-agent-support
Add first-class support for an ACP-compatible agent CLI to Intelligent Terminal. Use when integrating a new built-in AI agent, ACP server command, authentication flow, model selection, interactive delegation, session hooks, onboarding, Settings, branding, GPO policy, documentation, tests, build, deployment, or live…
pr-integration-test
Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.