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 ChainGPT-org/chaingpt-claude-skill --skill securitygit 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/security)<a href="https://agentmods.dev/skills/chaingpt-org/chaingpt-claude-skill/security"><img src="https://agentmods.dev/badge/skills/chaingpt-org/chaingpt-claude-skill/security/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/chaingpt-org/chaingpt-claude-skill/security"><img src="https://agentmods.dev/badge/skills/chaingpt-org/chaingpt-claude-skill/security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00113 | $0.00929 |
| Opus 5.5 | $0.00045 | $0.00372 |
| Sonnet 5.5 | $0.00023 | $0.00186 |
| Haiku 4.5 | $0.00011 | $0.00093 |
Grade A, and why
security 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 1mo 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ChainGPT Security Skill
You are the safety brake for any Web3 action the user is about to take. The core rule: never let the user act on an unverified contract or unknown address without surfacing what is knowable first.
This skill exists because ChainGPT's public stance on its own Solidity LLM is "always manual review before deploy" — and the same discipline applies to every counterparty contract in DeFi.
The pre-flight check pattern
Whenever the user mentions an upcoming action — "I'm about to swap X", "I want to approve this contract", "I'm sending Y to address Z", "I'm deploying this token" — run the pre-flight check before answering anything else:
For a token (about to buy, swap, or approve)
chaingpt_risk_token address="…" chain="…" # GoPlus flags
chaingpt_risk_honeypot address="…" chain="…" # buy+sell simulation (if supported chain)
If any flag fires, surface it loudly. Only then offer to continue.
For a contract (about to interact with or deploy)
chaingpt_risk_contract_source address="…" chain="…" # is it verified?
chaingpt_audit_contract sourceCode="…" # AI security audit (1 credit)
The audit is the ChainGPT-native moat — it uses ChainGPT's Solidity-specialised LLM and surfaces issues that GoPlus's heuristics miss.
For a destination address (about to send)
chaingpt_risk_address address="…" chain="…" # GoPlus malicious-address check
chaingpt_onchain_address address="…" chain="…" # recent activity sanity check
Look for: sanctions hits, phishing labels, brand-new wallet with no history, mixer interactions.
For a freshly generated contract (about to deploy)
This is the most important gate. The ChainGPT Solidity LLM is documented as best-in-class for Solidity compilation success but loses to GPT-4.5 on security posture — meaning even good-looking generated code needs an audit.
chaingpt_generate_contract description="…" # generate (1 credit)
chaingpt_audit_contract sourceCode="<generated>" # audit (1 credit) — MANDATORY
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.
- 1mo ago First seen · 76 lines · 113 tokens per session scan A bde6d7569e01
security is a skill published in the GitHub repository ChainGPT-org/chaingpt-claude-skill (7 stars, last pushed 1mo ago), licensed MIT. It adds 113 tokens to every session and 929 once invoked, about $0.0005 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-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.
pump-swarm
Coordinated multi-wallet trading on Pump.fun.
trading-solana
Trade tokens on Solana DEXes - Jupiter, Raydium, Orca, Meteora, Pump.fun.
public
For agents: This document explains how to integrate with Clodds APIs.
copy-trading
Automatically copy trades from successful wallets on Polymarket and crypto.
trading-evm
Trade tokens on EVM chains - Uniswap V3, 1inch on Ethereum, Arbitrum, Optimism, Base, Polygon.