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 conformance-triagegit 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/conformance-triage)<a href="https://agentmods.dev/skills/evmts/tevm/conformance-triage"><img src="https://agentmods.dev/badge/skills/evmts/tevm/conformance-triage.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.00000 | $0.00168 |
| Opus 5 | $0.00000 | $0.00084 |
| Sonnet 5 | $0.00000 | $0.00034 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
conformance-triage 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 today.
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
Diagnose a native conformance failure
Input: a failing Guillotine Mini fixture identifier and optional suite.
- Locate the native fixture in
../guillotine-miniand reproduce it with the pinned Zig target. Do not regenerate unrelated fixtures. - Compare its native trace with the fixture's named reference. Identify whether the failure belongs to Guillotine Mini execution, Voltaire state/primitives, ZEVM RPC, or TEVM transport.
- Write a diagnosis and concrete regression/fix plan under
factory/queue/conformance/. Include the exact fixture, command, observed mismatch, owning repository, and files that need changes. - Do not change sibling repositories from this factory action. Their patches need a candidate with an explicit write set in the owning repository. Do not commit, publish, or mark a failing assertion skipped.
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.
- today First seen · 9 lines · 0 tokens per session scan A 378d4bb7a495
conformance-triage is a skill published in the GitHub repository evmts/tevm (446 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 168 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
forge-bugfix
A structured bug-fixing process that investigates one problem at a time, records evidence, tests the fix, and waits for the user's final acceptance.
solidity
Solidity smart-contract authoring authority — ERC20/ERC721/ERC1155 token standards, reentrancy guards, access control, gas optimisation, upgradeable proxies, Foundry testing, fuzzing, invariant checks, and production contract security for EVM chains.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.