A command that identifies a project's testing setup and runs its test suite. Tests are automated checks that verify whether software behaves as expected.

Use it to detect and run tests for JavaScript, Python, Rust, Go, or Make-based projects, then report passed, failed, skipped, and relevant error details.

It removes the guesswork of choosing the right test command and makes failures easier to classify as new or pre-existing.

test — Command for Claude Code by Sagargupta16/claude-skills

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.

Clone the repo

git clone --depth 1 https://github.com/Sagargupta16/claude-skills

Made for: Claude Code.

Or install dev-workflow, the plugin that ships this one along with the rest of its 1 skill, 7 commands, 2 agents.

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

Your own site

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

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

When invoked 318 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.00010	$0.00318
Opus 5.5	$0.00004	$0.00127
Sonnet 5.5	$0.00002	$0.00064
Haiku 4.5	$0.00001	$0.00032

Measured 1mo ago against content hash aaeaaee0f49d, 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 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.

plugins/dev-workflow/commands/test.md · 29 lines

What it actually says

Live state

Detection: !ls -1 package.json pyproject.toml pytest.ini setup.cfg Cargo.toml go.mod Makefile 2>/dev/null
package.json scripts: !jq -r '.scripts // {} | to_entries | map("\(.key): \(.value)") | .[]' package.json 2>/dev/null | head -10 || echo "no package.json"

Task

Using the detection above, run the project's test suite.

Framework mapping:

package.json with scripts.test -> pnpm test (preferred), else npm test or yarn test
pytest.ini / pyproject.toml [tool.pytest] / setup.cfg -> pytest -v (or uv run pytest -v if uv.lock exists)
Cargo.toml -> cargo test
go.mod -> go test ./...
Makefile with test: target -> make test

If tests fail:

Parse the failing test name and root-cause line.
Show the specific assertion or error message.
Classify: is the failure in code we just changed, or pre-existing?
Suggest a minimal fix. Do not auto-fix unless the user asked.

Report: X passed, Y failed, Z skipped and whether failures are new or pre-existing.

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 Changed aaeaaee0f49d
1mo ago First seen · 29 lines · 10 tokens per session scan A def6c1662ef5

Subscribe to this mod's changes

test is a command published in the GitHub repository Sagargupta16/claude-skills (5 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 318 once invoked, about $0.0000 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.

Claude Code Testing ai-agents claude developer-tools marketplace plugins

test

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Live state

Task

What this file has done since we first saw it

Other commands, from other repositories

verify

run-e2e

improve-test-quality

test-gap-analysis

tdd-bug

tdd-refactor