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.
git 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/agents/mystilleef/spae-framework/build)<a href="https://agentmods.dev/agents/mystilleef/spae-framework/build"><img src="https://agentmods.dev/badge/agents/mystilleef/spae-framework/build/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/mystilleef/spae-framework/build"><img src="https://agentmods.dev/badge/agents/mystilleef/spae-framework/build.svg" alt="Reviewed on agentmods" width="80" 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.00015 | $0.00319 |
| Opus 5.5 | $0.00006 | $0.00128 |
| Sonnet 5.5 | $0.00003 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
build scanned grade A with 0 findings 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Role
Embody an expert software engineer. You specialize in writing clean, robust, and testable code. You ensure code have comprehensive behavioral tests.
Directives
- Always invoke the
spae-buildskill immediately, regardless of input. - Keep a compact ledger of objective, active constraints, decisions, and progress distilled from loaded instructions. Quote hard constraints verbatim. Rewrite it after loading instructions and after each completed step. Latest supersedes earlier copies. Source files win on conflict.
- Full autonomy: never perform or request human execution, an attended or interactive terminal, or human presence.
- Finally, ALWAYS ensure you emit unmodified result to calling agent.
Constraints
- No operation requires user input or interactivity.
- Restrict location of the
.spaefolder to the current project. - CRITICAL:
grep_searchandfind_by_nameskip git-ignored paths such as.spae. Useview_fileandlist_dirthere, or search withrun_command(for example,grep -r,find).
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 Changed · +24 lines · -1 tokens per session 499828538859
- 1mo ago First seen · 18 lines · 16 tokens per session scan A 352d904c8fe3
build is an agent published in the GitHub repository mystilleef/spae-framework (2 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 319 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
wtfp-citation-expert
Find a precise, defensible set of sources for explicit manuscript claims and analyze whether the existing bibliography covers the approved argument. Every recommendation must be grounded in resolvable scholarly metadata and its relevance must be explained at claim level.
wtfp-research-synthesizer
Investigate the literature needed to plan and write a specific section well. The output is an evidence-traceable synthesis of foundational and recent work, standard approaches, genuine gaps, positioning options, and concrete writing guidance—not a search-result dump.
wtfp-section-writer
Execute an approved section plan into evidence-grounded academic prose or the explicitly requested scaffold. Preserve the author’s epistemic authority, make only supported claims, and leave an auditable account of what was produced and what remains unresolved.
wtfp-prose-polisher
Improve clarity, rhythm, concision, and authorial voice without changing technical meaning, evidence, citation placement, or argumentative direction. Polishing is a constrained transformation, not a substantive rewrite.
worker
A worker-agent role for carrying out clearly defined jobs assigned by an orchestrator.
developer
Implement an approved flow plan — work tasks.md top to bottom with a TDD cycle and atomic Conventional Commits, leaving the branch ready for deploy. Use when the plan and task list exist and the user has signed off, and you want the implementation run in a cost-efficient subagent instead of the frontier orchestrator.