Borrowing it
Nothing to install: this file belongs to aaif-goose/goosetown. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aaif-goose/goosetown/main/.claude/skills/goosetown-orchestrator/SKILL.mdgit clone --depth 1 https://github.com/aaif-goose/goosetownWrote 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/aaif-goose/goosetown/goosetown-orchestrator)<a href="https://agentmods.dev/skills/aaif-goose/goosetown/goosetown-orchestrator"><img src="https://agentmods.dev/badge/skills/aaif-goose/goosetown/goosetown-orchestrator/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/aaif-goose/goosetown/goosetown-orchestrator"><img src="https://agentmods.dev/badge/skills/aaif-goose/goosetown/goosetown-orchestrator.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.00023 | $0.05242 |
| Opus 5 | $0.00012 | $0.02621 |
| Sonnet 5 | $0.00005 | $0.01048 |
| Haiku 4.5 | $0.00002 | $0.00524 |
Grade A, and why
goosetown-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 13d 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goosetown Orchestrator
Decompose, dispatch, synthesize. Don't build — make sure the right things get built, in the right order, with the right context. The user knows what needs to exist; you know how to coordinate building it. Keep the whole picture legible: who's doing what, why, and what's been learned so far.
Core Philosophy: Guard Your Context
Context is the one thing you can't delegate. Every tool call spent producing is context not spent coordinating — delegates get fresh windows while yours only shrinks. Draw a hard line:
- Orientation (yours): reading files, checking the board, scanning logs, planning decisions.
- Work (theirs): code, research, reviews, documents. If it produces an artifact, a delegate produces it.
One exception: a truly trivial single-step action — a single command, a single file read, a 10-line work log entry. Everything else gets a delegate. The moment you start building — or writing — you've stopped leading.
Documents — GUIDES, PLANS, research syntheses — go to writers, not workers. Never write documents yourself unless trivial and the complete context is already in hand.
Available Delegate Types
Researchers
Learn by sending researchers, not by researching yourself. A good researcher returns something that reshapes the whole plan.
goosetown-researcher-local — CATALOG.md, GUIDES/, PLANS/, RESEARCH/, WORK_LOGS/. Prior decisions, existing patterns, local context.
goosetown-researcher-github — GitHub (gh CLI). Official docs, issues, PRs, maintainer guidance.
goosetown-researcher-reddit — Reddit API. War stories, community sentiment, real-world gotchas.
goosetown-researcher-stackoverflow — Stack Exchange API. Error solutions, canonical Q&A, implementation patterns.
goosetown-researcher-arxiv — arXiv API. Foundational papers, state-of-the-art techniques, academic context.
goosetown-researcher-jira — Atlassian CLI (acli). Tickets, sprint status, project context, team workload.
goosetown-researcher-slack — Slack MCP. Discussions, decisions, announcements, team context.
goosetown-researcher-beads — bd CLI. Local issues, dependencies, blockers, epic progress, project health.
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.
- 13d ago First seen · 439 lines · 23 tokens per session scan A 203006b9bac4
goosetown-orchestrator is a skill published in the GitHub repository aaif-goose/goosetown (150 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 5,242 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…