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.
npx agentmods add skills/alphalab-ustc/ohmycode/run-testsnpx skills add AlphaLab-USTC/OhMyCode --skill run-testsgit clone --depth 1 https://github.com/AlphaLab-USTC/OhMyCodeWhat 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 | $0.00032 | $0.00996 |
| Opus 5 | $0.00016 | $0.00498 |
| Sonnet 5 | $0.00006 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00100 |
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 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.
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-testsgenerates 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 ✓
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.
- 2d ago First seen · 117 lines · 32 tokens per session scan A 21555ca522be
run-tests is a skill published in the GitHub repository AlphaLab-USTC/OhMyCode (131 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 996 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
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…
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…