kc1t/alethe-orchestrate-skill

Install

npx skills add Kc1t/alethe-orchestrate-skill

Getting Started

1. Install with the command above.
2. /alethe setup checks which agent CLIs you have and whether they are logged in, lists their models, and proposes three profiles: base, savings and aggressive. Nothing is saved until you approve.
3. /alethe always (optional) keeps it on in every project, so you never type /alethe again.
4. Ask for the work: /alethe move the billing endpoints to v2, or just ask in plain words while it is on. The lead picks a playbook, previews the plan and runs the workers.
5. /alethe status while it runs, /alethe stop to stop it.
6. /alethe report when it is done: what each worker did, why, and what it cost. /alethe mark used records what you kept.

Passive mode (default)

With the Claude Code plugin hook, Alethe quietly watches the lead session’s own spend and local provider quota from the first prompt. It hands cheaper, bounded scouting, checked mechanical edits, tests and finished-diff reviews to workers without choosing a playbook. Codex comes first while its subscription has fresh room; API-billed workers or unknown/stale quota need your ok. Small, ambiguous and coupled work stays with the lead.

/alethe spend shows lead and delegated tokens and a list-price estimate, a subscription yardstick rather than a bill. Checks appear every 15 minutes, each $5 step of lead spend, or when known quota becomes low, blocked or resets. /alethe off disables it here; /alethe off everywhere disables it everywhere. /alethe passive enables it explicitly. ALETHE_PASSIVE=0 disables only the default. Tune the optional passive block in playbooks. Manual installs without the hook use mode show, spend and usage for checks.

While the Claude Code plugin is installed, its hook runs a small Python script on every prompt and after every tool call. It reads the local Claude transcript, Codex session files and Alethe state; the hook sends nothing over the network. /alethe off disables it in this project; /alethe off everywhere disables the default everywhere, and ALETHE_PASSIVE=0 disables the implicit default. Explicit project modes can still apply; turn them off in those projects too. Off modes leave a quick silent hook check; uninstall the plugin to stop the script from running.

Worker safety

Workers get provider-specific authentication, with unrelated secret variables removed. The runner requires real read-only support, confines working directories and task files, and checks worktree paths, unsafe arguments and process identities. Internal git calls disable hooks and fsmonitor. Exceptions belong in the saved user policy’s trust block (allowUnsafe, cwdRoots, workerEnv), changed only at your explicit request; a plan cannot authorize them.

/alethe clean previews completed folders older than 14 days. Use clean --older-than DAYS --yes to delete eligible folders; current sessions, unfinished work and open worktrees are kept.

Commands

Type them after /alethe.

/alethe help lists the rest.

Keep It On

With always or on, every prompt reminds the lead of your goal and rules, and it decides per request whether to hand work off.

Join Mid-Task

It joins halfway through another skill’s workflow: the spec and the diff so far become the plan.

Change Course

A playbook is a starting point. skip, add, switch and freeform change it between waves, and the report lists every change with its reason.

Playbooks

Agents

Any other CLI with a non-interactive mode, such as Kiro, Copilot CLI or Gemini CLI, runs as a custom worker.

Why It’s Different

• Real spend, never estimated: tokens and cost as each CLI reported them, split between used and discarded results.
• Enforced limits: budgets per wave and per orchestration, a hard cost cap on Claude workers, no subagents.
• Never runs your quota dry: it reads Claude and Codex usage before every wave, refuses to start workers past a stop line, and asks you, with options, before it would spend past it.
• Lean, checked workers: no MCP servers in Codex and Claude workers, and git catches a read-only worker that wrote.
• Easy to audit: Python’s standard library only, no shell, no network, no install scripts.

The Report

/alethe report html opens the same report as a page: a routing map from each wave through the lead to the providers it used, with each one’s share of the tokens, then the workers and what is left to do.

Orchestration report

Check the report on real CLIs, playbook research, 1 wave, 2026-10-18 21:20 to 21:20

• Result: 2 of 2 workers succeeded
• Time: 16s running, 29s of worker time
• Tokens: 108,820 reported, 65,836 of them from cache
• Cost: $0.16 reported by claude; codex reports no cost
• Lead context: 5.0 KB of worker transcripts stayed on disk, 595 B of results to read

Worker	Role	Ran on	Mode	Status	Time	Tokens	Cost
claude-haiku	cheapest Claude model for a one-line answer	claude, haiku	read	succeeded	12s	76,160	$0.16
codex-low	default Codex model at low effort	codex, default model, low	read	succeeded	16s	32,660	-

Video

Example Playbook

scout-then-build: cheap read-only scouts map the code, then one worker writes the change. /alethe editor opens your own playbooks this way, as one offline page where you can switch profiles, simulate quota and edit a step, then copy the YAML back. It works without Python too.

License

MIT, see LICENSE. The Alethe name and logo and the vendor marks belong to their owners. Part of Alethe · Changelog · Issues

(back to top)