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-fixnpx skills add mystilleef/spae-framework --skill spae-fixgit 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-fix)<a href="https://agentmods.dev/skills/mystilleef/spae-framework/spae-fix"><img src="https://agentmods.dev/badge/skills/mystilleef/spae-framework/spae-fix.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 | $0.00032 | $0.01876 |
| Opus 5 | $0.00016 | $0.00938 |
| Sonnet 5 | $0.00006 | $0.00375 |
| Haiku 4.5 | $0.00003 | $0.00188 |
Grade C, and why
spae-fix 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix (SPAE)
When to use
STATE.jsonreportsphase: fix.FIX.mdlists pre-classified gaps for the active in-progress task.
Goal
- Close only the active task's named
FIX.mdgaps through minimal, test-driven changes. - Return the workstream to
/checkwithout task completion, cursor movement, plan edits, or scope expansion.
Input
Read:
- STATE.json in
.spae/current/for task management (consultreferences/STATE.mdfor field reference, directives, and phase snapshots). - FIX.md in
.spae/current/for gaps to address. - Project source, tests, configuration, docs, and command output required by the named gaps.
Testing
See references/testing-guide.md for test structure, isolation,
mocking, assertion, and performance standards.
Cleanup
See references/cleanup-guide.md for the self-introduced-artifact
checklist and diff-only audit scope.
Workflow
- GATE—Read
.spae/current/STATE.json; confirmphase: fixand an active task identifier. Self-heal state drift: iftasks[active_task_id]reads"todo", correct it to"in_progress"and writeSTATE.jsonbefore proceeding. Halt on state drift: iftasks[active_task_id]reads"done", halt. Read.spae/current/FIX.md; confirm its task identifier matches the active task and its## Gapslist supplies concrete actionable gaps. Halt on missing, malformed, or mismatched input; report the failed precondition; make no changes. - ORIENT—Goal: close the named gaps for one active task and return
it to
/check. LeavePLAN.md,SPEC.md, task completion, cursor movement, forward tasks, and unrelated project concerns untouched. - PLAN—List each pre-classified
FIX.mdgap. Map its required test surface: expected behavior, failure modes, and edge cases. Use the taskIntentonly for context; never expand scope from it,Acceptance,Verification, forward tasks, seams, or observations. - ACT—For each named gap:
- Write a failing or gap-reproducing test covering expected behavior, failure modes, and edge cases.
- Write the minimal source, test, configuration, or documentation change required by that gap.
- Run targeted checks; repeat
test→implementuntil the gap passes.
What ships with it
4 files 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 · 188 lines · 32 tokens per session scan C a119345e188e
spae-fix is a skill published in the GitHub repository mystilleef/spae-framework (1 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 1,876 once invoked, about $0.0002 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-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-review
Preview a code review against ticket/objective alignment, with deep semantic (name-vs-behavior) analysis. No tasks created, no harness tracking.
ahk-use-cases
Define or refine a feature, change, refactor, or user journey as an approved non-technical use-case specification.
ahk-triage
Triage a bug or unexpected behavior. Deep diagnostic analysis with structured report. No tasks created, no harness tracking.