test

A workflow for finding a project's test setup, running the smallest useful tests, and reporting what was and was not checked.

In plain words
What is it for?
Use it to run tests for a specific change, add or improve tests when authorized, and document failures and remaining gaps.
Why use it?
It avoids assuming a test framework and prevents overstating coverage or test results.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/hmbown/codewhale/test
Any agent
npx skills add Hmbown/CodeWhale --skill test
Clone the repo
git clone --depth 1 https://github.com/Hmbown/CodeWhale

Made for: Claude Code, Codex.

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 142 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00028 $0.00142
Opus 5 $0.00014 $0.00071
Sonnet 5 $0.00006 $0.00028
Haiku 4.5 $0.00003 $0.00014

Measured yesterday against content hash 9c6665b525f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

crates/tui/assets/skills/test/SKILL.md · 21 lines

What it actually says

Test

When to use

Use when the user wants tests run, added, or improved for a concrete surface.

Non-goals

  • Do not invent a test framework the repo does not use.
  • Do not claim coverage you did not measure.

Workflow

  1. Detect the repo’s test runner and conventions.
  2. Run the narrowest useful suite for the change.
  3. Add or update tests only when authorized.
  4. Report pass/fail with commands and residual gaps.
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. yesterday First seen · 21 lines · 28 tokens per session scan A 9c6665b525f9

Subscribe to this mod's changes

test is a skill published in the GitHub repository Hmbown/CodeWhale (40,867 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 142 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-30.

Related

Other skills, from other repositories

Session Monitoring

Provides awareness of claudectl session state, health checks, and cost tracking. Activated when the user asks about session health, spending, brain decisions, or multi-session coordination.

mercurialsolo/claudectl · 38 tokens

qa-testing

Verify your work by actually operating the app or website you changed, instead of assuming it works. Strongly recommended whenever you build, modify, or debug a web app, website, or desktop GUI app. Drive real browsers with the agent-browser CLI and native desktop apps with the cua-driver CLI. These are installed on…

openinterpreter/openinterpreter · 77 tokens

organize-modules

Apply private modules with public re-exports (barrel export) pattern for clean API design. Includes conditional visibility for docs and tests. Use when creating modules, organizing mod.rs files, or before creating commits.

r3bl-org/r3bl-open-core · 47 tokens

check-bounds-safety

Apply type-safe bounds checking patterns using VPIndex/VPLength types instead of usize. Use when working with arrays, buffers, cursors, viewports, or any code that handles indices and lengths.

r3bl-org/r3bl-open-core · 46 tokens

check-code-quality

Run comprehensive Rust code quality checks including compilation, linting, documentation, and tests. Use after completing code changes and before creating commits.

r3bl-org/r3bl-open-core · 31 tokens

analyze-performance

Establish performance baselines and detect regressions using flamegraph analysis. Use when optimizing performance-critical code, investigating performance issues, or before creating commits with performance-sensitive changes.

r3bl-org/r3bl-open-core · 38 tokens