coverage

A test-coverage workflow that repeatedly runs test agents on selected files or folders. Test coverage describes how much of a program’s behavior is checked by tests.

In plain words
What is it for?
Use it to improve tests around target code and receive a summary of the testing work.
Why use it?
It helps find and address untested behavior, stopping when no coverage gaps remain or an error occurs.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/mystilleef/spae-framework/coverage
Any agent
npx skills add mystilleef/spae-framework --skill coverage
Clone the repo
git clone --depth 1 https://github.com/mystilleef/spae-framework

Made for: Claude Code, Codex.

Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 736 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.00736
Opus 5 $0.00007 $0.00368
Sonnet 5 $0.00003 $0.00147
Haiku 4.5 $0.00001 $0.00074

Measured 2d ago against content hash 967bdf847e03, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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 -->
skills/coverage/SKILL.md · 104 lines

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 test agent.

Goal

  • Run test subagents sequentially to cover behavioral gaps in target code.

Input

  • Accept optional arguments (file or folder paths).

Workflow

  1. Testing Loop:
    • Immediately use the subagent tool to spawn a test subagent (pass optional arguments).
    • Await test result.
    • If subagent returns No Gaps status, exit loop and finish.
    • On Failed status or any process failure, halt immediately and surface the error.
    • Loop back to spawn another test subagent if the previous pass returns Improved.
  2. Report: Emit execution summary.

Directives

  • Always use the subagent tool for subagent invocation.
  • Pass the optional argument verbatim to the test subagent; never read or expand file-path arguments.
  • Rely on subagent status blocks to direct the loop.
  • Halt immediately on subagent Failed status or any process failure (crash, timeout, AgentError).
  • List of agents permitted to invoke:
    • test

Constraints

  • Restrict your activities to:
    • Using the subagent tool to spawn test agents to advance the workflow.
    • Using agent results to direct the loop or advance the workflow.
  • Perform orchestration only; never edit codebase files, tests, or documentation.
  • Operate strictly in read-only mode; make no file writes.
  • Never run subagents in 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 test subagents.
  • Confirm loop termination when subagents return No Gaps.
  • Confirm immediate halt when a subagent returns Failed.
  • Confirm zero writes from the orchestration agent itself.

Read the full file on GitHub · 104 lines

Changes

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.

  1. 2d ago First seen · 104 lines · 14 tokens per session scan C 967bdf847e03

Subscribe to this mod's changes

coverage is a skill published in the GitHub repository mystilleef/spae-framework (1 stars, last pushed 28d ago), licensed MIT. It adds 14 tokens to every session and 736 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

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.

crazyMarky/pentest-skills · 71 tokens

results-storage

SQLite-based persistent storage and reporting system for penetration testing results. Use this skill when user needs to store scan results, query vulnerabilities, generate reports, or manage pentest data across sessions.

crazyMarky/pentest-skills · 40 tokens

exploit-sqli

SQL injection detection and exploitation using sqlmap, manual techniques, and custom payloads. Use this skill when user needs to test for SQL injection vulnerabilities, extract database information, or exploit SQLi in parameters, headers, or cookies.

crazyMarky/pentest-skills · 51 tokens

recon-dir-scan

Directory and file enumeration using ffuf, gobuster, dirsearch, and feroxbuster. Use this skill when user needs to discover hidden directories, enumerate files, find backup files, or map application structure through path fuzzing.

crazyMarky/pentest-skills · 52 tokens

recon-fingerprint

Web fingerprinting and WAF detection using wafw00f, whatweb, nuclei, and httpx. Use this skill when user needs to identify web technologies, detect WAF/CDN, analyze server headers, or fingerprint web applications and frameworks.

crazyMarky/pentest-skills · 55 tokens

recon-subdomain

Subdomain enumeration and DNS reconnaissance using subfinder, amass, dnsx, and other tools. Use this skill when user needs to discover subdomains, perform DNS enumeration, gather DNS records, or find hidden subdomains of a target domain.

crazyMarky/pentest-skills · 54 tokens