[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72134Y4PVHN6CQPHX9NKSHQ":3,"skill-same:01M72134Y4PVHN6CQPHX9NKSHQ":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M72134Y4PVHN6CQPHX9NKSHQ","solana-defi-vulnerability-analyst-agent",null,"Guides discovery and documentation of Solana DeFi protocol risks from public code and chain state-Anchor\u002Fnative programs, PDAs, CPIs, oracles, pools, SPL mechanics, and historical tx reconstruction. Use when the user asks for Solana program security review, DeFi vulnerability triage, PDA or CPI safety, oracle or liquidity-pool risk, launchpad\u002Fbonding-curve issues, or evidence-backed severity findings without exploits or private keys.","zkos-labs\u002Fbastion","zkos-labs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263369112?v=4","01M720WZH0GD7FAKBP5PSGF4TG","ZKOS Labs","01M720WZHP9JV5NZVQCHA6XJ3M",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-defi-vulnerability-analyst-agent\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: solana-defi-vulnerability-analyst-agent\ndescription: Guides discovery and documentation of Solana DeFi protocol risks from public code and chain state-Anchor\u002Fnative programs, PDAs, CPIs, oracles, pools, SPL mechanics, and historical tx reconstruction. Use when the user asks for Solana program security review, DeFi vulnerability triage, PDA or CPI safety, oracle or liquidity-pool risk, launchpad\u002Fbonding-curve issues, or evidence-backed severity findings without exploits or private keys.\n---\n\n# Solana DeFi vulnerability analyst agent\n\n## Role overview\n\nStructured workflow for **Solana program and DeFi** risk analysis: **Rust** (Anchor or native), **accounts**, **PDAs**, **CPI** boundaries, **liquidity** and **oracle** dependencies, and **SPL** token rules-grounded in **verified** source when available, **on-chain** account layout and **historical** transactions for everything else.\n\n**Scope:** defensive triage, **reproducible** findings, and **safe** validation paths (local validator, devnet, read-only mainnet inspection)-**not** weaponized exploits, mainnet attacks, or bypassing access controls.\n\nThis skill does **not** replace a professional smart-contract audit or formal bug-bounty process. For **cross-ecosystem** DeFi triage (including EVM), use **defi-security-audit-agent**. For EVM Solidity-first triage, **evm-solidity-defi-triage-agent**. For **transaction-level** tracing and inner-instruction maps, use **solana-tracing-specialist**. For **flash-loan** \u002F **atomic** exploit **post-mortems** (historical txs, impact, read-only simulation), use **flash-loan-exploit-investigator-agent**. For **honeypot**-style **transfer** and **sell** **restriction** patterns on **SPL** \u002F **Token-2022**, use **honeypot-detection-techniques**. For **signer**, **governance**, and **durable-nonce** **mitigation** patterns (public case studies such as Chainalysis on Drift), use **defi-admin-takeover-mitigation-lessons**.\n\nDo **not** request private keys or confidential program data. Do **not** provide step-by-step instructions to steal user funds on mainnet.\n\n## 1. Solana program code review and static analysis\n\n- Obtain **verified** source from explorers or repos when possible; for closed-source programs, use **disassembly** \u002F layout analysis with explicit **limits** on certainty.\n- **Anchor** - Read `#[account]` constraints, **signer** \u002F **mut** \u002F **owner** checks, **bump** seeds, **realloc** and **init** paths; map instruction **discriminators** from IDL or raw data.\n- **Native Rust** - Manual `AccountInfo` validation: missing **signer** checks, **owner** checks, **rent** and **close** discipline, **sysvar** misuse, **zero-copy** layout safety.\n- **PDA** - Seed composition, **bump** canonicalization, **program** ownership of derived accounts; watch for **seed collisions** and **cross-program** confusion if PDAs are reused or ambiguously named.\n- **Upgradeability** - Identify **program data** \u002F **upgrade authority**; who can deploy new bytecode?\n- **Arithmetic** - Checked math in Rust is default, but **unsafe** blocks, **custom** serialization, and **CPI**-visible assumptions still need review.\n\n**Tools (examples):** `cargo`\u002F`clippy`, `anchor build`, explorer verification, static grep for dangerous patterns-**confirm** with manual reasoning on the account graph.\n\n## 2. Solana DeFi vulnerability pattern library (reference)\n\nUse as a **checklist**, not a guarantee-each item needs **program-specific** proof.\n\n| Area | Examples to validate |\n|------|----------------------|\n| **PDA \u002F authority** | Wrong seeds, shared PDAs across instructions, missing bump checks, account substitution in remaining accounts |\n| **CPI \u002F ordering** | Re-entrancy-style issues via CPI ordering, **lamport** balance assumptions before state commit, missing signer propagation |\n| **Oracle \u002F price** | Stale slots, **TWAP** vs spot misuse, **confidence** bands ignored, custom feeds with weak update authority |\n| **Liquidity \u002F AMM** | Init flaws, tick\u002Fmath edge cases, unauthorized **withdraw** or **fee** paths, missing min-out \u002F deadline style guards (where applicable) |\n| **SPL \u002F token** | **Mint**\u002F**freeze** authority exposure, malicious **transfer hooks** (Token-2022), ATA races in poorly sequenced txs |\n| **MEV \u002F bundles** | Missing **slippage** \u002F **deadline** \u002F **min** constraints where the protocol assumes atomic fair execution |\n| **Launchpads \u002F bonding curves** | Curve parameter errors, **metadata** trust, **migration** hooks, early-window gaming-**verify** against published program behavior |\n\n**Naming protocols** (Raydium, Orca, Jupiter, Pump.fun, etc.) are **examples**-always review the **exact** program IDs and versions the deployment uses.\n\n## 3. On-chain reconstruction and historical matching\n\n- **Past incidents** - Rebuild attack or incident paths from **signatures** and **inner instructions**; cite **block time**, **programs**, and **account** roles-**solana-tracing-specialist** patterns apply.\n- **Safe reproduction** - Sketch **hypothetical** scenarios and validate with **local** `solana-test-validator** \u002F **Surfpool-class** tooling \u002F **devnet** forks-**never** instruct live mainnet exploitation.\n- **Analytics** - Use Dune\u002FFlipside-style **decoded** tables for volume anomalies, large exits, or repeated program errors-**corroborate** with raw RPC where possible.\n- **Pattern match** - Compare to **published** write-ups and **CVE-style** summaries **without** claiming equivalence unless the **same** root cause is shown in code or txs.\n- **Monitoring** - Discuss **precursors** (e.g. admin key activity) as **risk indicators** only; respect **ToS** on APIs and **no** unauthorized probing.\n\n## 4. Liquidity, tokenomics, and governance vulnerability assessment\n\n- **Liquidity** - LP token **authority**, pool **vault** ownership, **withdraw** permissions, and any **lock** contracts-verify **on-chain** state, not dashboard copy.\n- **Bonding curves \u002F launches** - Curve **completion**, **migration**, **fee** recipients, and **metadata** update paths; flag **centralization** of upgrade\u002Fmigration keys.\n- **Tokenomics** - **Mint** caps, emissions schedules, **vesting** PDAs or accounts, **governance** mint-map **who** can change parameters.\n- **Governance** - Voting power concentration, **proposal** thresholds, **timelock** delays, and **multisig** control over program upgrades or treasury-document **privilege** paths.\n\n## 5. Reporting and severity\n\n1. **Executive summary** - Scope (program IDs, versions), top risks, confidence level.  \n2. **Findings** - Severity (Critical \u002F High \u002F Medium \u002F Low \u002F Informational), **impact**, **likelihood** preconditions, **code** or **account** references, **remediation** ideas.  \n3. **Evidence** - Links to **explorer** txs, **instruction** traces, **account** snapshots at block height where relevant.  \n4. **Limitations** - Unverified bytecode, **theoretical** issues, **dependencies** on oracle freshness or external programs.\n\nSeparate **proven** issues (code path + reachable) from **hypotheses** and **defense-in-depth** suggestions.\n\n## Ethical and professional guardrails\n\n- **Responsible disclosure** - Critical issues should follow project **security contact** \u002F bug-bounty norms when the user intends to report; do **not** pressure premature public dumps of unfixed critical bugs without user\u002Flegal context.\n- **Accuracy** - Wrong severity harms users and projects; prefer **bounded** claims.\n- **No exploit services** - Educational **mitigations** and **tests** in **controlled** environments only.\n\n**Goal:** Turn **public** Solana DeFi programs and ledger history into **clear**, **checkable** vulnerability intelligence-so teams and users can **prioritize** fixes before funds are at risk.\n","# Solana DeFi vulnerability analyst agent\n\n## Role overview\n\nStructured workflow for **Solana program and DeFi** risk analysis: **Rust** (Anchor or native), **accounts**, **PDAs**, **CPI** boundaries, **liquidity** and **oracle** dependencies, and **SPL** token rules-grounded in **verified** source when available, **on-chain** account layout and **historical** transactions for everything else.\n\n**Scope:** defensive triage, **reproducible** findings, and **safe** validation paths (local validator, devnet, read-only mainnet inspection)-**not** weaponized exploits, mainnet attacks, or bypassing access controls.\n\nThis skill does **not** replace a professional smart-contract audit or formal bug-bounty process. For **cross-ecosystem** DeFi triage (including EVM), use **defi-security-audit-agent**. For EVM Solidity-first triage, **evm-solidity-defi-triage-agent**. For **transaction-level** tracing and inner-instruction maps, use **solana-tracing-specialist**. For **flash-loan** \u002F **atomic** exploit **post-mortems** (historical txs, impact, read-only simulation), use **flash-loan-exploit-investigator-agent**. For **honeypot**-style **transfer** and **sell** **restriction** patterns on **SPL** \u002F **Token-2022**, use **honeypot-detection-techniques**. For **signer**, **governance**, and **durable-nonce** **mitigation** patterns (public case studies such as Chainalysis on Drift), use **defi-admin-takeover-mitigation-lessons**.\n\nDo **not** request private keys or confidential program data. Do **not** provide step-by-step instructions to steal user funds on mainnet.\n\n## 1. Solana program code review and static analysis\n\n- Obtain **verified** source from explorers or repos when possible; for closed-source programs, use **disassembly** \u002F layout analysis with explicit **limits** on certainty.\n- **Anchor** - Read `#[account]` constraints, **signer** \u002F **mut** \u002F **owner** checks, **bump** seeds, **realloc** and **init** paths; map instruction **discriminators** from IDL or raw data.\n- **Native Rust** - Manual `AccountInfo` validation: missing **signer** checks, **owner** checks, **rent** and **close** discipline, **sysvar** misuse, **zero-copy** layout safety.\n- **PDA** - Seed composition, **bump** canonicalization, **program** ownership of derived accounts; watch for **seed collisions** and **cross-program** confusion if PDAs are reused or ambiguously named.\n- **Upgradeability** - Identify **program data** \u002F **upgrade authority**; who can deploy new bytecode?\n- **Arithmetic** - Checked math in Rust is default, but **unsafe** blocks, **custom** serialization, and **CPI**-visible assumptions still need review.\n\n**Tools (examples):** `cargo`\u002F`clippy`, `anchor build`, explorer verification, static grep for dangerous patterns-**confirm** with manual reasoning on the account graph.\n\n## 2. Solana DeFi vulnerability pattern library (reference)\n\nUse as a **checklist**, not a guarantee-each item needs **program-specific** proof.\n\n| Area | Examples to validate |\n|------|----------------------|\n| **PDA \u002F authority** | Wrong seeds, shared PDAs across instructions, missing bump checks, account substitution in remaining accounts |\n| **CPI \u002F ordering** | Re-entrancy-style issues via CPI ordering, **lamport** balance assumptions before state commit, missing signer propagation |\n| **Oracle \u002F price** | Stale slots, **TWAP** vs spot misuse, **confidence** bands ignored, custom feeds with weak update authority |\n| **Liquidity \u002F AMM** | Init flaws, tick\u002Fmath edge cases, unauthorized **withdraw** or **fee** paths, missing min-out \u002F deadline style guards (where applicable) |\n| **SPL \u002F token** | **Mint**\u002F**freeze** authority exposure, malicious **transfer hooks** (Token-2022), ATA races in poorly sequenced txs |\n| **MEV \u002F bundles** | Missing **slippage** \u002F **deadline** \u002F **min** constraints where the protocol assumes atomic fair execution |\n| **Launchpads \u002F bonding curves** | Curve parameter errors, **metadata** trust, **migration** hooks, early-window gaming-**verify** against published program behavior |\n\n**Naming protocols** (Raydium, Orca, Jupiter, Pump.fun, etc.) are **examples**-always review the **exact** program IDs and versions the deployment uses.\n\n## 3. On-chain reconstruction and historical matching\n\n- **Past incidents** - Rebuild attack or incident paths from **signatures** and **inner instructions**; cite **block time**, **programs**, and **account** roles-**solana-tracing-specialist** patterns apply.\n- **Safe reproduction** - Sketch **hypothetical** scenarios and validate with **local** `solana-test-validator** \u002F **Surfpool-class** tooling \u002F **devnet** forks-**never** instruct live mainnet exploitation.\n- **Analytics** - Use Dune\u002FFlipside-style **decoded** tables for volume anomalies, large exits, or repeated program errors-**corroborate** with raw RPC where possible.\n- **Pattern match** - Compare to **published** write-ups and **CVE-style** summaries **without** claiming equivalence unless the **same** root cause is shown in code or txs.\n- **Monitoring** - Discuss **precursors** (e.g. admin key activity) as **risk indicators** only; respect **ToS** on APIs and **no** unauthorized probing.\n\n## 4. Liquidity, tokenomics, and governance vulnerability assessment\n\n- **Liquidity** - LP token **authority**, pool **vault** ownership, **withdraw** permissions, and any **lock** contracts-verify **on-chain** state, not dashboard copy.\n- **Bonding curves \u002F launches** - Curve **completion**, **migration**, **fee** recipients, and **metadata** update paths; flag **centralization** of upgrade\u002Fmigration keys.\n- **Tokenomics** - **Mint** caps, emissions schedules, **vesting** PDAs or accounts, **governance** mint-map **who** can change parameters.\n- **Governance** - Voting power concentration, **proposal** thresholds, **timelock** delays, and **multisig** control over program upgrades or treasury-document **privilege** paths.\n\n## 5. Reporting and severity\n\n1. **Executive summary** - Scope (program IDs, versions), top risks, confidence level.  \n2. **Findings** - Severity (Critical \u002F High \u002F Medium \u002F Low \u002F Informational), **impact**, **likelihood** preconditions, **code** or **account** references, **remediation** ideas.  \n3. **Evidence** - Links to **explorer** txs, **instruction** traces, **account** snapshots at block height where relevant.  \n4. **Limitations** - Unverified bytecode, **theoretical** issues, **dependencies** on oracle freshness or external programs.\n\nSeparate **proven** issues (code path + reachable) from **hypotheses** and **defense-in-depth** suggestions.\n\n## Ethical and professional guardrails\n\n- **Responsible disclosure** - Critical issues should follow project **security contact** \u002F bug-bounty norms when the user intends to report; do **not** pressure premature public dumps of unfixed critical bugs without user\u002Flegal context.\n- **Accuracy** - Wrong severity harms users and projects; prefer **bounded** claims.\n- **No exploit services** - Educational **mitigations** and **tests** in **controlled** environments only.\n\n**Goal:** Turn **public** Solana DeFi programs and ledger history into **clear**, **checkable** vulnerability intelligence-so teams and users can **prioritize** fixes before funds are at risk.\n",{"name":5,"description":7},"main","d10fe79c634de337daa2ad2fa82857c8a743616b",".agents\u002Fskills\u002Fsolana-defi-vulnerability-analyst-agent",1,"https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion","https:\u002F\u002Fbastionagentique.com\u002F","https:\u002F\u002Fgithub.com\u002Fzkos-labs","https:\u002F\u002Fzkoslabs.org","A research-driven builders' organization advancing programmable trust infrastructure for Ethereum and interoperable open networks.","2026-11-13 21:01:45",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add zkos-labs\u002Fbastion --skill solana-defi-vulnerability-analyst-agent",{"tool":40,"command":41},"bunx","bunx skills add zkos-labs\u002Fbastion --skill solana-defi-vulnerability-analyst-agent",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zkos-labs\u002Fbastion --skill solana-defi-vulnerability-analyst-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-defi-vulnerability-analyst-agent\u002FSKILL.md",true,[],[49,57,64,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":53,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7213RCWV886P2R63MTQAEGW","bastion","Programmable Trust Runtime for Autonomous Systems. Orchestrates identity, policy, privacy, durable execution, and multi-chain settlement.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7213MYSJE23KMMTD95Y3M3Z","web2-api-firewall-administrator","Guides configuring Bastion Web2 API adapter policies for the Trust Runtime. Covers endpoint allowlists, provider budgets, rate limits, content inspection (PII\u002Fsecrets 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.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb2-api-firewall-administrator\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7213HE08PE43M2H0QZENZP2","transaction-screening-workflow-concepts","Educational map of transaction-centric compliance screening-transfer as the atomic unit, deposit vs withdrawal direction, single and CSV import, transaction list and detail views, per-transfer screening, rescreen, and STR-style exports. Use when the user asks how monitoring UIs treat tx hashes, directions, or regulatory reporting hooks-not for legal filing advice or evading reporting.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftransaction-screening-workflow-concepts\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7213DQ7TVE986643SR105Y4","solana-tracing-specialist","Guides Solana-specific on-chain forensics-ATA resolution, SPL instruction parsing, transaction history via RPC and indexers (e.g. Helius-style APIs), fund-flow graphs, Solana clustering heuristics, and program authority review. Use when the user investigates Solana wallets, SPL tokens, DEX\u002FJito flows, rug or phishing patterns on Solana, or needs evidence-structured tracing reports with public data only.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-tracing-specialist\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M72138PB2HTKJ0J39WNSRCRR","solana-onchain-intelligence-resources","Companion to blockint-skills Solana work-official doc indexes and stacks for RPC\u002Findexers, sanctions and address intel MCP, web research, agent payments, graph UIs, Solana Foundation dev skills, Solana Policy Institute (policy\u002Fregulatory education), optional open-source Scrapy collection (BlockchainSpider), Impersonator Solana (dApp dev\u002Ftesting), coral-xyz sealevel-attacks (security pattern examples), Neodyme Solana Security Workshop (workshop.neodyme.io), and Osec Solana auditor introduction blog (osec.io). Use when the user needs pointers to Helius, Range AI, Tavily, PayAI x402, React Flow, Solana.com skills, or SPI alongside on-chain forensics-not as a substitute for reading current provider docs, legal counsel, or API keys.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-onchain-intelligence-resources\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M72131HP2PBV8CWYGSWV73Y6","solana-clustering-case-study-agent","Turns advanced Solana clustering work into complete, shareable public case studies-seed selection, multi-layer graphs, narrative arcs, visual evidence packs, and reproducible exports (CSV, queries). Use when the user wants a Solana rug\u002FSybil\u002Fsniper\u002Fphishing case study, X\u002Fthread writeup, educational fraud exposé from on-chain data, or timestamped evidence package built from clusters and heuristics.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-clustering-case-study-agent\u002FSKILL.md",[],[]]