Borrowing it
Nothing to install: this file belongs to me2resh/apexyard. 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/me2resh/apexyard/main/.claude/skills/fan-out/SKILL.mdgit clone --depth 1 https://github.com/me2resh/apexyardWrote 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/me2resh/apexyard/fan-out)<a href="https://agentmods.dev/skills/me2resh/apexyard/fan-out"><img src="https://agentmods.dev/badge/skills/me2resh/apexyard/fan-out/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/me2resh/apexyard/fan-out"><img src="https://agentmods.dev/badge/skills/me2resh/apexyard/fan-out.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.00024 | $0.02179 |
| Opus 5 | $0.00012 | $0.01090 |
| Sonnet 5 | $0.00005 | $0.00436 |
| Haiku 4.5 | $0.00002 | $0.00218 |
Grade A, and why
fan-out 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 10d 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.
/fan-out — Parallel Agent Fan-Out
Spawns multiple specialised agents in parallel — each on its own task, optionally in its own git worktree — so independent work items progress concurrently instead of being silently serialised behind a single agent's session.
This skill is the happy path for parallel execution. The companion rule .claude/rules/parallel-work.md defines when to offer fan-out proactively. Read both before invoking.
When to use
The trigger heuristic is in parallel-work.md. The short version: use /fan-out when the user's request decomposes into ≥ 2 work items that are file-independent, context-independent, and individually substantial.
Do NOT use when:
- Tasks share file write targets (worktree merge-back will conflict)
- One task's output is another's input (sequential dependency)
- The work is a single indivisible task
- The decision itself is the work (architecture / AgDR-class) — that needs cross-task reasoning, not concurrency
Process
1. Gather tasks
Accept tasks from any of these forms:
$ARGUMENTSas a comma-separated list:"audit hooks dir, audit skills dir, audit rules dir"- A markdown file path:
/fan-out tasks.md— one task per line, blank lines and#comments ignored --from-tickets <list>:/fan-out --from-tickets apexyard#109,apexyard#110,apexyard#111— fetch each issue title + body viagh issue viewand use them as task descriptions- Interactive entry — if
$ARGUMENTSis empty, prompt: "Paste your tasks, one per line. Blank line to finish."
Trim whitespace, drop empties. If the result is fewer than 2 tasks, stop: fan-out is overkill for one item.
2. Per-task questions — ASK ONCE per task
For each task, infer the answer from the description first, then ask only when ambiguous.
Agent type — default general-purpose. Options:
| Agent | Use for |
|---|---|
general-purpose |
Implementation, multi-step research, anything mixed |
Explore |
Read-only research, codebase questions, audits |
code-reviewer |
Reviewing an existing PR (read-only) |
security-reviewer |
Security audit of a PR (read-only) |
Plan |
Plan-mode — produces a plan, no edits |
| Custom | Any subagent in .claude/agents/ |
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.
- 10d ago First seen · 191 lines · 24 tokens per session scan A 74d9ec6fa9fe
fan-out is a skill published in the GitHub repository me2resh/apexyard (498 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 2,179 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…