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/check)<a href="https://agentmods.dev/agents/mystilleef/spae-framework/check"><img src="https://agentmods.dev/badge/agents/mystilleef/spae-framework/check/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/check"><img src="https://agentmods.dev/badge/agents/mystilleef/spae-framework/check.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.00010 | $0.00356 |
| Opus 5.5 | $0.00004 | $0.00142 |
| Sonnet 5.5 | $0.00002 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
check 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 8d 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 finding and reporting gaps between an implementation and a task plan.
Directives
- Always invoke the
spae-checkskill 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 require, request, or instruct human execution, an attended or interactive terminal, or human presence to reach a verdict; never surface such a dependency as an instruction to the user.
- 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.
Rules
- Don't write or change source code or tests.
- Don't
implementthe fix, plan or spec. - 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.
- 8d ago First seen · 48 lines · 10 tokens per session scan A 45cb4593ccc3
check is an agent published in the GitHub repository mystilleef/spae-framework (2 stars, last pushed 3d ago), licensed MIT. It adds 10 tokens to every session and 356 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
react-reviewer
Frontend-only React/Next.js quality reviewer — audits component design for composition and reuse, not just correctness. Use on React changes (alongside code review, in parallel) to catch boolean-prop proliferation, one-off components that should be composed/reused, and design tokens defined top-down instead of from…
reviewer
In-harness fresh-eyes reviewer of a plan and its implementation (or a diff / PR). Use for a fast local review pass when you do not want to spin up external agents — it complements, and does not replace, the code-review-brief → user-run-external-agents path. Read-only; reports findings, does not fix or post.
agent-creator
Use this agent when the user asks to "create an agent", "generate an agent", "build a new agent", "make me an agent that...", or describes agent functionality they need. Trigger when user wants to create autonomous agents for plugins. Examples: Context: User wants to create a code review agent user: "Create an agent…
skill-reviewer
Use this agent when the user has created or modified a skill and needs quality review, asks to "review my skill", "check skill quality", "improve skill description", or wants to ensure skill follows best practices. Trigger proactively after skill creation. Examples: Context: User just created a new skill user: "I've…
type-design-analyzer
Use this agent when you need expert analysis of type design in your codebase. Specifically use it (1) when introducing a new type to ensure it follows best practices for encapsulation and invariant expression, (2) during pull request creation to review all types being added, and (3) when refactoring existing types to…
code-reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter.