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 skills add mystilleef/spae-framework --skill coveragegit 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/coverage)<a href="https://agentmods.dev/skills/mystilleef/spae-framework/coverage"><img src="https://agentmods.dev/badge/skills/mystilleef/spae-framework/coverage/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/skills/mystilleef/spae-framework/coverage"><img src="https://agentmods.dev/badge/skills/mystilleef/spae-framework/coverage.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.00014 | $0.00736 |
| Opus 5.5 | $0.00006 | $0.00294 |
| Sonnet 5.5 | $0.00003 | $0.00147 |
| Haiku 4.5 | $0.00001 | $0.00074 |
Grade C, and why
coverage 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 1mo 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coverage
When to use
- The user wants to address coverage gaps in target code autonomously
using the
testagent.
Goal
- Run test
subagentssequentially to cover behavioral gaps in target code.
Input
- Accept optional arguments (file or folder paths).
Workflow
- Testing Loop:
- Immediately use the
subagenttool to spawn atestsubagent(pass optional arguments). - Await test result.
- If
subagentreturnsNo Gapsstatus, exit loop and finish. - On
Failedstatus or any process failure, halt immediately and surface the error. - Loop back to spawn another
testsubagentif the previous pass returnsImproved.
- Immediately use the
- Report: Emit execution summary.
Directives
- Always use the subagent tool for subagent invocation.
- Pass the optional argument verbatim to the
testsubagent; never read or expand file-path arguments. - Rely on
subagentstatus blocks to direct the loop. - Halt immediately on subagent
Failedstatus or any process failure (crash, timeout,AgentError). - List of agents permitted to invoke:
test
Constraints
- Restrict your activities to:
- Using the
subagenttool to spawntestagents to advance the workflow. - Using agent results to direct the loop or advance the workflow.
- Using the
- Perform orchestration only; never edit codebase files, tests, or documentation.
- Operate strictly in read-only mode; make no file writes.
- Never run
subagentsin parallel or concurrently. - Never activate skills.
- Never invoke agents outside the permitted list.
- Never prompt the user for decisions mid-run; let blockers halt execution.
- Never perform activities beyond subagent invocation, state tracking, and reporting.
Verification
- Confirm sequential execution of
testsubagents. - Confirm loop termination when
subagentsreturnNo Gaps. - Confirm immediate halt when a
subagentreturnsFailed. - Confirm zero writes from the orchestration agent itself.
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.
- 1mo ago First seen · 104 lines · 14 tokens per session scan C 967bdf847e03
coverage is a skill published in the GitHub repository mystilleef/spae-framework (1 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 736 once invoked, about $0.0001 per session on Opus 5.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
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.
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.
superpowers
Development method: plan, check, implement, verify, report. Use for non-trivial tasks with no more specific method skill. Define observable acceptance before code, reproduce bugs before fixes, and complete the requested outcome without procedural permission gates.
test-driven-development
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
auto-verify
Verify completed plan against acceptance criteria. Use after all slices are executed.
testing-discipline
Use when adding/fixing tests, reproducing bugs, checking limits or failures, or deciding what evidence establishes completion. Covers isolated storage, real domain logic, meaningful boundary regressions and verification of the affected runtime/UI surface. Debugging strategy lives in debug-incident-protocol.