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 agentmods add commands/evmts/tevm/update-soliditygit clone --depth 1 https://github.com/evmts/tevmWhat 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 | $0.00000 | $0.00539 |
| Opus 5 | $0.00000 | $0.00269 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
update-solidity 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 yesterday.
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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Solidity Versions
I need your help to update the Solidity compiler version support in the @tevm/solc package. This involves checking for new Solidity releases, using the version script to get their version hashes, and updating the appropriate files.
Steps:
-
First, let's do a smoke test with the last supported version to verify the script is working correctly.
- Check the
bundler-packages/solc/src/solcTypes.tsandbundler-packages/solc/src/solc.jsfiles to find the latest supported version. - Run the version script against that version to verify it works:
cd bundler-packages/solc && npm run solc:version <last_supported_version>
- Check the
-
Check what's the next unreleased version we need to add:
- Run the npm command to check the latest available solc version:
npm view solc versions --json - Identify the latest versions that aren't supported yet in our codebase.
- Run the npm command to check the latest available solc version:
-
For each new version, use our script to get the version hash:
cd bundler-packages/solc && npm run solc:version <new_version>- The output will be the version hash in the format:
v<version>+commit.<hash>
-
Update the following files in the project:
bundler-packages/solc/src/solcTypes.ts: Add the new version(s) to theSolcVersionstype unionbundler-packages/solc/src/solc.js: Add the new version hash(es) to thereleasesobject
-
Consider updating the
solcdependency in package.json if appropriate.
Please help me execute these steps to add support for any new Solidity compiler versions. Start with the smoke test to verify the script works with an already supported version before proceeding with adding new versions.
Example workflow:
- You find that 0.8.28 is our latest supported version.
- Run the smoke test:
cd bundler-packages/solc && npm run solc:version 0.8.28 - Check for newer versions:
npm view solc versions --json - Find that 0.8.29 and 0.8.30 are available but not supported.
- For each new version, get the hash:
npm run solc:version 0.8.29 - Update the appropriate files with the new version information.
- Suggest updating package.json dependencies if needed.
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.
- yesterday First seen · 37 lines · 0 tokens per session scan A adef1e6b0b32
update-solidity is a command 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 539 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-08-31.
Other commands, from other repositories
deslop
Remove AI-generated code slop from the current branch's changes.
triage
Triage Linear issue with comprehensive analysis.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
audit
Command "audit" from chohra-med/expo_boilerplate, covering invocation, checks and output.