subagent-orchestration — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited subagent-orchestration (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.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Fable 5 dispatches and sustains parallel subagents far more dependably than prior models. Used well this cuts wall-clock time and improves verification quality; used badly it burns tokens on coordination overhead. The patterns:
Split out a subtask when it is (a) independent of your current working context, (b) large enough to amortize the handoff, and (c) specifiable in a few sentences plus file pointers. Don't delegate tightly coupled edits — coordination costs exceed parallelism gains.
For checking finished work, a separate verifier subagent with a clean context outperforms self-critique: it can't share your blind spots because it doesn't share your assumptions. Give the verifier the specification and the output — not your reasoning — and have it report discrepancies against the spec at a defined cadence (every N components, every X hours) rather than once at the end.
A good subagent brief contains exactly: goal (one sentence), inputs (paths/data), definition of done (checkable), constraints (what not to touch), and where to write results. If you can't fill these in, the task isn't ready to delegate.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.