A testing workflow for the OhMyCode project that runs its pytest test suite and examines the results. Pytest is a tool for automatically running Python tests.

Use it to run all tests or a selected area, such as tools, core loop code, providers, configuration, or skills, then analyze failures.

It checks code changes for broken behavior and helps identify what failed before a fix is committed.

How AlphaLab-USTC/OhMyCode configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to AlphaLab-USTC/OhMyCode. 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/AlphaLab-USTC/OhMyCode/main/.claude/skills/run-tests/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/AlphaLab-USTC/OhMyCode

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/skills/alphalab-ustc/ohmycode/run-tests/github.svg)](https://agentmods.dev/skills/alphalab-ustc/ohmycode/run-tests)

Your own site

<a href="https://agentmods.dev/skills/alphalab-ustc/ohmycode/run-tests"><img src="https://agentmods.dev/badge/skills/alphalab-ustc/ohmycode/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/alphalab-ustc/ohmycode/run-tests"><img src="https://agentmods.dev/badge/skills/alphalab-ustc/ohmycode/run-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 996 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.00032	$0.00996
Opus 5.5	$0.00013	$0.00398
Sonnet 5.5	$0.00006	$0.00199
Haiku 4.5	$0.00003	$0.00100

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

.claude/skills/run-tests/SKILL.md · 117 lines

How it starts

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

Run Tests for OhMyCode

Run the project test suite, analyze results, and take action on failures.

This skill is part of the OhMyCode development closed-loop:

编码 ──→ /gen-tests ──→ /run-tests ──→ 分析失败 ──→ 修代码 ──╮
 ↑                                                            │
 ╰────────────────────────────────────────────────────────────╯

When to Use

After /gen-tests generates new test files — verify them immediately
After editing any source code in ohmycode/ — catch regressions
After fixing a bug found by a previous /run-tests — confirm the fix
Before committing — full suite gate
User says "run tests", "check tests", "verify tests"

Input

$ARGUMENTS — optional scope specifier. If empty, run the full suite.

Argument	pytest path
(empty)	`tests/` (full suite)
`tools`	`tests/tools/`
`tools/bash`	`tests/tools/test_bash.py`
`core`	`tests/core/`
`core/loop`	`tests/core/test_loop.py`
`providers`	`tests/providers/`
`config`	`tests/config/`
`skills`	`tests/skills/`
specific file path	use as-is

Step 1 — Determine Scope

Resolve $ARGUMENTS to a pytest target path using the table above.

If a specific file is given, verify it exists. If not, check for the closest match under tests/.

Step 2 — Run Tests

python3 -m pytest <resolved_path> -v --tb=short 2>&1 | tee tests_run.log

Use -v for verbose output and --tb=short for concise tracebacks.

Step 3 — Analyze Results

All passed

Report the result summary (e.g., "73 passed in 2.1s") and confirm the code is healthy. No further action needed.

Failures detected — enter fix loop

For each failure:

Read the traceback from the test output
Classify the root cause:
- Test bug — the test itself has a wrong assertion or outdated expectation
- Implementation bug — the source code under test has a defect
- Environment issue — missing dependency, import error, fixture mismatch
Fix it:
- For test bugs: fix the test code directly
- For implementation bugs: fix the source code in ohmycode/
- For environment issues: install missing deps or fix config
Re-run /run-tests — repeat until all green ✓

Read the full file on GitHub · 117 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.

1mo ago First seen · 117 lines · 32 tokens per session scan A 21555ca522be

Subscribe to this mod's changes

run-tests is a skill published in the GitHub repository AlphaLab-USTC/OhMyCode (132 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 996 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-30.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

OhMyCode: Skill for Claude Code