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/chaingpt-org/chaingpt-claude-skill/deploynpx skills add ChainGPT-org/chaingpt-claude-skill --skill deploygit clone --depth 1 https://github.com/ChainGPT-org/chaingpt-claude-skillWrote 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/chaingpt-org/chaingpt-claude-skill/deploy)<a href="https://agentmods.dev/skills/chaingpt-org/chaingpt-claude-skill/deploy"><img src="https://agentmods.dev/badge/skills/chaingpt-org/chaingpt-claude-skill/deploy.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.00127 | $0.01371 |
| Opus 5 | $0.00063 | $0.00685 |
| Sonnet 5 | $0.00025 | $0.00274 |
| Haiku 4.5 | $0.00013 | $0.00137 |
Grade A, and why
deploy 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 6d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ChainGPT Deploy Skill
You orchestrate Solidity-contract deployment to real mainnet chains through the ChainGPT plugin. This skill is mainnet-first by design — testnet is an opt-in via the network parameter, never the default behavior.
The plugin is custody-free: it builds an unsigned transaction object and returns it. The user signs and broadcasts via their own wallet (MetaMask, Rabby, hardware wallet, ERC-4337 smart account, WalletConnect). Never ask the user for a private key. Never accept one in a tool argument.
The mandatory pipeline
chaingpt_generate_contract (optional — if generating from description)
│
▼
chaingpt_audit_contract ← MANDATORY for mainnet. Costs 1 credit. Never skip.
│
▼
chaingpt_deploy_compile ← solc 0.8.x, returns bytecode + ABI
│
▼
chaingpt_deploy_estimate ← gas + USD cost on the chosen mainnet
│
▼
chaingpt_deploy_build_tx ← MAINNET REFUSES unless acknowledgeMainnet: true
│
▼
[user signs externally + broadcasts]
│
▼
chaingpt_deploy_verify ← submit source to Etherscan v2 multichain
│
▼
chaingpt_deploy_verify_status ← poll until ✓ Pass — Verified
Hard rules for mainnet
- Never call
chaingpt_deploy_build_txwith a mainnet network andacknowledgeMainnet=trueuntil you have surfaced the audit report to the user. If the audit raised any high-severity finding, refuse to proceed until the user explicitly waives it. - Always surface the estimated cost in USD before the build-tx step. Pull from
chaingpt_deploy_estimateand convert via the current native-coin price. - Echo the constructor args back to the user in plain English before the build-tx step. ("You're about to deploy
MyTokenwith name='X', symbol='Y', initialSupply=1,000,000 * 10**18 to mainnet Ethereum. Confirm?") - Echo the deployer address back and remind the user it must be the wallet they control.
- Default to testnet only when the user explicitly says "test", "testnet", "dry run", or names a testnet chain (sepolia, base-sepolia, etc.). Anything else is mainnet.
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.
- 6d ago First seen · 88 lines · 127 tokens per session scan A 4534521e4915
deploy is a skill published in the GitHub repository ChainGPT-org/chaingpt-claude-skill (16 stars, last pushed 6d ago), licensed MIT. It adds 127 tokens to every session and 1,371 once invoked, about $0.0006 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
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.
fork-test
Generate Foundry fork tests for contracts requiring integration testing against real on-chain state.
unit-test
Generate Foundry unit tests (concrete + fuzz) for a contract following our established conventions and patterns.
smoke-test
Generate Foundry smoke tests that validate deployment health using DeployManager/Resolver against real on-chain state with pending governance applied.
verify-deployment-pr
Verifies a POST-EXECUTION mainnet (or other network) smart-contract deployment PR for this repo: confirms every deployed contract is listed in the PR description, that the on-chain verified source (and its dependencies) matches the codebase via sol2uml diff, that constructor args and the initialize tx match the…