run-tests

run-tests is a skill for Claude Code from makigjuro/cloudstack-ai-plugins. It costs 58 tokens per session (1,148 once invoked), scanned A, original, MIT.

A test-running helper for .NET projects that detects which files changed and selects the related test projects. It supports unit tests, integration tests, or both.

In plain words
What is it for?
Use it to run affected unit or integration tests, test one service, or run all available tests after a change.
Why use it?
It avoids running unrelated tests when only part of a codebase changed, while still allowing tests for a named service or the whole solution.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the dev-workflow plugin — 14 skills, 4 agents, 2 hooks, 1 MCP server shipped together

Good fit Use it to run affected unit or integration tests, test one service, or run all available tests after a change.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/makigjuro/cloudstack-ai-plugins/run-tests
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.

Any agent
npx skills add makigjuro/cloudstack-ai-plugins --skill run-tests
Clone the repo
git clone --depth 1 https://github.com/makigjuro/cloudstack-ai-plugins

Made for: Claude Code.

Or install dev-workflow, the plugin that ships this one along with the rest of its 14 skills, 4 agents, 2 hooks, 1 MCP server.

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.

agentmods badge for run-tests

README.md
[![agentmods](https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/run-tests/github.svg)](https://agentmods.dev/skills/makigjuro/cloudstack-ai-plugins/run-tests)
Your own site
<a href="https://agentmods.dev/skills/makigjuro/cloudstack-ai-plugins/run-tests"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/run-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.

agentmods 80×15 button for run-tests

Your own site · 80×15
<a href="https://agentmods.dev/skills/makigjuro/cloudstack-ai-plugins/run-tests"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/run-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,148 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00058 $0.01148
Opus 5.5 $0.00023 $0.00459
Sonnet 5.5 $0.00012 $0.00230
Haiku 4.5 $0.00006 $0.00115

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

Security

Grade A, and why

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

plugins/dev-workflow/skills/run-tests/SKILL.md · 139 lines

How it starts

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

Run Tests -- Smart Change-Aware Test Selection

Run tests based on what changed. Auto-detects affected services from git diff and runs only their test projects instead of the full suite.

Configuration

Read cloudstack.json from the project root at the start of execution. Extract relevant fields:

  • SOLUTION = backend.solutionPath (default: find *.sln)
  • SERVICES = backend.services[] (default: discover from project structure)

If cloudstack.json does not exist, auto-detect by scanning the project structure.

1. Parse Arguments

Determine from user input:

  • MODE: unit (default), integration, or all
  • SERVICE: optional service name or slug
  • Explicit --all flag: runs both unit and integration for all projects
User says MODE SERVICE
/run-tests unit (auto-detect)
/run-tests {service} unit {service}
/run-tests --integration integration (auto-detect)
/run-tests --integration {service} integration {service}
/run-tests --all all (auto-detect)
/run-tests --all {service} all {service}

2. Resolve Test Projects

Auto-detection approach

Use git diff to identify changed files and map them to test projects:

# Get changed files relative to main
CHANGED_FILES=$(git diff origin/main...HEAD --name-only 2>/dev/null; git diff --name-only 2>/dev/null; git diff --name-only --cached 2>/dev/null)

Map changed source paths to their corresponding test projects:

  1. For each changed file under a service's source path, find matching test projects by convention (e.g., {ServicePath}.Tests.Unit, {ServicePath}.Tests.Integration, {ProjectPrefix}.Tests.*).
  2. If shared/foundational code changed (shared domain, shared infrastructure), fall back to running the full test suite.
  3. If only non-source files changed (docs, config, CI), report "No tests affected" and offer to run the full suite.

Explicit service mode

When a service name is provided, look up its path from cloudstack.json and find test projects matching that service's project prefix.

Read the full file on GitHub · 139 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. 1mo ago First seen · 139 lines · 58 tokens per session scan A 4457b0bd3433

Subscribe to this mod's changes

run-tests is a skill published in the GitHub repository makigjuro/cloudstack-ai-plugins (1 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 1,148 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

opa

Generate, test, validate, explain, and debug OPA (Open Policy Agent) Rego policies and Conftest configurations. Covers deny/warn/violation rules, unit tests, regal linting, conftest fmt, namespace design, input shape analysis, and GitHub Actions integration. Use when asked to "write a policy", "test a rego file"…

nitinjain999/platform-skills · 98 tokens

e2e

Orchestrates e2e testing: BDD scenarios, Playwright autotests. Triggers: e2e tests, BDD scenarios, write autotest.

kochetkov-ma/claude-brewcode · 37 tokens

testing-laravel

Writes Laravel tests using PHPUnit. Use when "write tests", "add tests", "phpunit", "laravel test", "feature test", "unit test", "mock", "factory", or testing controllers, models, services, actions, jobs, artisan commands, or API endpoints.

iliaal/whetstone · 63 tokens

testing-react

Writes React/TypeScript tests using Vitest and React Testing Library. Use when "write react tests", "vitest", "component test", "hook test", "RTL", "testing library", "snapshot test", or testing React components, hooks, and utilities.

iliaal/whetstone · 57 tokens

ia-verification-before-completion

Enforces fresh verification evidence before any completion claim. Use when about to claim "tests pass", "bug fixed", "done", "ready to merge", handing off work, or before editing when a request has ambiguous scope.

iliaal/whetstone · 52 tokens

ia-writing-tests

Generic test writing discipline: test quality, real assertions, anti-patterns, and rationalization resistance. Use when writing tests, adding test coverage, or fixing failing tests for any language or framework. Complements language-specific skills.

iliaal/whetstone · 49 tokens