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 agentmods add skills/mystilleef/spae-framework/spae-orchestratenpx skills add mystilleef/spae-framework --skill spae-orchestrategit clone --depth 1 https://github.com/mystilleef/spae-frameworkWrote 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/mystilleef/spae-framework/spae-orchestrate)<a href="https://agentmods.dev/skills/mystilleef/spae-framework/spae-orchestrate"><img src="https://agentmods.dev/badge/skills/mystilleef/spae-framework/spae-orchestrate.svg" alt="Measured on agentmods" height="20"></a>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.00022 | $0.01127 |
| Opus 5 | $0.00011 | $0.00563 |
| Sonnet 5 | $0.00004 | $0.00225 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade C, and why
spae-orchestrate scanned grade C with 1 finding 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 5d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- prettier-ignore-start --> How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate SPAE
When to use
- The user wants to perform all phases of the
SPAEstructured workflow autonomously.
Goal
- Spawn the subagent matching the current
STATE.jsonphase, looped until the workstream completes. - Halt immediately on any subagent failure.
Input
Read .spae/current/STATE.json to resolve the current phase and
cursor. Accept an optional argument, the proposal, during initial
execution.
STATE.json
See references/STATE.md for the field reference, directives, and
phase snapshots.
Phase-agent map
Every phase maps to exactly one subagent, spawned the same way regardless of phase:
phase |
Subagent |
|---|---|
spec |
spec |
plan |
plan |
inspect |
inspect |
build |
build |
check |
check |
fix |
fix |
verify |
verify |
Workflow
- Resolve Workstream:
- Locate
.spae/current/STATE.json. - Missing, no proposal argument: halt.
- Missing, proposal provided: spawn
specwith the proposal; await completion; proceed to step 2. - Present: proceed to step 2 without spawning.
- Locate
- Dispatch Loop:
- Re-read
.spae/current/STATE.json; recordphase. - Exit on
phase: "done",status: "completed", or a missing.spae/currentsymlink. - Halt immediately if
phasematches none of the phase-agent map's rows. - Spawn the subagent the map names for the recorded
phase, no arguments. - Await completion; halt immediately on
Failedstatus or any process failure (crash, timeout,AgentError). - Re-read
.spae/current/STATE.json; halt immediately ifphasematches the value recorded at the start of this iteration. - Repeat step 2.
- Re-read
- Finalize: Emit the execution summary.
Directives
- Always use the subagent tool for subagent invocation.
- Rely only on
STATE.jsonfor all orchestration decisions. - Operate strictly in read-only mode; make no file writes.
- Trust the machine-readable state file over subagent output text.
- Pass the proposal argument verbatim to the bootstrap
specspawn only; never reuse it on later iterations, and never read or expand file-path arguments. - Halt immediately on subagent
Failedstatus or any process failure (crash, timeout,AgentError). - List of agents permitted to invoke:
specplaninspectbuildcheckfixverify
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 146 lines · 22 tokens per session scan C 68d5e8f85409
spae-orchestrate is a skill published in the GitHub repository mystilleef/spae-framework (1 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,127 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
architecture
Project architecture and file structure conventions for all process types. Use when: (1) Creating new files or modules, (2) Deciding where code should go, (3) Converting single-file components to directories, (4) Reviewing code for structure compliance, (5) Adding new bridges, services, agents, or workers.
testing
Testing workflow and quality standards for writing and running tests. Use when: (1) Writing new tests, (2) Adding a new feature that needs tests, (3) Modifying logic that has existing tests, (4) Before claiming a task is complete.
ahk-review
Preview a code review against ticket/objective alignment, with deep semantic (name-vs-behavior) analysis. No tasks created, no harness tracking.
ahk-test
Design, write, and run behavior-focused tests for an objective or existing code. Writes test files only and reports evidence. No tasks created, no harness tracking.
ahk-triage
Triage a bug or unexpected behavior. Deep diagnostic analysis with structured report. No tasks created, no harness tracking.
ahk-use-case-tech
Turn an approved use-case specification into a linked, evidence-backed technical specification.