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 verify-with-inline-testsgit 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/verify-with-inline-tests)<a href="https://agentmods.dev/skills/jimmc414/claude-code-plugin-marketplace/verify-with-inline-tests"><img src="https://agentmods.dev/badge/skills/jimmc414/claude-code-plugin-marketplace/verify-with-inline-tests/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/verify-with-inline-tests"><img src="https://agentmods.dev/badge/skills/jimmc414/claude-code-plugin-marketplace/verify-with-inline-tests.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.00027 | $0.00674 |
| Opus 5.5 | $0.00011 | $0.00270 |
| Sonnet 5.5 | $0.00005 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
verify-with-inline-tests 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
verify-with-inline-tests
When to Use
- Tests should be near the code
- Tests serve as documentation
- Single-file modules
- Quick verification during development
When NOT to Use
- Large test suites
- Need test isolation
- CI/CD expects tests in specific location
The Pattern
Include tests in the module, run them when module is executed directly.
def my_function(x):
"""Do something useful."""
return x * 2
def test():
"""Run all tests."""
assert my_function(2) == 4
assert my_function(0) == 0
assert my_function(-1) == -2
print("All tests pass.")
if __name__ == '__main__':
test()
Example (from pytudes)
# sudoku.py - structural invariant tests
def test():
"""A set of tests that must pass."""
assert len(squares) == 81
assert len(unitlist) == 27
assert all(len(units[s]) == 3 for s in squares)
assert all(len(peers[s]) == 20 for s in squares)
assert units['C2'] == [
['A2', 'B2', 'C2', 'D2', 'E2', 'F2', 'G2', 'H2', 'I2'],
['C1', 'C2', 'C3', 'C4', 'C5', 'C6', 'C7', 'C8', 'C9'],
['A1', 'A2', 'A3', 'B1', 'B2', 'B3', 'C1', 'C2', 'C3']
]
print('All tests pass.')
if __name__ == '__main__':
test()
solve_all(open("sudoku-easy50.txt"), "easy")
solve_all(open("sudoku-top95.txt"), "hard")
# spell.py - comprehensive unit tests
def unit_tests():
assert correction('speling') == 'spelling'
assert correction('korrectud') == 'corrected'
assert correction('bycycle') == 'bicycle'
assert words('This is a TEST.') == ['this', 'is', 'a', 'test']
assert len(WORDS) == 32198
assert sum(WORDS.values()) == 1115585
assert 0.07 < P('the') < 0.08
return 'unit_tests pass'
if __name__ == '__main__':
print(unit_tests())
spelltest(Testset(open('spell-testset1.txt')))
Key Principles
if __name__ == '__main__': Only run tests when executed directly- Assert for tests: Simple, clear assertions
- Print success: Confirm tests ran
- Test structure first: Validate data structures built correctly
- Tests as examples: Show how functions are used
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 · 83 lines · 27 tokens per session scan A 87d81cd3c121
verify-with-inline-tests is a skill published in the GitHub repository jimmc414/claude-code-plugin-marketplace (4 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 674 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-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-test-adversarial-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…