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/zaxbyhub/opencode-swarm/running-testsnpx skills add ZaxbyHub/opencode-swarm --skill running-testsgit clone --depth 1 https://github.com/ZaxbyHub/opencode-swarmWrote 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/zaxbyhub/opencode-swarm/running-tests)<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/running-tests"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/running-tests.svg" alt="Measured on agentmods" 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.00052 | $0.00264 |
| Opus 5 | $0.00026 | $0.00132 |
| Sonnet 5 | $0.00010 | $0.00053 |
| Haiku 4.5 | $0.00005 | $0.00026 |
Grade A, and why
running-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 6d 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.
What it actually says
Running Tests
Use this adapter when executing tests in opencode-swarm. For writing tests, load $writing-tests instead.
Read, in order:
AGENTS.md.opencode/skills/running-tests/SKILL.md
Codex-specific execution notes:
- Use the available shell execution tool for
bun --smol testand PowerShell/bash loops. - Prefer
rgand repo scripts to rediscover exact commands from source. - Capture long output to a temp file when needed and report the important tail or failure lines.
- Do not use broad OpenCode
test_runnerscopes for repo validation. - On Windows, if Bun reports
EPERMafter a forced dependency refresh, rerun the same focused command with approved/elevated access before treating it as a test failure.
Default rule: one source file or one explicit test file can be targeted narrowly; multiple files or directories should use shell loops or the documented tier commands.
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.
- 6d ago First seen · 25 lines · 52 tokens per session scan A 03c6eabac322
running-tests is a skill published in the GitHub repository ZaxbyHub/opencode-swarm (463 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 264 once invoked, about $0.0003 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
ux-create-manifest
Create the initial Product UX Bible for an existing web or full-screen web app by deeply auditing the repository, using sub-agents when available, and generating docs/ux manifests, schemas, budgets, surface maps, action taxonomy, and design-token policies from observed code.
ux-principal
Principal UX architect skill for deciding WHERE a UI feature belongs, before it is implemented. Reads and maintains docs/ux manifests, classifies the feature, decides placement, navigation, surface, action hierarchy and complexity budgets, and produces a precise implementation brief without coding unless explicitly…
full_unpackd_rep
Use when the task is to unpack a local reference repository into a Chinese structural topic page, update site navigation, stamp dates, and leave behind a reusable deconstruction note for the repo.
loloop
Use when a task should advance through repeated plan-driven loop cycles for an engineering project, paper, or long-running repo change. loloop wraps the official /loop idea with the repo's loop-in-loop method: read the current plan, inspect prior evolution notes, execute the current iteration, write a new evolution…
keyword-site-topic
Use when the task is to take a user-provided keyword, search the web for relevant articles, summarize and cluster the findings, choose the most appropriate existing site/ topic or hotspot page in this project, and draft a publish-ready Markdown article with explicit image prompt placeholders or Mermaid notes.
auto-dot-claude
Use when a project needs a standard .claude workspace initialized or repaired incrementally. This skill audits the existing .claude folder, adds missing files and directories without overwriting existing rules/skills/settings, and can optionally evolve the structure over time for the current project.