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 skills/protokol/solidity-typescript-hardhat-template/deploy-checknpx skills add protokol/solidity-typescript-hardhat-template --skill deploy-checkgit clone --depth 1 https://github.com/protokol/solidity-typescript-hardhat-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/protokol/solidity-typescript-hardhat-template/deploy-check)<a href="https://agentmods.dev/skills/protokol/solidity-typescript-hardhat-template/deploy-check"><img src="https://agentmods.dev/badge/skills/protokol/solidity-typescript-hardhat-template/deploy-check.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 | $0.00017 | $0.00415 |
| Opus 5 | $0.00009 | $0.00208 |
| Sonnet 5 | $0.00003 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
deploy-check 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.
What it actually says
/deploy-check
Run a pre-deployment checklist to verify everything is ready for deployment.
Instructions
Perform each step in order and report results:
1. Compile Contracts
Run npm run compile and verify all contracts compile without errors or warnings.
2. Run Tests
Run npm run test and verify all tests pass.
3. Run Coverage
Run npm run coverage and report the coverage summary. Flag any contracts with low coverage.
4. Lint Checks
Run npm run solhint and npm run lint:check to verify no linting issues.
5. Format Check
Run npm run format:check and npm run sol:format:check to verify formatting is consistent.
6. Review Ignition Modules
Read each file in ignition/modules/ and verify:
- All constructor parameters have sensible defaults
- Parameter names match what the contract expects
- Owner/deployer is set via
m.getAccount(0)
7. Check Network Configuration
Read hardhat.config.ts and verify:
- Target network is configured
- Required environment variables are documented in
.env.example
8. Summary Report
Output a summary table:
| Check | Status | Notes |
|---|---|---|
| Compilation | PASS/FAIL | |
| Tests | PASS/FAIL | X/Y passing |
| Coverage | PASS/WARN | XX% |
| Solhint | PASS/FAIL | |
| ESLint | PASS/FAIL | |
| Formatting | PASS/FAIL | |
| Ignition Modules | PASS/WARN | |
| Network Config | PASS/WARN |
Flag any FAIL or WARN items with recommended fixes.
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 · 66 lines · 17 tokens per session scan A 6544438bf5af
deploy-check is a skill published in the GitHub repository protokol/solidity-typescript-hardhat-template (48 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 415 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
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).
Smart Contract Testing
Smart contract testing with Hardhat, Foundry, and Brownie including unit tests, gas optimization, reentrancy checks, and fork testing.
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.
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.
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.
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.