Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/LuuOW/meridian-mcpnpx agentmods add skills/luuow/meridian-mcp/solidityWrote 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/luuow/meridian-mcp/solidity)<a href="https://agentmods.dev/skills/luuow/meridian-mcp/solidity"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/solidity.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.00054 | $0.01720 |
| Opus 5 | $0.00027 | $0.00860 |
| Sonnet 5 | $0.00011 | $0.00344 |
| Haiku 4.5 | $0.00005 | $0.00172 |
Grade A, and why
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 4d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
solidity
Production smart-contract authoring for EVM chains. Covers the full contract lifecycle: standards compliance, security patterns, gas optimisation, testing with Foundry, and deployment hardening.
Contract Structure
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.24;
import {IERC20} from "@openzeppelin/contracts/token/ERC20/IERC20.sol";
import {SafeERC20} from "@openzeppelin/contracts/token/ERC20/utils/SafeERC20.sol";
import {ReentrancyGuard} from "@openzeppelin/contracts/utils/ReentrancyGuard.sol";
import {Ownable} from "@openzeppelin/contracts/access/Ownable.sol";
contract FlashloanArb is ReentrancyGuard, Ownable {
using SafeERC20 for IERC20;
error InsufficientProfit(uint256 expected, uint256 got);
error UnauthorizedCaller(address caller);
event ArbExecuted(address indexed asset, uint256 profit, uint256 gasUsed);
address public immutable POOL; // Aave V3 Pool
address public immutable ROUTER; // Swap router
constructor(address _pool, address _router) Ownable(msg.sender) {
POOL = _pool;
ROUTER = _router;
}
modifier onlyPool() {
if (msg.sender != POOL) revert UnauthorizedCaller(msg.sender);
_;
}
}
Access Control Patterns
Prefer role-based over owner-only for anything beyond toy contracts.
import {AccessControl} from "@openzeppelin/contracts/access/AccessControl.sol";
contract Treasury is AccessControl {
bytes32 public constant OPERATOR = keccak256("OPERATOR");
bytes32 public constant EMERGENCY = keccak256("EMERGENCY");
constructor(address admin) {
_grantRole(DEFAULT_ADMIN_ROLE, admin);
}
function withdraw(address to, uint256 amount) external onlyRole(OPERATOR) { /*...*/ }
function pause() external onlyRole(EMERGENCY) { /*...*/ }
}
Reentrancy Defence
The 2016 DAO hack is still the most common class of exploit. Follow checks-effects-interactions, use ReentrancyGuard on every external-facing state-mutating function that calls untrusted addresses.
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.
- 4d ago First seen · 192 lines · 54 tokens per session scan A 25c9aa0f9b83
solidity is a skill published in the GitHub repository LuuOW/meridian-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 54 tokens to every session and 1,720 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-03.
Other skills, from other repositories
Smart Contract Testing
Smart contract testing with Hardhat, Foundry, and Brownie including unit tests, gas optimization, reentrancy checks, and fork testing.
token-analyzer
Analyze ERC20/ERC721/ERC1155 token implementations for non-standard behavior, fee-on-transfer mechanics, rebasing logic, blacklists, pausability, and integration risks. Use when reviewing protocols that interact with external tokens or implementing token-related features.
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.
nft-minting
NFT auto-minting toolkit: direct contract minting, OpenSea/SeaDrop public minting, competitive fast-mint raw-TX path, multi-wallet, scheduled minting, browser fallback, health checks, post-mint verification, and OpenSea listing. For hot/FCFS/max mints use fast-mint.mjs, NOT schedulemint/browser clicking. Available as…
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.
auditing-foundry-smart-contract-security
Pre-deployment security audit of Solidity smart contracts in a Foundry project. Combines static analysis (Slither, Aderyn), symbolic execution (Mythril), and property-based testing (forge fuzz + invariant tests with handlers) to catch reentrancy, access-control, oracle/price manipulation, and arithmetic bugs BEFORE…