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 trustless-agentsgit 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/trustless-agents)<a href="https://agentmods.dev/skills/chaingpt-org/chaingpt-claude-skill/trustless-agents"><img src="https://agentmods.dev/badge/skills/chaingpt-org/chaingpt-claude-skill/trustless-agents/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/trustless-agents"><img src="https://agentmods.dev/badge/skills/chaingpt-org/chaingpt-claude-skill/trustless-agents.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.00116 | $0.00511 |
| Opus 5 | $0.00058 | $0.00255 |
| Sonnet 5 | $0.00023 | $0.00102 |
| Haiku 4.5 | $0.00012 | $0.00051 |
Grade A, and why
trustless-agents 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 10d 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
ERC-8004 Trustless Agents skill
ERC-8004 (draft EIP) gives AI agents a portable on-chain identity + reputation:
the Identity Registry is an ERC-721 ("AgentIdentity") deployed as a singleton
at the vanity address 0x8004A169… across many chains (verified on Base
mainnet). An agent's tokenURI points to an AgentCard describing what it does,
its endpoints (A2A/MCP), trust models, and x402 support.
Tools
| Tool | Purpose |
|---|---|
chaingpt_erc8004_resolve_agent |
Resolve agentId → owner + decoded AgentCard (handles data: and https/ipfs tokenURIs). Read-only. |
chaingpt_erc8004_registries |
The canonical Identity + Reputation registry addresses and the chains they're on. |
chaingpt_erc8004_agentcard |
Generate a registration-v1 AgentCard JSON (name, services, supportedTrust, x402Support) to host at the tokenURI / /.well-known/agent-card.json. Optionally emits the data: URI form. |
chaingpt_erc8004_resolve_agent agentId=0 chain=base → the Genesis Agent.
Scope
Read + scaffolding are shipped and verified. The write path (register / giveFeedback / validation) is intentionally deferred: ERC-8004 is a draft whose write ABIs (especially the Validation Registry) are still being revised, so we don't ship unverified identity/reputation-mutating calldata. Generate the AgentCard here, then register via the project's reference contracts once the write ABI is final.
Reads use a public-RPC fallback chain; set BASE_RPC_URL for reliability.
0 ChainGPT credits.
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.
- 10d ago First seen · 35 lines · 0 tokens per session scan A 060438b28291
trustless-agents is a skill published in the GitHub repository ChainGPT-org/chaingpt-claude-skill (16 stars, last pushed 10d ago), licensed MIT. It adds 116 tokens to every session and 511 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.
talos-action-development
Develop, modify, review, and maintain standalone Talos actions in contracts/tasks/actions, including chain guardrails, contract bindings, transaction safety, schedules, action catalogues, and Talos documentation. Use when adding an action, changing an action’s behavior or parameters, updating a Talos schedule, or…
web3-bug-classes
Complete reference for all 10 DeFi smart contract bug classes. Use this when hunting for specific vulnerability types, need attack patterns for accounting desync, access control, incomplete path, off-by-one, oracle manipulation, ERC4626 vaults, reentrancy, flash loans, signature replay, or proxy/upgrade bugs.
web3-methodology-research
External research synthesis from Trail of Bits, SlowMist, ConsenSys, Immunefi, and Cyfrin. Use this for advanced audit methodology, Echidna/Medusa fuzzing setup, Slither custom detector writing, attack pattern deep dives, or the 4-phase learning roadmap.
web3-poc-foundry
Complete Foundry PoC writing guide + all cheatcodes + DeFiHackLabs reproduction patterns. Use this when building a proof of concept exploit, setting up a fork test, using Foundry cheatcodes, or reproducing a known DeFi hack for learning.