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/jkaninda/okapi-skills/testingnpx skills add jkaninda/okapi-skills --skill testinggit clone --depth 1 https://github.com/jkaninda/okapi-skillsWrote 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/jkaninda/okapi-skills/testing)<a href="https://agentmods.dev/skills/jkaninda/okapi-skills/testing"><img src="https://agentmods.dev/badge/skills/jkaninda/okapi-skills/testing.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 | $0.00000 | $0.01332 |
| Opus 5 | $0.00000 | $0.00666 |
| Sonnet 5 | $0.00000 | $0.00266 |
| Haiku 4.5 | $0.00000 | $0.00133 |
Grade A, and why
testing 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Okapi Testing
Two pieces: okapi's test server / test context, and the okapitest package's fluent request builder and assertions.
Test Server
func TestBooks(t *testing.T) {
server := okapi.NewTestServer(t) // random free port, stopped via t.Cleanup
server.Get("/books", GetBooksHandler) // *TestServer embeds *Okapi — register as usual
okapitest.GET(t, server.BaseURL+"/books").
ExpectStatusOK().
ExpectBodyContains("The Go Programming Language")
}
Constructors:
okapi.NewTestServer(t TestingT) *TestServer // new Okapi instance
okapi.NewTestServerOn(t TestingT, port int) *TestServer // fixed port
okapi.NewTestServerWithOkapi(t TestingT, o *Okapi) *TestServer // wrap a configured instance
okapi.DefaultTestServer(t TestingT) *TestServer // okapi.Default() based
*TestServer embeds *Okapi and adds BaseURL string.
TestingT is satisfied by *testing.T (Helper, Cleanup, Errorf, Fatalf), so a custom harness can be plugged in.
Starting an already-built app for a test:
o := buildApp() // your production wiring
baseURL := o.StartForTest(t) // starts and registers cleanup
addr := o.WaitForServer(2 * time.Second) // block until ready (when starting manually)
Test Context (unit-testing a handler directly)
ctx, rec := okapi.NewTestContext("POST", "/books", strings.NewReader(`{"name":"Go"}`))
ctx.Request().Header.Set("Content-Type", "application/json")
if err := CreateBookHandler(ctx); err != nil {
t.Fatal(err)
}
okapitest.FromRecorder(t, rec).
ExpectStatusCreated().
ExpectJSONPath("name", "Go")
NewTestContext builds its own in-memory request and httptest.ResponseRecorder without a full Okapi engine.
Fluent Requests (okapitest)
import "github.com/jkaninda/okapi/okapitest"
okapitest.GET(t, url).
Header("Authorization", "Bearer "+token).
ExpectStatusOK().
ExpectContentType("application/json").
ExpectBodyContains("Go Programming")
okapitest.POST(t, url).
JSONBody(map[string]any{"name": "Book"}).
ExpectStatusCreated()
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.
- 4d ago First seen · 178 lines · 0 tokens per session scan A 18c05e145bed
testing is a skill published in the GitHub repository jkaninda/okapi-skills (3 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,332 tokens. 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.
Other skills, from other repositories
test-commander
Generate unit, integration, E2E, and visual regression tests following the Testing Trophy methodology (80% integration). Covers Vitest/Jest, Testing Library, Playwright, MSW for API mocking, snapshot strategy, visual regression (Chromatic/Percy/Playwright), test factories with Faker, and CI sharding. Use when user…
zig-testing
Zig testing skill for writing and running tests. Use when using zig build test, writing comptime tests, using test filters, working with test allocators to detect leaks, or using Zig's built-in fuzz testing (0.14+). Activates on queries about Zig tests, zig test, zig build test, comptime testing, test allocators, Zig…
kernel-testing
Linux kernel testing skill for KUnit, kselftest, syzkaller, and LTP. Use when writing KUnit tests, running kselftest harness, configuring syzkaller fuzzing, or integrating KernelCI. Activates on queries about kunittestsuite, kunit.py, kselftest, syzkaller, kcov, or Linux Test Project.
test-writer
Generate or extend comprehensive test suites — unit, integration, E2E, and contract tests — for any language or framework. Use when the user asks to write tests, add coverage, test a specific function or module, set up a test framework, generate test cases from code, or validate behaviour with automated tests.
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
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…