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 DongDuong2001/pudo-code-system --skill smart-contractsgit clone --depth 1 https://github.com/DongDuong2001/pudo-code-systemWrote 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/dongduong2001/pudo-code-system/smart-contracts)<a href="https://agentmods.dev/skills/dongduong2001/pudo-code-system/smart-contracts"><img src="https://agentmods.dev/badge/skills/dongduong2001/pudo-code-system/smart-contracts.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.00000 | $0.00424 |
| Opus 5 | $0.00000 | $0.00212 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
smart-contracts 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 7d 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
Web3 & Smart Contracts PUDO Checklist
1. PLAN (Architecture & Strategy)
- Protocol Design: Define contract architecture (e.g., Monolithic vs. Proxy/Upgradable vs. Diamond pattern).
- Tokenomics: Map out value flow, minting, burning, and pausing capabilities (ERC20/ERC721/ERC1155).
- Access Control: Plan roles (Owner, Admin, Minter) and multisig requirements.
- Gas Economics: Architect data structures to minimize storage operations (packing variables).
2. UNDERSTAND (Context & Auditing)
- Dependencies: Validate versions of inherited libraries (e.g., OpenZeppelin Contracts).
- External Interactions: Map all calls to external, untrusted contracts (risk of reentrancy).
- State Changes: Understand the lifecycle of state variables over the contract's active period.
3. DEVELOP (Implementation)
- CEI Pattern: STRICTLY adhere to Checks-Effects-Interactions pattern for all state-mutating functions.
- Modifiers: Use modifiers for access control and validation logically without bloating gas.
- Events: Emit events for all significant state changes for off-chain indexing.
- Testing: Achieve 100% branch test coverage using Foundry or Hardhat. Include fuzz testing and invariant testing.
4. OPTIMIZE (Performance & Review)
- Security Auditing: Run static analyzers (Slither, Aderyn) to catch common vulnerabilities (reentrancy, arithmetic overflows).
- Gas Optimization: Use
calldatainstead ofmemoryfor read-only external inputs. Pack structs to fit in 256-bit slots. - Upgradability: If using proxies, ensure storage slots do not clash on upgrades (append-only storage).
- Documentation: Add NatSpec comments (
@title,@notice,@param) to all public/external functions.
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.
- 7d ago First seen · 24 lines · 0 tokens per session scan A fdd4ebdbbf5d
smart-contracts is a skill published in the GitHub repository DongDuong2001/pudo-code-system (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 424 tokens. 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-31.
Other skills, from other repositories
scale-to-millions
Use this skill whenever the user is designing, reviewing, debugging, or answering interview questions about system/software architecture and scalability — e.g. "scale my app", "how do I handle more traffic", "design a URL shortener / news feed / chat system", "my API is slow under load", "should I shard my database"…
defi-protocol-templates
Implement DeFi protocols with production-ready templates for staking, AMMs, governance, and lending systems. Use when building decentralized finance applications or smart contract protocols.
012-agile-epic
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for…
pumpfun
Complete PumpFun Protocol guide for building token launches, bonding curves, and AMM integrations on Solana. Covers Pump Program (token creation, buy/sell on bonding curves), PumpSwap AMM (liquidity pools, swaps), fee structures, creator fees, and SDK integration.
lifi
Integrate LI.FI for cross-chain swaps, bridging, payments, route discovery, and transfer status tracking across Solana, EVM, Bitcoin, and Sui. Use when building Solana applications or AI agents that need quotes, routes, executable transactions, supported chains/tokens/tools, or cross-chain transfer monitoring.
agent-ready-x402
Sub-skill de agent-ready-cloudflare: Implement x402 Payment Protocol.