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 skills add kaeawc/auto-mobile --skill fan-out-fan-ingit clone --depth 1 https://github.com/kaeawc/auto-mobileWrote 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/kaeawc/auto-mobile/fan-out-fan-in)<a href="https://agentmods.dev/skills/kaeawc/auto-mobile/fan-out-fan-in"><img src="https://agentmods.dev/badge/skills/kaeawc/auto-mobile/fan-out-fan-in/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/kaeawc/auto-mobile/fan-out-fan-in"><img src="https://agentmods.dev/badge/skills/kaeawc/auto-mobile/fan-out-fan-in.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.00036 | $0.00422 |
| Opus 5 | $0.00018 | $0.00211 |
| Sonnet 5 | $0.00007 | $0.00084 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
fan-out-fan-in 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 12d 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.
What it actually says
Fan Out Fan In
Use this when the user explicitly wants parallel agent work or the task is naturally decomposable into independent file scopes.
Workflow
- Read the plan from a file such as
scratch/plan.mdor from inline instructions. - Record the parent branch and commit with
git branch --show-currentandgit rev-parse HEAD. - Stop if
git status --shortis not clean. Do not fan out from a dirty tree. - Scan recent history and existing worktrees with
git log --oneline -20andgit worktree listso you do not duplicate work. - Split the work into units that do not edit the same files. If two units need the same file, merge them or sequence them.
- For each unit, create an isolated worktree from the parent commit with
git worktree add ../worktree-unit-N -b fan-out-unit-N "$PARENT_COMMIT". - In each worktree, implement only the assigned scope, run the relevant validation, and commit with
fan-out: [unit-name]. - Merge unit branches back into the parent branch one at a time, validating after each merge and again at the end.
- Remove successful worktrees and branches. Preserve failed ones for inspection.
Repo Rules
- Prefer repo validations over generic ones:
- TypeScript:
bun run lint,bun run build,bun test - Fast repo checks:
bash scripts/all_fast_validate_checks.sh - Android:
(cd android && ./gradlew <task>)
- TypeScript:
- Write logs that matter to
scratch/if they are too long to inspect inline. - Do not create PRs or push branches as part of fan-out work.
- Do not proceed if the work cannot be partitioned cleanly.
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.
- 12d ago First seen · 31 lines · 36 tokens per session scan A c286e2205bee
fan-out-fan-in is a skill published in the GitHub repository kaeawc/auto-mobile (47 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 422 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…