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 terva-sh/terva --skill test-fixgit clone --depth 1 https://github.com/terva-sh/tervaWrote 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/terva-sh/terva/test-fix)<a href="https://agentmods.dev/skills/terva-sh/terva/test-fix"><img src="https://agentmods.dev/badge/skills/terva-sh/terva/test-fix/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/terva-sh/terva/test-fix"><img src="https://agentmods.dev/badge/skills/terva-sh/terva/test-fix.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.00017 | $0.00329 |
| Opus 5.5 | $0.00007 | $0.00132 |
| Sonnet 5.5 | $0.00003 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
test-fix 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.
This is a copy
100% identical to test-fix — 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
Test fix
When the user reports a failing test (or a test suite failure), work in this order. Resist the temptation to rewrite large chunks of code.
1. Reproduce
Run the failing test in isolation first. For Go: go test -run TestThing ./pkg/.... For Node: npm test -- --run TestThing. The
goal is a fast feedback loop, not the whole suite.
2. Read the failure carefully
- What was expected vs got?
- Which line of test code triggered the failure?
- Is it a logic error in the implementation, an outdated test expectation, or environmental drift (e.g. timezone, locale, file system case-sensitivity)?
3. Choose the smallest possible fix
- If the test is wrong → update the assertion only. Don't restructure.
- If the implementation is wrong → patch the smallest function that fixes the failing case. Avoid drive-by refactors.
- If the test depends on behaviour you need to change deliberately → ask the user before changing the assertion.
4. Re-run
The same isolated test, then the immediate suite, then the full test command if applicable. Stop the moment you see green; don't keep poking.
5. Report
Write 2–3 sentences: what was wrong, what changed, and which command verifies the fix. Include the diff inline.
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 · 44 lines · 17 tokens per session scan A d7190ae93b97
test-fix is a skill published in the GitHub repository terva-sh/terva (3 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 329 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 test-fix, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
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…
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.
code-review-pi
Review code for quality, run linters, check test coverage, fix issues, and enforce gates. Save the final report to ./specs/issues/003-code-review-pi/PROMPT.md. Use before committing changes.