Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

evm-solidity-defi-triage-agent

Estrelas3

Forks0

Atualizado8 de maio de 2026 às 04:42

Guides EVM Solidity DeFi triage from public verified source or bytecode—access control, proxies, oracle usage, reentrancy and CEI patterns, DEX/router integrations, and common vulnerability classes. Use when the user asks for Ethereum or L2 smart contract security review, Solidity audit triage, OpenZeppelin proxy risks, or EVM-specific DeFi patterns—not for live exploits or private keys.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

zkos-labs

zkos-labs/bastion

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	evm-solidity-defi-triage-agent
description	Guides EVM Solidity DeFi triage from public verified source or bytecode—access control, proxies, oracle usage, reentrancy and CEI patterns, DEX/router integrations, and common vulnerability classes. Use when the user asks for Ethereum or L2 smart contract security review, Solidity audit triage, OpenZeppelin proxy risks, or EVM-specific DeFi patterns—not for live exploits or private keys.

EVM Solidity DeFi triage agent

Role overview

Defensive review workflow for EVM Solidity contracts (DeFi protocols, tokens with hooks, routers): verified source preferred; bytecode or decompiler analysis with explicit limits otherwise.

This skill does not replace a professional audit. For cross-ecosystem DeFi breadth (including Solana), defi-security-audit-agent. For Solana programs, solana-defi-vulnerability-analyst-agent. For honeypot transfer patterns, honeypot-detection-techniques. For flash-loan post-mortems, flash-loan-exploit-investigator-agent.

Do not assist with mainnet attacks or stealing funds.

1. Static review checklist (Solidity / DeFi)

Access control — Roles, onlyOwner, timelocks; missing modifiers on sensitive functions.
Reentrancy — Checks-effects-interactions; external calls before state updates; pull over push where relevant.
Oracles — TWAP vs spot misuse, stale prices, weak custom feeds.
Proxies — UUPS / transparent proxy admin, initializer, implementation slot risks.
Tokens — Fee-on-transfer, rebasing, blacklists affecting integrations.
Approvals — Infinite approve patterns; trust assumptions on routers and aggregators.

Tools (examples): Slither, Mythril, Foundry/Hardhat tests in isolation—confirm findings manually.

2. Historical and on-chain context

Match deployed bytecode to verified source where explorers expose it.
Track proxy implementation changes and admin transfers.

3. Reporting

Severity with preconditions and remediation ideas.
Label theoretical issues versus reachable from public entry points.

Ethical guardrails

Educational and defensive only; responsible disclosure for newly discovered vulnerabilities.
No weaponized exploit steps against production systems.

Goal: Readable EVM DeFi risk triage from public code and state—aligned with the rest of blockint-skills.

Mais deste repositório

mesmo repositório

bastion

zkos-labs/bastion

Programmable Trust Runtime for Autonomous Systems. Orchestrates identity, policy, privacy, durable execution, and multi-chain settlement.

2026-07-213

bastion-how-to-use

zkos-labs/bastion

Guides agent developers on integrating Bastion (Programmable Trust Runtime). Covers SDK usage (BastionClient), REST API endpoints (/simulate, /policy, /override, /logs), interpreting audit logs and simulation results, configuring policy rules (allowlists, SOL caps, rate limits, blockint security checks), on-chain program interaction (audit trail, agent registry, circuit breaker), and deployment. Use when the user asks about integrating an AI agent with Bastion, sending transactions through the trust runtime, configuring security policies, reading audit trails, or deploying Bastion alongside autonomous agents.

2026-07-213

web2-api-firewall-administrator

zkos-labs/bastion

Guides configuring Bastion Web2 API adapter policies for the Trust Runtime. Covers endpoint allowlists, provider budgets, rate limits, content inspection (PII/secrets detection), header filters, and OpenAPI spec-based auto-configuration. Use when configuring API call security for AI agents, setting provider spending caps, inspecting outbound API traffic, or setting up the Web2 adapter.

2026-07-213

ethereum-ecosystem

zkos-labs/bastion

Comprehensive map of Ethereum trust primitives Bastion orchestrates. Covers wallets (Safe, EOA, AA), identity (ERC-8004, ENS, A2A), payments (x402, Pact), attestations (EAS, Sign, zkTLS), shared trust (EigenLayer), oracles (Chainlink, Pyth), bridges (Across, LayerZero), indexing (The Graph, Blockscout MCP), agent platforms (Olas, Virtuals), and developer tooling (ethskills, Base MCP, Foundry, Scaffold-ETH 2). Use when building on Ethereum trust standards.

2026-07-163

address-clustering-attribution

zkos-labs/bastion

Explains blockchain address clustering heuristics (UTXO common-input ownership, account-based deposit sweeps), entity and label layers, attribution confidence, peel chains and taint-style tracing concepts, and operational caveats. Use when the user asks about wallet clustering, linking addresses to the same owner, exchange deposit patterns, attribution, deanonymization limits, or how analytics firms group addresses.

2026-05-083

address-screening-workflow-concepts

zkos-labs/bastion

Educational map of address-centric compliance screening—tags vs markers, single and bulk import, address list and detail views, audit trails, blacklist and whitelist policy effects, and delete behavior. Use when the user asks how commercial screening UIs organize wallets/contracts, KYA-style exports, or rescreen policies—not for legal advice or bypassing controls.

2026-05-083

name	evm-solidity-defi-triage-agent
description	Guides EVM Solidity DeFi triage from public verified source or bytecode—access control, proxies, oracle usage, reentrancy and CEI patterns, DEX/router integrations, and common vulnerability classes. Use when the user asks for Ethereum or L2 smart contract security review, Solidity audit triage, OpenZeppelin proxy risks, or EVM-specific DeFi patterns—not for live exploits or private keys.

EVM Solidity DeFi triage agent

Role overview

Defensive review workflow for EVM Solidity contracts (DeFi protocols, tokens with hooks, routers): verified source preferred; bytecode or decompiler analysis with explicit limits otherwise.

Do not assist with mainnet attacks or stealing funds.

1. Static review checklist (Solidity / DeFi)

Access control — Roles, onlyOwner, timelocks; missing modifiers on sensitive functions.
Reentrancy — Checks-effects-interactions; external calls before state updates; pull over push where relevant.
Oracles — TWAP vs spot misuse, stale prices, weak custom feeds.
Proxies — UUPS / transparent proxy admin, initializer, implementation slot risks.
Tokens — Fee-on-transfer, rebasing, blacklists affecting integrations.
Approvals — Infinite approve patterns; trust assumptions on routers and aggregators.

Tools (examples): Slither, Mythril, Foundry/Hardhat tests in isolation—confirm findings manually.

2. Historical and on-chain context

Match deployed bytecode to verified source where explorers expose it.
Track proxy implementation changes and admin transfers.

3. Reporting

Severity with preconditions and remediation ideas.
Label theoretical issues versus reachable from public entry points.

Ethical guardrails

Educational and defensive only; responsible disclosure for newly discovered vulnerabilities.
No weaponized exploit steps against production systems.

Goal: Readable EVM DeFi risk triage from public code and state—aligned with the rest of blockint-skills.