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 evmts/tevm --skill raise-coveragegit clone --depth 1 https://github.com/evmts/tevmWrote 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/evmts/tevm/raise-coverage)<a href="https://agentmods.dev/skills/evmts/tevm/raise-coverage"><img src="https://agentmods.dev/badge/skills/evmts/tevm/raise-coverage/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/evmts/tevm/raise-coverage"><img src="https://agentmods.dev/badge/skills/evmts/tevm/raise-coverage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.00331 |
| Opus 5.5 | $0.00000 | $0.00132 |
| Sonnet 5.5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
raise-coverage 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.
What it actually says
Raise a package's coverage floor
Input: a package directory (for example packages/txpool) and optionally a
target line-coverage percentage. Without a target, raise every threshold by
five points or to what the new run measures, whichever is lower.
- Run the package's coverage (
vitest run --coveragein the package; never the baretestscript, which is interactive). Readcoverage/coverage-summary.jsonand list the files with the lowest line and branch coverage. - For each of the lowest files, read the implementation and write the
missing cases in the colocated
<name>.spec.ts. Tests use real objects:createTevmNode(),createMemoryClient(), real compiled contracts from@tevm/test-utils, recorded RPC snapshots. Novi.mock, novi.fnon tevm objects (CLAUDE.md, testing conventions). - Cover error paths through the real error classes in
@tevm/errors: assert on the error name and message, not on a mock being called. - Re-run coverage. Raise
thresholdsin the package'svitest.config.tsto the measured values rounded down to two decimals, and never above what the run measured. Do not touchautoUpdate. - Run the package's full test suite and its typecheck. Every test passes.
Do not change implementation files to make coverage easier. If a file is unreachable dead code, report it in your final message instead of testing it.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 24 lines · 0 tokens per session scan A 57f2e835d242
raise-coverage is a skill published in the GitHub repository evmts/tevm (449 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 331 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-09-07.
Other skills, from other repositories
typescript
TypeScript strict mode with eslint and jest.
foundry-testing
Write and debug Foundry tests and Solidity scripts. Use when writing unit, fuzz, fork, or invariant tests, writing bulloak BTT .tree specs (Branching Tree Technique), using cheatcodes, benchmarking gas, measuring coverage, writing deploy scripts, or working in tests/ or script/.
jest-unit
Unit testing skill using Jest for TypeScript and JavaScript, covering mocking, spies, snapshots, coverage, async testing, and custom matchers.
Jasmine Testing
BDD-style JavaScript testing with Jasmine covering spies, async patterns, custom matchers, clock manipulation, and comprehensive test organization for frontend and Node.js applications.
vitest-skill
Generates Vitest tests in JavaScript/TypeScript with Vite-native speed. Jest-compatible API with ESM support and HMR. Use when user mentions "Vitest", "vi.mock", "vitest.config". Triggers on: "Vitest", "vi.mock", "vi.fn", "Vite test", "vitest config".
jest
Jest testing best practices for JavaScript and TypeScript applications, covering test structure, mocking, and assertion patterns.