A command that examines code and generates tests suited to its language and framework. Tests are small checks that verify code behaves as expected and help reveal missing coverage or recurring test mistakes.

Use it to generate tests for recent changes, a file or directory, or a full project, with an option to skip documentation review.

It helps find untested areas and test anti-patterns without requiring you to inspect the whole project manually. It can focus on changed files, one module, or the entire project.

tests — Command for Claude Code by radumarias/xorio-claude-plugin

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, 11 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/commands/radumarias/xorio-claude-plugin/tests/github.svg)](https://agentmods.dev/commands/radumarias/xorio-claude-plugin/tests)

Your own site

<a href="https://agentmods.dev/commands/radumarias/xorio-claude-plugin/tests"><img src="https://agentmods.dev/badge/commands/radumarias/xorio-claude-plugin/tests/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/commands/radumarias/xorio-claude-plugin/tests"><img src="https://agentmods.dev/badge/commands/radumarias/xorio-claude-plugin/tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 801 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.00015	$0.00801
Opus 5.5	$0.00006	$0.00320
Sonnet 5.5	$0.00003	$0.00160
Haiku 4.5	$0.00002	$0.00080

Measured 1mo ago against content hash db6e9b843532, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

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.

commands/tests.md · 90 lines

How it starts

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

Test Command

Generate tests for code in scope. Detects language, analyzes coverage gaps and anti-patterns, then generates idiomatic tests.

Argument Parsing

Parse $ARGUMENTS to determine scope and options:

No arguments → diff scope: run git diff HEAD to find changed files
--project → project scope: analyze the entire project for coverage gaps
A file or directory path (anything that isn't a flag) → module scope: analyze that path
--no-docs → skip the documentation review step (can combine with any scope)

Examples:

/xorio:tests → diff scope
/xorio:tests src/auth → module scope on src/auth
/xorio:tests --project → full project scan
/xorio:tests src/auth --no-docs → module scope, skip doc review
/xorio:tests --project --no-docs → full project, skip doc review

Workflow

Step 1: Detect Languages

Based on the files in scope, detect languages and frameworks:

Languages:

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

Frameworks (check dependency files):

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 Standards

Read ONLY the matching standards files from the plugin's skill references directory:

Language: ${CLAUDE_PLUGIN_ROOT}/skills/tests/references/test-standards-{language}.md
Framework: ${CLAUDE_PLUGIN_ROOT}/skills/tests/references/test-standards-{framework}.md

Step 3: Analyze

Launch the test-analyzer agent with:

Diff scope: include the git diff HEAD output
Module scope: the path provided by the user
Project scope: instruction to scan the full project
The matching language + framework standards content

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

1mo ago First seen · 90 lines · 15 tokens per session scan A db6e9b843532

Subscribe to this mod's changes

tests is a command published in the GitHub repository radumarias/xorio-claude-plugin (3 stars, last pushed 6d ago), licensed MIT. It adds 15 tokens to every session and 801 once invoked, about $0.0001 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-08-31.

Testing

prototype

You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.

grainulation/grainulator · 0 tokens

qa-changes

This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…

OpenHands/extensions · 63 tokens

tests