spae-spawn

spae-spawn is a skill for Claude Code, Codex from mystilleef/spae-framework. It costs 29 tokens per session (978 once invoked), scanned C, original, MIT.

An automation step for SPAE, a structured workflow for taking a coding task from request to verified change. It repeatedly runs the build, check, and fix phases until all registered tasks are complete.

In plain words
What is it for?
Use it to execute SPAE tasks after planning and inspection, including checking results and fixing detected problems.
Why use it?
It coordinates implementation and correction work without requiring manual dispatch of each phase. It also moves the workflow to verification when the loop finishes.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/mystilleef/spae-framework/spae-spawn
Any agent
npx skills add mystilleef/spae-framework --skill spae-spawn
Clone the repo
git clone --depth 1 https://github.com/mystilleef/spae-framework

Made for: Claude Code, Codex.

Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 978 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00029 $0.00978
Opus 5 $0.00015 $0.00489
Sonnet 5 $0.00006 $0.00196
Haiku 4.5 $0.00003 $0.00098

Measured 3d ago against content hash 9f3adbfb4e65, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

spae-spawn 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 3d 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 -->
skills/spae-spawn/SKILL.md · 130 lines

How it starts

The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spawn

When to use

  • The user wants to perform the build phase of the SPAE structured workflow autonomously.

Goal

  • Spawn the subagent matching the current STATE.json phase, looped until every task completes.
  • Ensure phase: verify in STATE.json once the loop exits.

Input

Read .spae/current/STATE.json for phase, cursor, and task registry.

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
build build
check check
fix fix

Workflow

  1. Validate State: Confirm STATE.json has phase in "build", "check", "fix" and a populated cursor.active_task_id. Halt on malformed or missing STATE.json, or an unrecognized phase.
  2. Dispatch Loop:
    • Re-read .spae/current/STATE.json; record phase.
    • Exit on phase: "verify".
    • Halt immediately if phase matches 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 Failed status or any process failure (crash, timeout, AgentError).
    • Re-read .spae/current/STATE.json; halt immediately if phase matches the value recorded at the start of this iteration.
    • Repeat step 2.
  3. Finalize Phase: Confirm STATE.json shows phase: "verify". Emit the final completion feedback.

Directives

  • Limit actions entirely to orchestration.
  • Always use the subagent tool for subagent invocation.
  • Trust STATE.json over subagent result.
  • Halt immediately on subagent Failed status or any process failure (crash, timeout, AgentError).
  • List of agents permitted to invoke:
    • build
    • check
    • fix

Constraints

  • Restrict your activities to:
    • Reading .spae/current/STATE.json.
    • Using the subagent tool to spawn agents the phase-agent map names.
  • Never write to any project file.
  • Never activate skills.
  • Never invoke agents outside the permitted list.
  • Never make commits.
  • Never run subagents in parallel or concurrently.
  • Never prompt the user for decisions mid-run; let failures halt execution.
  • Never perform activities beyond subagent invocation, state tracking, and reporting.

Read the full file on GitHub · 130 lines

Files

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.

Changes

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.

  1. 3d ago First seen · 130 lines · 29 tokens per session scan C 9f3adbfb4e65

Subscribe to this mod's changes

spae-spawn is a skill published in the GitHub repository mystilleef/spae-framework (1 stars, last pushed 29d ago), licensed MIT. It adds 29 tokens to every session and 978 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.

Related

Other skills, from other repositories

exploit-xss

Cross-site scripting (XSS) vulnerability detection and exploitation. Supports reflected XSS, stored XSS, DOM-based XSS, and blind XSS testing. Use this skill when user mentions XSS, cross-site scripting, script injection, or needs to test JavaScript injection in parameters, forms, headers, or DOM sources.

crazyMarky/pentest-skills · 71 tokens

results-storage

SQLite-based persistent storage and reporting system for penetration testing results. Use this skill when user needs to store scan results, query vulnerabilities, generate reports, or manage pentest data across sessions.

crazyMarky/pentest-skills · 40 tokens

exploit-sqli

SQL injection detection and exploitation using sqlmap, manual techniques, and custom payloads. Use this skill when user needs to test for SQL injection vulnerabilities, extract database information, or exploit SQLi in parameters, headers, or cookies.

crazyMarky/pentest-skills · 51 tokens

recon-dir-scan

Directory and file enumeration using ffuf, gobuster, dirsearch, and feroxbuster. Use this skill when user needs to discover hidden directories, enumerate files, find backup files, or map application structure through path fuzzing.

crazyMarky/pentest-skills · 52 tokens

recon-fingerprint

Web fingerprinting and WAF detection using wafw00f, whatweb, nuclei, and httpx. Use this skill when user needs to identify web technologies, detect WAF/CDN, analyze server headers, or fingerprint web applications and frameworks.

crazyMarky/pentest-skills · 55 tokens

recon-subdomain

Subdomain enumeration and DNS reconnaissance using subfinder, amass, dnsx, and other tools. Use this skill when user needs to discover subdomains, perform DNS enumeration, gather DNS records, or find hidden subdomains of a target domain.

crazyMarky/pentest-skills · 54 tokens