A command that runs a project’s code checks and tests, then fixes problems and repeats the checks until they pass. A linter is a tool that finds style and common code mistakes.

Use it to check current changes, fix linter errors and failed tests, and prepare code for review.

It puts the repeated cycle of finding, fixing, and checking issues into one workflow and also looks for small problems in changed files.

How xsovad06/sova configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to xsovad06/sova. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/xsovad06/sova/main/.claude/commands/test.md

Clone the repo

git clone --depth 1 https://github.com/xsovad06/sova

Made for: Claude Code.

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/xsovad06/sova/test/github.svg)](https://agentmods.dev/commands/xsovad06/sova/test)

Your own site

<a href="https://agentmods.dev/commands/xsovad06/sova/test"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/test/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/xsovad06/sova/test"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 371 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.00017	$0.00371
Opus 5.5	$0.00007	$0.00148
Sonnet 5.5	$0.00003	$0.00074
Haiku 4.5	$0.00002	$0.00037

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

Security

Grade A, and why

test 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 21d 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.

.claude/commands/test.md · 64 lines

What it actually says

Test Runner

Run tests and linter, fixing issues iteratively until everything passes.

Instructions

Step 1: Identify the Scope

Determine what to test from $ARGUMENTS or the current directory. If unclear, check git diff --name-only to see which modules have changes.

Step 2: Run Linter

Run the project's lint command: make lint

If linter fails:

Analyze the errors
Fix the code issues
Re-run until it passes

Step 3: Run Tests

Run the project's test command: make test

If tests fail:

Analyze the test failures
Fix the code or tests as needed
Re-run until they pass

Step 4: Scout Check

While fixing test or lint failures, scan each touched file for pre-existing issues: flaky test patterns, stale imports, dead code. Fix them alongside the failures. Keep scout fixes small and low-risk.

Step 5: Iterate

Repeat Steps 2-4 until both linter and tests pass completely.

Cross-References

After tests pass: Run the /review workflow to self-review before pushing
Full workflow: Use the /develop-full workflow for the complete develop-test-review-pr cycle

Rules

Always fix linter issues before running tests
After fixing issues, re-run to verify the fix
Continue iterating until both pass
Report final status when everything is green
NEVER use emojis in any output

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.

21d ago Changed e8decbe82462
1mo ago Changed 4078cf1be5bb
2mo ago First seen · 64 lines · 17 tokens per session scan A d9d3fe94e7ab

Subscribe to this mod's changes

test is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 371 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.

Code review Testing ai-agents automation autonomous-development cli core developer-tools

sova: Command for Claude Code