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 PaulRBerg/foundry-template --skill solidity-codinggit clone --depth 1 https://github.com/PaulRBerg/foundry-templateWrote 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/paulrberg/foundry-template/solidity-coding)<a href="https://agentmods.dev/skills/paulrberg/foundry-template/solidity-coding"><img src="https://agentmods.dev/badge/skills/paulrberg/foundry-template/solidity-coding/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/paulrberg/foundry-template/solidity-coding"><img src="https://agentmods.dev/badge/skills/paulrberg/foundry-template/solidity-coding.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.00053 | $0.02039 |
| Opus 5.5 | $0.00021 | $0.00816 |
| Sonnet 5.5 | $0.00011 | $0.00408 |
| Haiku 4.5 | $0.00005 | $0.00204 |
Grade A, and why
solidity-coding 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 21d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solidity Coding
Write Solidity that compiles under the project's pinned toolchain, follows its conventions, and passes its lint gate.
Ground Rules
- Read
foundry.toml,remappings.txt, and the nearestAGENTS.mdbefore writing code. The pinnedsolcand the effective EVM version decide which features exist: transient storage andmcopyneed Cancun or later, andtransientstate variables also need solc 0.8.28 or later. Whenevm_versionis unset, Foundry's default applies; read it withforge config | grep evm_version. - Treat the defaults below as fallbacks. Existing code and repository instructions win; match the surrounding file when they disagree.
- Let
forge fmt, Solhint, and Prettier own formatting. Run them instead of hand-formatting.
References
- references/security-practices.md: read when a change touches access control,
external calls, hooks,
uncheckedarithmetic, token integrations, signatures, oracles, or account abstraction. - references/gas-optimization.md: read when optimizing gas, packing storage, using transient storage, or choosing between OpenZeppelin and Solady.
- references/event-design.md: read when adding or changing events, especially ones that indexers consume.
- references/upgrades-and-versioning.md: read when writing upgradeable contracts, changing storage layout, or shipping a new version beside a deployed one.
- references/onchain-metadata.md: read when implementing
tokenURIor onchain JSON/SVG metadata.
Conventions
Naming
| Element | Convention | Example |
|---|---|---|
| Contract, library, struct, enum, event | PascalCase | TokenVault |
| Interface | I + PascalCase |
ITokenVault |
| Function, variable, parameter | camelCase | withdrawableAmountOf |
| Constant, immutable | SCREAMING_SNAKE_CASE | MAX_FEE |
| Internal or private function, state var | Leading underscore | _balances, _update |
| Custom error | {Contract}_{Description} |
TokenVault_Overdraw |
| Type namespace library | Domain name | Vault.Position |
What ships with it
6 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.
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.
- 21d ago First seen · 207 lines · 53 tokens per session scan A 81c5c1cb1f72
solidity-coding is a skill published in the GitHub repository PaulRBerg/foundry-template (642 stars, last pushed 7d ago), licensed MIT. It adds 53 tokens to every session and 2,039 once invoked, about $0.0002 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-25.
Other skills, from other repositories
blockchain-expert
Expert-level blockchain, Web3, smart contracts, DeFi, and cryptocurrency development. Use when the user mentions Web3, smart contracts, DeFi, Ethereum, or Solidity, or when the task involves Blockchain Fundamentals, Web3 & DeFi, Smart Contract Security, or Gas Optimization.
web3-expert
Build production-ready Web3 applications including smart contracts, dApps, DeFi protocols, and decentralized storage solutions. Use when the user mentions Web3, smart contracts or Solidity, dApps, DeFi protocols, ethers.js or web3.js, IPFS, or on-chain integration with Ethereum-compatible networks.
ethereum-development
Production-grade Ethereum/EVM development workflow for smart contracts, dApps, transactions, clients, gas optimization, testing, security review, deployment, verification, monitoring, and incident response across Foundry, Hardhat, Solidity, TypeScript, viem, ethers, wagmi, and common EVM networks.
solidity-language-docs
Solidity 0.8.36 — smart contracts, types, functions, modifiers, events, inheritance, libraries, assembly, ABI.
Web3 & Blockchain Development
Production-grade Web3 development with Solidity smart contracts, ethers.js/web3.js integration, DApp architecture, security patterns, and AI-enhanced blockchain development (ChatWeb3, Aider + Gemini 2024).
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.