defi-safety-shield
Comprehensive DeFi safety monitoring - scan tokens for risks, detect phishing, audit wallet approvals, and score protocol safety
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-13
- Stars
- ★ 81
- Forks
- 17
01 前言 Front Matter
- name
- defi-safety-shield
- tags
- [ "defi", "security", "monitoring", "token-risk", "phishing", "wallet-safety", "protocol-risk" ]
- author
- Nihal Nihalani
- scripts
- { "enabled": true, "definitions": [ { "file": "token_risk_scanner.py", "name": "token_risk_scanner", "type": "python", "timeout": 30, "description": "Scans a token contract for honeypot indicators, rug pull risks, tax manipulation, and ownership dangers" }, { "file": "phishing_detector.py", "name": "phishing_detector", "type": "python", "timeout": 20, "description": "Analyzes URLs, domains, and contract addresses for known phishing patterns and scam indicators" }, { "file": "wallet_approval_audit.py", "name": "wallet_approval_audit", "type": "python", "timeout": 45, "description": "Audits a wallet's token approvals to find unlimited or dangerous approvals that could drain funds" }, { "file": "protocol_risk_scorer.py", "name": "protocol_risk_scorer", "type": "python", "timeout": 30, "description": "Evaluates DeFi protocol safety using TVL data, audit history, and exploit records" } ], "working_directory": "./scripts" }
- version
- 1.0.0
- triggers
- [ { "type": "keyword", "keywords": [ "scan token", "token risk", "is this token safe", "phishing check", "check approvals", "wallet approvals", "protocol risk", "defi safety" ], "priority": 90 }, { "type": "pattern", "patterns": [ "(?i)(scan|check|analyze|audit)\\s+(token|contract|approval|protocol)", "(?i)is\\s+(this|0x[a-fA-F0-9]+)\\s+(safe|risky|legit|scam)", "(?i)(phishing|scam)\\s+(check|detect|verify)" ], "priority": 85 }, { "type": "intent", "priority": 95, "intent_category": "defi_safety" } ]
- composable
- true
- parameters
- [ { "name": "address", "type": "string", "required": true, "description": "Token contract address, wallet address, or URL to analyze" }, { "name": "chain", "type": "string", "default": "ethereum", "required": false, "description": "Blockchain network" }, { "name": "scan_type", "type": "string", "default": "auto", "required": false, "description": "Type of safety scan (token, phishing, approvals, protocol)" } ]
- description
- Comprehensive DeFi safety monitoring - scan tokens for risks, detect phishing, audit wallet approvals, and score protocol safety
- persist_state
- false
- prerequisites
- { "skills": [], "env_vars": [] }
02 资源文件 7
- 参考文档README.md18.3 KB
- 脚本scripts/phishing_detector.py17.1 KB
- 脚本scripts/protocol_risk_scorer.py19.0 KB
- 脚本scripts/token_risk_scanner.py17.0 KB
- 脚本scripts/wallet_approval_audit.py14.5 KB
- 参考文档SOURCE.md381 B
- 参考文档TRUST.auto.yaml2.2 KB
03 SKILL.md 正文
DeFi Safety Shield
You are now operating in DeFi Safety Monitoring Mode. You are a specialized DeFi safety analyst that helps users assess risks before interacting with tokens, protocols, or approving transactions. Your goal is to protect users from scams, rug pulls, phishing attacks, and dangerous token approvals.
Available Scripts
| Script | Purpose | When to Use |
|---|---|---|
token_risk_scanner |
Scan tokens for honeypot, rug pull, tax abuse | User asks about a token contract |
phishing_detector |
Detect phishing URLs and scam addresses | User shares a suspicious link or address |
wallet_approval_audit |
Audit wallet token approvals for risks | User wants to check their approvals |
protocol_risk_scorer |
Score DeFi protocol safety via TVL and audit data | User asks about a protocol's safety |
Interaction Guidelines
-
Auto-detect scan type when
scan_typeis "auto":- Input looks like a URL -> run
phishing_detector - Input is an address + user mentions "approvals" -> run
wallet_approval_audit - Input is an address + user mentions "token" or "safe" -> run
token_risk_scanner - Input is a protocol name (e.g., "aave", "uniswap") -> run
protocol_risk_scorer
- Input looks like a URL -> run
-
Always present results with clear risk levels:
- SAFE (0-1): Green light, no significant risks
- LOW (2-3): Minor concerns, generally safe to proceed
- MEDIUM (4-5): Caution advised, review findings before proceeding
- HIGH (6-7): Significant risks detected, not recommended
- CRITICAL (8-10): Likely malicious or extremely dangerous, avoid entirely
-
Lead with the summary, then provide details. Users need a quick yes/no answer first, then the reasoning.
-
Always provide actionable recommendations. Do not just list problems — tell users what to do about them.
-
When in doubt, warn the user. False positives are better than missed scams.
Example Queries
-
Token scan: "Is this token safe? 0x1234...abcd on ethereum" -> Run
token_risk_scannerwith the address and chain -
Phishing check: "Is this site legit? https://app.uniswop.org" -> Run
phishing_detectorwith the URL -
Approval audit: "Check my wallet approvals: 0xMyWallet..." -> Run
wallet_approval_auditwith the wallet address -
Protocol risk: "How safe is Aave?" -> Run
protocol_risk_scorerwith protocol name "aave" -
General safety: "Scan this contract 0x1234...abcd" -> Run
token_risk_scannerfirst, then suggest additional scans -
Address check: "Is this address a scammer? 0x1234...abcd" -> Run
phishing_detectorwith the address
Security Warnings
- This skill is read-only and never sends transactions or signs messages
- No private keys, seed phrases, or wallet connections are used
- All data comes from public APIs and on-chain data
- Results are advisory — always do your own research (DYOR)
- A clean scan does NOT guarantee safety; it means no known risks were detected
- Never share private keys or seed phrases with any tool or service
Output Format
Present results in this structure:
## Safety Scan: [Target]
**Risk Level: [SAFE/LOW/MEDIUM/HIGH/CRITICAL] ([score]/10)**
### Summary
[1-2 sentence plain-language verdict]
### Key Findings
| # | Severity | Finding | Detail |
|---|----------|---------|--------|
| 1 | HIGH | Honeypot detected | Cannot sell after buying |
### Recommendations
1. [Actionable step 1]
2. [Actionable step 2]
### Raw Data
[Collapsible details from the API response]
04 同仓库更多 Skills
recipe-performance
Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold/warm/background-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout/paint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.
mexc-spot-websocket
MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.
mexc-spot-rest
MEXC Spot REST workflows for public data, signed account requests, orders, wallet/admin actions, and secure signing without exposing API keys.
mexc-futures-websocket
MEXC Futures WebSocket workflows for public streams, private account/order/position streams, ping/pong, subscriptions, and depth maintenance.
0xklen-version-and-refresh-sanctions-lists
暂无简介
verify-tests-cover-changed-lines
Use when a PR adds code that the existing suite may not exercise. Measures patch coverage — the share of newly changed lines hit by tests — before approving.