A repository-specific testing workflow for running the project's standard checks and reviewing failures or coverage. Test coverage shows which parts of the code are exercised by tests.

Use it to run quick, regression, assurance, or coverage test suites, install required development dependencies, and reproduce failures locally.

It provides one agreed local test procedure and helps verify whether changes meet the project's assurance requirements.

test — Skill for Claude Code and Codex by physics91: A repository-specific testing workflow for running the project's standard…

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/physics91/openrouter-mcp/test

Any agent

npx skills add physics91/openrouter-mcp --skill test

Clone the repo

git clone --depth 1 https://github.com/physics91/openrouter-mcp

Made for: Claude Code, Codex.

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/physics91/openrouter-mcp/test.svg)](https://agentmods.dev/skills/physics91/openrouter-mcp/test)

Your own site

<a href="https://agentmods.dev/skills/physics91/openrouter-mcp/test"><img src="https://agentmods.dev/badge/skills/physics91/openrouter-mcp/test.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 938 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.

Model	Per session	Once invoked
Fable 5	$0.00027	$0.00938
Opus 5	$0.00014	$0.00469
Sonnet 5	$0.00005	$0.00188
Haiku 4.5	$0.00003	$0.00094

Measured 3d ago against content hash 38a0b9a18180, 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 3d 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.

.agents/skills/test/SKILL.md · 89 lines

How it starts

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

Test Skill

Overview

This repository's canonical local test entrypoint is python3 run_tests.py <suite> -v. Use it even when package.json exposes wrappers; the Python runner is the source of truth for local assurance behavior.

Execution Baseline

Prefer python3 for running run_tests.py and installing Python dependencies.
If python3 is unavailable but python exists, use python as fallback.
If pip installation is blocked by externally-managed environment (PEP 668), create and use local .venv.
Default recommendation: assurance for PR readiness.
For the fastest confidence check, use quick first and then regression if needed.
Do not substitute npm run test:assurance unless the user explicitly wants the npm wrapper.

Preflight

Confirm python3 and npm are available.
For assurance or coverage, ensure pytest-cov is installed:
```
python3 -m pip install -r requirements-dev.txt
```

If pip is externally managed, switch to:

python3 -m venv .venv
.venv/bin/python -m pip install -r requirements-dev.txt

For the real suite, require OPENROUTER_API_KEY and remember the run is interactive and billable.

Canonical Command

python3 run_tests.py <suite> -v

Quick Reference

Suite	Command	When to use
`assurance`	`python3 run_tests.py assurance -v`	PR gate (unit+contract+property+replay+security, coverage>=70%)
`unit`	`python3 run_tests.py unit -v`	Fast isolated checks during development
`integration`	`python3 run_tests.py integration -v`	Mocked API integration smoke test
`quick`	`python3 run_tests.py quick -v`	Fastest sanity (two regression guards only)
`regression`	`python3 run_tests.py regression -v`	Critical bug-prevention tests
`coverage`	`python3 run_tests.py coverage -v`	Full HTML coverage report (`htmlcov/index.html`)
`all`	`python3 run_tests.py all -v`	Everything except real API tests
`real`	`python3 run_tests.py real -v`	Live API calls - requires `OPENROUTER_API_KEY`, consumes credits

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

3d ago First seen · 89 lines · 27 tokens per session scan A 38a0b9a18180

Subscribe to this mod's changes

test is a skill published in the GitHub repository physics91/openrouter-mcp (9 stars, last pushed 21d ago), licensed MIT. It adds 27 tokens to every session and 938 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-31.

Testing

systematic-debugging

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

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 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