Borrowing it
Nothing to install: this file belongs to agentculture/agenda. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agentculture/agenda/main/.claude/skills/run-tests/SKILL.mdgit clone --depth 1 https://github.com/agentculture/agendaWrote 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.
[](https://agentmods.dev/skills/agentculture/agenda/run-tests)<a href="https://agentmods.dev/skills/agentculture/agenda/run-tests"><img src="https://agentmods.dev/badge/skills/agentculture/agenda/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.
<a href="https://agentmods.dev/skills/agentculture/agenda/run-tests"><img src="https://agentmods.dev/badge/skills/agentculture/agenda/run-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00034 | $0.00475 |
| Opus 5.5 | $0.00014 | $0.00190 |
| Sonnet 5.5 | $0.00007 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
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 2mo 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.
This is a copy
100% identical to run-tests — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Run Tests
Run the project's pytest suite with optional parallelism (pytest-xdist) and coverage.
Coverage targets are read from pyproject.toml's [tool.coverage.run] section,
so the same script works in any sibling repo without modification.
Usage
# Default: parallel + verbose (recommended)
bash .claude/skills/run-tests/scripts/test.sh -p
# Quick check: parallel + quiet
bash .claude/skills/run-tests/scripts/test.sh -p -q
# Full CI mode: parallel + coverage + xml report
bash .claude/skills/run-tests/scripts/test.sh --ci
# Specific test file
bash .claude/skills/run-tests/scripts/test.sh -p tests/test_socket_server.py
# Without parallelism (for debugging test ordering issues)
bash .claude/skills/run-tests/scripts/test.sh tests/test_rooms.py
# With coverage
bash .claude/skills/run-tests/scripts/test.sh -p -c
Options
| Flag | Short | Description |
|---|---|---|
--parallel |
-p |
Run with -n auto (pytest-xdist, uses all CPU cores) |
--coverage |
-c |
Enable coverage reporting to terminal |
--ci |
Full CI mode: parallel + coverage + XML report + verbose | |
--quick |
-q |
Quiet output (no verbose, no coverage) |
Extra arguments are passed through to pytest (e.g., -x for stop-on-first-failure, -k "pattern" for filtering).
When to Use Which Mode
- After code changes:
bash test.sh -p— fast parallel run, verbose output - Quick sanity check:
bash test.sh -p -q— minimal output - Before PR / release:
bash test.sh --ci— matches CI exactly - Debugging flaky test:
bash test.sh tests/test_flaky.py— sequential, single file
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 52 lines · 34 tokens per session scan A e45754b02a28
run-tests is a skill published in the GitHub repository agentculture/agenda (2 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 475 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to run-tests, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.