What is generate-tests-coverage?

A workflow that scans a project for code with too few tests and creates tests for important coverage gaps.

Use it to inspect Rust, TypeScript, or Python projects, identify their frameworks, and generate tests for under-tested source areas.

It helps reveal untested business logic across supported languages and frameworks, where bugs can otherwise go unnoticed.

generate-tests-coverage — Skill for Claude Code by radumarias

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add radumarias/xorio-claude-plugin

Claude Code

/plugin install xorio

Made for: Claude Code.

Or install xorio, the plugin that ships this one along with the rest of its 9 skills, 10 commands, 4 agents, 2 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/radumarias/xorio-claude-plugin/generate-tests-coverage/github.svg)](https://agentmods.dev/skills/radumarias/xorio-claude-plugin/generate-tests-coverage)

Your own site

<a href="https://agentmods.dev/skills/radumarias/xorio-claude-plugin/generate-tests-coverage"><img src="https://agentmods.dev/badge/skills/radumarias/xorio-claude-plugin/generate-tests-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/radumarias/xorio-claude-plugin/generate-tests-coverage"><img src="https://agentmods.dev/badge/skills/radumarias/xorio-claude-plugin/generate-tests-coverage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 728 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00028	$0.00728
Opus 5	$0.00014	$0.00364
Sonnet 5	$0.00006	$0.00146
Haiku 4.5	$0.00003	$0.00073

Measured 8d ago against content hash f254d7ac59a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

generate-tests-coverage 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.

skills/generate-tests-coverage/SKILL.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Generate Tests for Coverage Gaps

Scan the entire project for under-tested code and generate tests to fill coverage gaps, prioritizing critical business logic.

Workflow

Step 1: Detect All Languages and Frameworks

Scan the project root to detect all languages and frameworks present:

Languages:

.rs files or Cargo.toml → Rust
.ts/.tsx files or package.json → TypeScript
.py files or pyproject.toml/setup.py → Python

Frameworks:

Cargo.toml contains egui → egui
package.json contains react → React
package.json contains vue → Vue.js
package.json contains three → Three.js
package.json contains spark → SparkJS
Dockerfile or docker-compose.yml exists → Docker
AWS SDK deps, CDK, CloudFormation, or SAM templates → AWS

Step 2: Load All Matching Standards

Read all matching standards files from ${CLAUDE_PLUGIN_ROOT}/skills/tests/references/:

One test-standards-{language}.md per detected language
One test-standards-{framework}.md per detected framework

Step 3: Parallel Analysis

Launch test-analyzer agents in parallel, split by source directories for speed. Each gets its language's standards. Example splits:

crates/ → Rust analyzer with Rust + egui standards
tools/renderer/ → TypeScript analyzer with TS + Three.js standards
src/ → whichever language is present there

Also launch the test-docs-advisor agent in parallel for a full project documentation review.

Step 4: Present Comprehensive Gap Analysis

Aggregate results from all analyzers and present:

Project test health summary — overall coverage assessment per language/module
Critical gaps — highest risk items across the project
High/Medium/Low gaps — remaining items by priority
Documentation suggestions from the docs advisor

Ask the user which gaps to fill. Suggest starting with Critical items.

Step 5: Generate Tests

Launch test-generator agents — parallelize across independent modules:

One agent per language/crate/package if they're independent
Each gets only its language + framework standards
Each gets its subset of the gap list

Read the full file on GitHub · 79 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.

8d ago First seen · 79 lines · 28 tokens per session scan A f254d7ac59a8

Subscribe to this mod's changes

generate-tests-coverage is a skill published in the GitHub repository radumarias/xorio-claude-plugin (3 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 728 once invoked, about $0.0001 per session on Opus 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.

Testing Unit testing

migrate-xunit-to-xunit-v3

Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…

dotnet/skills · 149 tokens

go-testing

Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.

Gentleman-Programming/gentle-ai · 26 tokens

nw-fp-clojure

Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.

nWave-ai/nWave · 25 tokens

mobiai-ios-testing

Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.

ArisGuimera/MobiAI-Core · 31 tokens

restore-internals-seams-in-finally-blocks-after-each-test

When delegating a task affected by this skill, include.

ZaxbyHub/opencode-swarm · 26 tokens

testing-llm

LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.

yonatangross/orchestkit · 55 tokens