test

A read-only verification workflow that runs a project’s type checks, code-quality checks, tests, and build when those checks exist.

In plain words
What is it for?
Use it before starting work, after a merge, or when continuous integration is failing to run the relevant checks and report each result.
Why use it?
It shows whether the project is healthy without changing files or applying fixes.

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/dixus/claudeframework/test
Any agent
npx skills add dixus/claudeframework --skill test
Clone the repo
git clone --depth 1 https://github.com/dixus/claudeframework

Made for: Claude Code, Codex.

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 587 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.00034 $0.00587
Opus 5 $0.00017 $0.00293
Sonnet 5 $0.00007 $0.00117
Haiku 4.5 $0.00003 $0.00059

Measured 2d ago against content hash 9a6e552420d2, 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 2d 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/skills/test/SKILL.md · 36 lines

What it actually says

Run the full verify suite and report the results. Do not fix anything — report only.

Primary use case: run this skill when CI is red, after a merge/rebase, or before starting a new PRD to confirm the baseline is clean. This is intentionally read-only — no fixes are applied here.

Use a subagent to run the commands so the output does not consume the main session's context. The subagent should return a structured summary.

Steps:

  1. Read CLAUDE.md to discover the project's verify commands (typecheck, lint, tests, build). If no commands are listed, detect them from the project structure (e.g. package.json scripts, Makefile, pyproject.toml, Cargo.toml, etc.)
  2. If $ARGUMENTS is provided, run only that specific test file or test pattern using the project's test runner
  3. Otherwise run all verify commands in this order: a. Typecheck (e.g. tsc --noEmit, mypy, pyright, or equivalent — skip if none detected) b. Lint (e.g. eslint, ruff, clippy, or equivalent — skip if none detected) c. Tests (e.g. vitest, pytest, cargo test, go test ./..., or equivalent) d. Build (e.g. npm run build, cargo build, go build, or equivalent — skip if none detected)
  4. Report:
    • Each command run and its exit status
    • How many tests passed / failed / skipped
    • Any typecheck or lint errors with file and line reference
    • A clear overall status: PASS or FAIL

ACTION REQUIRED — do not end your response without doing this:

If running as a subagent (no direct user interaction), skip the question and return the structured summary instead.

  • If overall status is PASS: Ask: "All checks pass. This was run as [standalone check / part of pipeline]. Shall I proceed to /2_review <spec-name>?"
  • If overall status is FAIL: Identify the root cause for each failure and suggest a specific fix — but do not apply fixes. Then ask: "Suite is FAIL with [N] failures. How do you want to proceed? A) Route to /3_fix if these are known review issues B) Route to /debug for a specific error C) Show me the full error output first"

Do not end your response without asking this question.

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. 2d ago First seen · 36 lines · 34 tokens per session scan A 9a6e552420d2

Subscribe to this mod's changes

test is a skill published in the GitHub repository dixus/claudeframework (10 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 587 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens