Is fan-out-fan-in safe to install?

SaferSkills independently audited fan-out-fan-in (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/fan-out-fan-in/SKILL.md · 1 file

skills/fan-out-fan-in/SKILL.md1.7 KB · Markdown

name: fan-out-fan-in

description: Use this workflow skill only when the user wants explicit parallelization or the task should be split into isolated worktrees and merged back without separate PRs.

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.md or from inline instructions.
Record the parent branch and commit with git branch --show-current and git rev-parse HEAD.
Stop if git status --short is not clean. Do not fan out from a dirty tree.
Scan recent history and existing worktrees with git log --oneline -20 and git worktree list so 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>)
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.

fan-out-fan-in— agent skill

Is fan-out-fan-in safe to install?

Fan Out Fan In

Workflow

Repo Rules

Audit the pieces. Scan the whole. Decide.