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 Kerliula/ship-me --skill test-megit clone --depth 1 https://github.com/Kerliula/ship-meWrote 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/kerliula/ship-me/test-me)<a href="https://agentmods.dev/skills/kerliula/ship-me/test-me"><img src="https://agentmods.dev/badge/skills/kerliula/ship-me/test-me.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.00104 | $0.01937 |
| Opus 5 | $0.00052 | $0.00968 |
| Sonnet 5 | $0.00021 | $0.00387 |
| Haiku 4.5 | $0.00010 | $0.00194 |
Grade A, and why
test-me scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
endpoints, matching what was manually proven with curl in verify-me. How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Me — Write Tests That Earn Their Place
Your job is to write tests that would actually catch a real bug if one showed up. Not tests that exist to make a coverage number go up. A test that can never fail is worse than no test — it's false confidence.
Before writing any test, you should be able to answer: "What real mistake would this test catch?" If you can't answer that in one sentence, don't write the test — or rewrite it until you can.
Input
You need the /verify-me output: the markdown file at
docs/verification/<topic>.md (or wherever the developer points you).
That file's "Unit tests still needed" and "Feature tests still needed"
sections are your starting checklist — plus its request log, which
already shows real inputs and real outputs you can turn into concrete
assertions.
Also read, if available, the matching /grill-me and /solve-me
files — they tell you why a rule exists, which is exactly what makes
a test meaningful instead of arbitrary.
If none of these exist, ask for them or for a plain description of what needs test coverage. Don't invent test cases from guessing what the code probably does.
Step 1 — Learn how this project already tests things
Before writing anything, look at how existing tests in this codebase are structured: which test framework, how the database is reset between tests, how factories are used, naming conventions, folder layout (unit vs. feature), how HTTP requests are made in tests, how auth is set up in tests. Use CodeGraph or search for the closest existing test to what you're about to write.
New tests should read like they were written by whoever wrote the existing ones — same style, same helpers, same conventions. Don't introduce a new testing pattern when the project already has one.
Step 2 — Turn the checklist into real test cases
For every item in verify-me's "tests still needed" lists, write down, in one line, the real-world rule or scenario it protects — pulling this from the grill-me/solve-me docs when possible. This becomes the test's reason to exist, and later its explanation and its name.
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.
- 7d ago First seen · 202 lines · 104 tokens per session scan A 7f2eef35e2fa
test-me is a skill published in the GitHub repository Kerliula/ship-me (1 stars, last pushed 9d ago), licensed MIT. It adds 104 tokens to every session and 1,937 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
review-ugc-render
Mandatory pre-publish review gate for a UGC video render. Transcribes the finished render's AUDIO with Whisper and word-diffs it against the approved spoken script, then gates setfinalrender — blocking a render whose generated audio mis-voices a word (e.g. the approved "human-vetted" spoken as "human witted"), drops…
test-generator
A test-writing helper that creates unit or integration tests from the code's actual behavior and contracts. Unit tests check small pieces of code, while integration tests check how real components work together.
testing-r-packages
Best practices for writing R package tests using testthat version 3+. Use when writing, organizing, or improving tests for R packages. Covers test structure, expectations, fixtures, snapshots, mocking, and modern testthat 3 patterns including self-sufficient tests, proper cleanup with withr, and snapshot testing.
r-package-development
R package development with devtools, testthat, and roxygen2. Use when the user is working on an R package, running tests, writing documentation, or building package infrastructure.
coverage-enhancer
Analyze existing test suites and source code to suggest additional unit tests that improve test coverage. Use this skill when working with test files and source code to identify untested code paths, missing edge cases, uncovered branches, untested error conditions, and gaps in test coverage. Supports major testing…
111-java-maven-dependencies
Use when you need to add or evaluate Maven dependencies that improve code quality or domain modeling — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), or money and currency support (JavaMoney) — and want a…