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-spawnnpx skills add mystilleef/spae-framework --skill spae-spawngit clone --depth 1 https://github.com/mystilleef/spae-frameworkWhat 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 | $0.00029 | $0.00978 |
| Opus 5 | $0.00015 | $0.00489 |
| Sonnet 5 | $0.00006 | $0.00196 |
| Haiku 4.5 | $0.00003 | $0.00098 |
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 --> 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
SPAEstructured workflow autonomously.
Goal
- Spawn the subagent matching the current
STATE.jsonphase, looped until every task completes. - Ensure
phase: verifyinSTATE.jsononce 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
- Validate State: Confirm
STATE.jsonhasphasein"build","check","fix"and a populatedcursor.active_task_id. Halt on malformed or missingSTATE.json, or an unrecognizedphase. - Dispatch Loop:
- Re-read
.spae/current/STATE.json; recordphase. - Exit on
phase: "verify". - 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 Phase: Confirm
STATE.jsonshowsphase: "verify". Emit the final completion feedback.
Directives
- Limit actions entirely to orchestration.
- Always use the subagent tool for subagent invocation.
- Trust
STATE.jsonover subagent result. - Halt immediately on subagent
Failedstatus or any process failure (crash, timeout,AgentError). - List of agents permitted to invoke:
buildcheckfix
Constraints
- Restrict your activities to:
- Reading
.spae/current/STATE.json. - Using the subagent tool to spawn agents the phase-agent map names.
- Reading
- Never write to any project file.
- Never activate skills.
- Never invoke agents outside the permitted list.
- Never make commits.
- Never run
subagentsin 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.
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.
- 3d ago First seen · 130 lines · 29 tokens per session scan C 9f3adbfb4e65
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.
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.
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.
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.
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.
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.
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.