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 skills add pilinux/gorest --skill test-runnergit clone --depth 1 https://github.com/pilinux/gorestWrote 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/pilinux/gorest/test-runner)<a href="https://agentmods.dev/skills/pilinux/gorest/test-runner"><img src="https://agentmods.dev/badge/skills/pilinux/gorest/test-runner/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/pilinux/gorest/test-runner"><img src="https://agentmods.dev/badge/skills/pilinux/gorest/test-runner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00022 | $0.00264 |
| Opus 5.5 | $0.00009 | $0.00106 |
| Sonnet 5.5 | $0.00004 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
test-runner 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.
What it actually says
Test Runner
When to Use
- Validate changes with unit/integration tests or triage failing test runs.
Rules
- Use
source setTestEnv.shwhen environment variables are required. - Focus on the first actionable failure line and include package + test name.
- Prefer targeted test runs (
-run) over full-suite when iterating.
Commands
- Full suite (with test env):
source setTestEnv.sh && go test -v -cover ./... - Single package:
source setTestEnv.sh && go test -v -cover ./lib/... - Single test:
source setTestEnv.sh && go test -v -run TestHashPass ./lib/...
Output
- Result: pass or fail.
- Failures: package, test name, first actionable error lines.
- Next: 1-3 focused suggestions (narrow test, inspect file, add mock).
Related Skills
logs-repro-harness,linter-runner,db-infra-mocks
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 · 37 lines · 22 tokens per session scan A f0b1152e7f6a
test-runner is a skill published in the GitHub repository pilinux/gorest (506 stars, last pushed 7d ago), licensed MIT. It adds 22 tokens to every session and 264 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.
Other skills, from other repositories
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…
bubbletea-testing
Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm…
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.
functions-development
Build serverless Go or Python functions for Falcon Foundry apps. TRIGGER when user asks to "create a function", "write a serverless function", "build backend logic", runs foundry functions create, or needs help with FDK handler patterns, function testing, or collection integration from functions. Also TRIGGER when…
test-new-skill
Skill "test-new-skill" from dimetron/pi-go, covering test-new-skill, examples and guidelines.
go-testing
Write clear, fast, deterministic Go tests including mandatory repo integration tests (x/testkit) and app unit tests. Use when adding or fixing Go tests, implementing internal/repo or internal/app, designing table-driven tests, writing benchmarks, using testify, or improving coverage in this workspace. For…