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/fix)<a href="https://agentmods.dev/agents/mystilleef/spae-framework/fix"><img src="https://agentmods.dev/badge/agents/mystilleef/spae-framework/fix/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/fix"><img src="https://agentmods.dev/badge/agents/mystilleef/spae-framework/fix.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.00009 | $0.00314 |
| Opus 5.5 | $0.00004 | $0.00126 |
| Sonnet 5.5 | $0.00002 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
fix 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 today.
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-fixskill 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.
- today First seen · 42 lines · 9 tokens per session scan A 795268b419e8
fix is an agent published in the GitHub repository mystilleef/spae-framework (1 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 314 once invoked, about $0.0000 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-10-18.
Other agents, from other repositories
investigator
Executes all 5 phases of the systematic debugging investigation under the Iron Law methodology. Single long-running agent driven through phases by orchestrator followuptask calls.
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
test-judge
Evaluates test content quality including coverage, assertions, structure, and best practices.
tester
Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or…
testing-bug-fixer
A bug-fixing agent that reproduces problems, traces them to their underlying cause, applies a small targeted change, and adds a regression test.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.