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 san-npm/skills-ws --skill solidity-devgit clone --depth 1 https://github.com/san-npm/skills-wsWrote 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/san-npm/skills-ws/solidity-dev)<a href="https://agentmods.dev/skills/san-npm/skills-ws/solidity-dev"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/solidity-dev/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/san-npm/skills-ws/solidity-dev"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/solidity-dev.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.00064 | $0.00417 |
| Opus 5 | $0.00032 | $0.00209 |
| Sonnet 5 | $0.00013 | $0.00083 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
solidity-dev 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 5d 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
Solidity Development — Foundry & Hardhat
Reference guide
Read only the references needed for the current request:
- 1. Project Setup: references/1-project-setup.md
- 2. Foundry Commands Reference: references/2-foundry-commands-reference.md
- 3. Common Solidity Patterns: references/3-common-solidity-patterns.md
- 4. Testing: references/4-testing.md
- 5. Deployment Scripts: references/5-deployment-scripts.md
- 6. Environment & Key Management: references/6-environment-key-management.md
- 7. Verification: references/7-verification.md
- 8. Gas Optimization Cheat Sheet: references/8-gas-optimization-cheat-sheet.md
- 9. Solidity Style Guide: references/9-solidity-style-guide.md
- 10. Common Gotchas: references/10-common-gotchas.md
- 11. Security & Audit Toolchain (expected for paid work): references/11-security-audit-toolchain-expected-for-paid-work.md
What ships with it
12 files 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.
- agents/openai.yaml 195 B
- references/1-project-setup.md 9.0 KB
- references/10-common-gotchas.md 2.6 KB
- references/11-security-audit-toolchain-expected-for-paid-work.md 4.3 KB
- references/2-foundry-commands-reference.md 2.0 KB
- references/3-common-solidity-patterns.md 4.0 KB
- references/4-testing.md 3.7 KB
- references/5-deployment-scripts.md 3.8 KB
- references/6-environment-key-management.md 1.7 KB
- references/7-verification.md 679 B
- references/8-gas-optimization-cheat-sheet.md 6.3 KB
- references/9-solidity-style-guide.md 1.4 KB
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.
- 5d ago First seen · 22 lines · 64 tokens per session scan A 3a8f91e7aa7c
solidity-dev is a skill published in the GitHub repository san-npm/skills-ws (2 stars, last pushed 5d ago), licensed MIT. It adds 64 tokens to every session and 417 once invoked, about $0.0003 per session on Opus 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-07.
Other skills, from other repositories
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
building-pydantic-ai-agents
Build AI agents with Pydantic AI — tools, capabilities (including on-demand loading), structured output, streaming, testing, and multi-agent patterns. Use when the user mentions Pydantic AI, imports pydanticai, or asks to build an AI agent, add tools/capabilities, defer capability loading, stream output, define agents…
prompt-proximity-architecture
Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited…
software-test-creation
Write failing tests for a TDD slice based on acceptance criteria and codebase conventions. Use when the "red" phase of red-green-refactor requires tests that define expected behavior before implementation exists. Discovers codebase test conventions first, writes test files that compile or parse but fail because the…
tevm
Build, simulate, test, fork, and debug EVM transactions in TypeScript with tevm 1.0.0-rc.151. Use for in-process EVM scripts, typed Solidity imports, lazy mainnet or OP-stack forks, direct account and storage setup, viem-compatible contract actions, Vitest EVM tests, traces, and transaction simulation.
verification-protocol
How to prove a hypothesis is TRUE or FALSE using Move unit tests.