fable-opus

Name: fable-opus
Author: mrtooher

126installs84forks

How to install fable-opus?

mrtooher/fable-mode/fable-opus

$npx -y skills add mrtooher/fable-mode --skill fable-opus

Installs into the current project.

Summary

Run fable-mode execution discipline on Claude Opus — the strongest staged run available. Routes the task to the @fable-orchestrator agent (Opus, Write-less), which stages the work, delegates artifact production to @fable-worker-sonnet / @fable-worker-haiku, and cold-checks delive

Files · 1

View on GitHub

SKILL.md

1	# Fable Mode — Opus (v3, agent-routed)
2
3	v3 change: delegation is enforced structurally, not requested in prose. The
4	orchestrator is a real agent definition (`agents/fable-orchestrator.md`) with no
5	Write/Edit tool — it cannot do the work inline, so "spawn a worker" stops being
6	a suggestion the model can skip. (Change prompted by field report: prose-level
7	"you may spawn workers" almost always ran inline on the main thread.)
8
9	If a task has one obvious correct approach and fits in a single pass, skip this
10	loop and do it directly.
11
12	## How to run it
13
14	1. Confirm the fable agents are installed (`fable-orchestrator`,
15	`fable-worker-sonnet`, `fable-worker-haiku`, `fable-verifier` appear in the
16	available agent types). If they are not, fall back to the inline method:
17	spawn a general-purpose Opus agent and pass it the Core loop and operational
18	rules verbatim from `agents/fable-orchestrator.md`.
19	2. Spawn @fable-orchestrator via the Task tool (`subagent_type:
20	"fable-orchestrator"`). Brief it with: the user's task, the output
21	directory, relevant session context, and any user-set limits (warning
22	threshold, worker cap, deadline).
23	3. Do not restate the Core Loop or operational rules in the briefing — the
24	orchestrator's agent definition carries them. Brief the task, not the
25	method.
26	4. When it returns, relay the result, every stage it marked unverified, and its
27	recommendations (surfaced scope it did not build).
28
29	## Known limitation
30
31	Write-removal closes the front door, not the side door: the orchestrator keeps
32	Bash for running verification commands, and Bash can technically create files.
33	Its definition forbids that use; if audits show it writing through Bash, the
34	next tightening is removing Bash and routing even check-execution through
35	workers (cost: one extra hop per check).

People who liked this also viewed

6 picks

Type

fable-opus

126installs84forks

View on GitHub

How to install fable-opus?

mrtooher/fable-mode/fable-opus

$npx -y skills add mrtooher/fable-mode --skill fable-opus

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Fable Mode — Opus (v3, agent-routed)
2
3	v3 change: delegation is enforced structurally, not requested in prose. The
4	orchestrator is a real agent definition (`agents/fable-orchestrator.md`) with no
5	Write/Edit tool — it cannot do the work inline, so "spawn a worker" stops being
6	a suggestion the model can skip. (Change prompted by field report: prose-level
7	"you may spawn workers" almost always ran inline on the main thread.)
8
9	If a task has one obvious correct approach and fits in a single pass, skip this
10	loop and do it directly.
11
12	## How to run it
13
14	1. Confirm the fable agents are installed (`fable-orchestrator`,
15	`fable-worker-sonnet`, `fable-worker-haiku`, `fable-verifier` appear in the
16	available agent types). If they are not, fall back to the inline method:
17	spawn a general-purpose Opus agent and pass it the Core loop and operational
18	rules verbatim from `agents/fable-orchestrator.md`.
19	2. Spawn @fable-orchestrator via the Task tool (`subagent_type:
20	"fable-orchestrator"`). Brief it with: the user's task, the output
21	directory, relevant session context, and any user-set limits (warning
22	threshold, worker cap, deadline).
23	3. Do not restate the Core Loop or operational rules in the briefing — the
24	orchestrator's agent definition carries them. Brief the task, not the
25	method.
26	4. When it returns, relay the result, every stage it marked unverified, and its
27	recommendations (surfaced scope it did not build).
28
29	## Known limitation
30
31	Write-removal closes the front door, not the side door: the orchestrator keeps
32	Bash for running verification commands, and Bash can technically create files.
33	Its definition forbids that use; if audits show it writing through Bash, the
34	next tightening is removing Bash and routing even check-execution through
35	workers (cost: one extra hop per check).

People who liked this also viewed

6 picks

Type