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 jimmc414/claude-code-plugin-marketplace --skill test-with-examplesgit clone --depth 1 https://github.com/jimmc414/claude-code-plugin-marketplaceWrote 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/jimmc414/claude-code-plugin-marketplace/test-with-examples)<a href="https://agentmods.dev/skills/jimmc414/claude-code-plugin-marketplace/test-with-examples"><img src="https://agentmods.dev/badge/skills/jimmc414/claude-code-plugin-marketplace/test-with-examples/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/jimmc414/claude-code-plugin-marketplace/test-with-examples"><img src="https://agentmods.dev/badge/skills/jimmc414/claude-code-plugin-marketplace/test-with-examples.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.00023 | $0.00890 |
| Opus 5.5 | $0.00009 | $0.00356 |
| Sonnet 5.5 | $0.00005 | $0.00178 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
test-with-examples 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
test-with-examples
When to Use
- Clear, discrete input/output relationships
- Examples serve as specification
- Teaching or documenting behavior
- Regression testing
When NOT to Use
- Behavior too complex for examples
- Need property-based testing
- Examples would be exhaustive
The Pattern
Write tests as lists of (input, expected_output) pairs.
# Test cases as data
tests = [
(input1, expected1),
(input2, expected2),
(input3, expected3),
]
def run_tests(func, tests):
"""Run function on test cases."""
for inp, expected in tests:
result = func(inp)
assert result == expected, f"{func.__name__}({inp}) = {result}, expected {expected}"
print(f"All {len(tests)} tests pass.")
Example (from pytudes)
# lispytest.py - comprehensive test examples
lis_tests = [
("(quote (testing 1 (2.0) -3.14e159))", ['testing', 1, [2.0], -3.14e159]),
("(+ 2 2)", 4),
("(+ (* 2 100) (* 1 10))", 210),
("(if (> 6 5) (+ 1 1) (+ 2 2))", 2),
("(if (< 6 5) (+ 1 1) (+ 2 2))", 4),
("(define x 3)", None),
("x", 3),
("(+ x x)", 6),
("((lambda (x) (+ x x)) 5)", 10),
("(define fact (lambda (n) (if (<= n 1) 1 (* n (fact (- n 1))))))", None),
("(fact 10)", 3628800),
("(fact 50)", 30414093201713378043612608166064768844377641568960512000000000000),
]
# DocstringFixpoint.ipynb - rainfall tests
def test_rainfall():
assert 0/2 == rainfall([0, 0]), "no rain"
assert 5/1 == rainfall([5]), "one day"
assert 6/3 == rainfall([1, 2, 3]), "mean of several days"
assert 6/4 == rainfall([0, 1, 2, 3]), "non-integer mean"
assert 9/3 == rainfall([1, 2, -9, -100, 6]), "negative values ignored"
assert 7/5 == rainfall([1, 0, 2, 0, 4]), "zeros not ignored"
assert 8/3 == rainfall([1, 2, 5, -999, 404]), "values after -999 ignored"
return True
# Cryptarithmetic.ipynb - solver test examples
for solver in (solve, faster_solve):
assert "1 + 2 = 3" in set(solver("A + B = C"))
assert not set(solver("A + B = CDE")) # No solution
assert set(solver("A * B = CA")) == {
'5 * 3 = 15', '5 * 7 = 35', '4 * 6 = 24',
'8 * 6 = 48', '2 * 6 = 12', '5 * 9 = 45'
}
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 · 85 lines · 23 tokens per session scan A 034156e82624
test-with-examples is a skill published in the GitHub repository jimmc414/claude-code-plugin-marketplace (4 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 890 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-09-04.
Other skills, from other repositories
generate-file-name-gate
Emit the file-name gate into a consuming repository: a standalone bash checker plus its own test suite, with the casing rule, roots, and exemptions inlined from the resolved docs-naming configuration, and optionally the path-scoped rule file. The emitted pair carries no dependency on this plugin at run time. Refuses…
phpunit-migration-test-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
phpunit-test-adversarial-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
phpunit-test-team-reviewing
Use this skill when the user asks for a team-based, consensus, multi-reviewer, or red-team review of Shopware PHPUnit tests — trigger phrases like "team review these tests", "consensus review the tests in PR.
phpunit-unit-test-reviewing
Internal sub-skill. Do not auto-activate. Use only when explicitly invoked by name by another skill or agent.
phpunit-integration-to-unit-migrating
Use this skill ONLY when the user explicitly requests an audit, migration, or evaluation of whether a Shopware integration test belongs in the unit suite — trigger phrases like "audit integration tests", "migrate integration tests to unit", "is this an integration test or a unit test", "evaluate integration tests for…