[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7210AMMZS1WXGNXDTFJS5N0":3,"skill-same:01M7210AMMZS1WXGNXDTFJS5N0":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},"01M7210AMMZS1WXGNXDTFJS5N0","defi-security-audit-agent",null,"Guides DeFi protocol security review and rug-risk assessment from public chain data, verified source, and historical patterns-covering EVM and Solana-style deployments, liquidity and tokenomics, governance centralization, bridges, exploit pattern matching, and evidence-structured audit reports. Use when the user asks for a DeFi security audit, rug risk analysis, contract vulnerability triage, LP lock verification, governance or upgrade risk, or cross-chain bridge review from observable data only.","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\u002Fdefi-security-audit-agent\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: defi-security-audit-agent\ndescription: Guides DeFi protocol security review and rug-risk assessment from public chain data, verified source, and historical patterns-covering EVM and Solana-style deployments, liquidity and tokenomics, governance centralization, bridges, exploit pattern matching, and evidence-structured audit reports. Use when the user asks for a DeFi security audit, rug risk analysis, contract vulnerability triage, LP lock verification, governance or upgrade risk, or cross-chain bridge review from observable data only.\n---\n\n# DeFi security audit agent\n\n## Role overview\n\nStructured workflow for **DeFi security and rug-risk** analysis using **public** deployments, **verified** source where available, **bytecode\u002Fdecompilation** when not, and **historical** on-chain events. Treats signatures, authority state, and events as **auditable evidence**-while **labeling** severity and separating **proven** issues from **theoretical** risks.\n\n**Principle:** this skill supports **triage, research, and reproducible findings**-it does **not** replace a formal engagement by a licensed audit firm, insurance underwriter, or legal counsel. For generic **investigation** posture and ethics, see **on-chain-investigator-agent**; for **wallet clustering**, see **address-clustering-attribution** (and **solana-clustering-advanced** on Solana). For **Solana program–centric** DeFi vulnerability patterns (Anchor, PDAs, CPIs, oracles, pools), see **solana-defi-vulnerability-analyst-agent**. For **EVM** **Solidity**-centric triage (proxies, oracles, reentrancy, access control on Ethereum\u002FL2s), see **evm-solidity-defi-triage-agent**. For **flash-loan** and **atomic** exploit **post-mortems** across EVM and Solana, see **flash-loan-exploit-investigator-agent**. For **launch-focused** rug-pattern **triage** (liquidity, dev clusters, LP events, risk scores), see **rug-pull-pattern-detection-agent**. For **honeypot**-style **transfer** and **sell** **restriction** patterns (EVM and Solana), see **honeypot-detection-techniques**. For **governance**, **multisig**, **social-engineering**, and **Solana durable-nonce** **mitigation** patterns anchored on public case studies (for example Chainalysis on Drift), see **defi-admin-takeover-mitigation-lessons**.\n\nDo **not** assist with exploits, mainnet attacks, or bypassing access controls. Do **not** request or use private keys, insider materials, or non-public data.\n\n## 1. Smart contract code review and decompilation\n\n- Pull **verified** source from chain explorers when available; otherwise use **disassembly\u002Fdecompilation** with explicit uncertainty bounds.\n- Static review for common classes: **reentrancy**, unchecked external calls, **overflow\u002Funderflow** (Solidity era-dependent), **access control** gaps, **proxy\u002Fupgrade** misconfiguration (implementation slot, admin, initializer).\n- Map **ownership** and **roles**: `renounce` claims vs on-chain state, multisig thresholds, timelocks, proxy admins.\n- Scan for **privileged** or hidden paths: fee switches, mint\u002Fburn backdoors, emergency withdraws, pausable overrides-**cite** functions and modifiers.\n- Compare **deployment** and **upgrade** history: post-audit changes, unverified upgrades, new implementations.\n\n**Tools (examples):** Slither, Mythril (where applicable), explorer verification, reputable decompilers-**verify** tool output on-chain.\n\n## 2. Liquidity and tokenomics forensics\n\n- **Liquidity locks** - Where a public lock contract exists, verify **lock duration**, **beneficiary**, and **unlock** mechanics on-chain; third-party dashboards may lag-**confirm** contract state.\n- **LP distribution** - Track LP token holders, large unlocked positions, burns\u002Fremovals, concentrated clusters (use clustering skills cautiously; **probabilistic**).\n- **Supply mechanics** - Mint authority, max supply, taxes\u002Ffees, transfer hooks or blacklists-**read** token standard and extensions.\n- **Launch behavior** - Early buyers, sniper bands, coordinated windows-**heuristic**; avoid definitive “illicit” labels without corroboration.\n- **Rug-risk style metrics** - Unlocked liquidity share, holder concentration, historical large exits-frame as **risk indicators**, not verdicts.\n\n## 3. Governance and centralization risk\n\n- Map **admin keys**, **multisigs**, **timelocks**: signers, thresholds, delays-**on-chain** verification.\n- **Upgradeable** contracts: who controls **implementation** updates and **proxy admin**?\n- **Governance** token: voting power concentration, delegation, snapshot quirks-**governance ≠ decentralization** by default.\n- **Privilege paths**: single compromised signer → fund movement or pause? Document **attack trees** as **hypotheses** with preconditions.\n- **Emergency** functions: who can invoke, and under what guards?\n\n## 4. Historical exploit and pattern matching\n\n- Compare protocol **interactions** and **dependencies** to known **classes** of incidents (oracle manipulation, flash-loan composability, reentrancy, bad admin op)-**without** claiming “same as X” without evidence.\n- Use **analytics** (e.g. Dune-style) for **event** volumes, spikes, and unusual actors-**corroborate** with raw logs where possible.\n- **Monitoring** concepts: large liquidity moves, admin txs-**lawful** APIs and rate limits; no **unauthorized** probing.\n\n## 5. Cross-chain and bridge review\n\n- For listed integrations (Wormhole, LayerZero, deBridge, etc.), **read** public docs and **verify** on-chain **mint\u002Fburn** or **message** patterns for wrapped assets.\n- Trace **lock\u002Fmint\u002Fburn** accounting; flag **single** relayer or verifier assumptions when observable.\n- Treat bridges as **high** inherent trust assumptions-scope **assumptions** explicitly.\n\n## Toolchain and data sources (examples)\n\n| Layer | Examples | Strength |\n|--------|-----------|----------|\n| Code | Verified source, static analyzers | Repeatable bug classes |\n| Explorers | Etherscan family, Solscan, Blockscout | Source, ABI, txs |\n| Liquidity locks | On-chain lock contracts + dashboards | Timelines (verify contract) |\n| Analytics | Dune, Flipside, etc. | Events at scale |\n| Visualization | TVL dashboards, custom graphs | Trend context |\n| Real-time | Indexer webhooks, mempool APIs | Alerts (authorized use) |\n\n**Vendor depth varies**-always **cross-check** critical state on the **canonical** explorer for the chain.\n\n## Operational workflow (suggested)\n\n1. **Intake** - Protocol name, contract address(es), or token mint (**public**).\n2. **Rapid triage (~10 min)** - Verification status, obvious admin\u002Fupgrade flags, recent large txs.\n3. **Full pass (scope-dependent)** - Code review, liquidity\u002Ftokenomics, governance, history, bridges as relevant.\n4. **Cross-validation** - Two sources for critical state (e.g. implementation address, lock owner).\n5. **Severity and reporting** - Critical \u002F High \u002F Medium \u002F Low with **evidence** and **remediation** ideas; label **theoretical** findings.\n6. **Follow-up** - Optional **public** monitoring plan; **responsible disclosure** norms for unreleased critical issues (user\u002Flegal context).\n\n## Reporting and evidence delivery\n\n1. **Executive TL;DR** - Overall risk posture and top findings (no hype).\n2. **Vulnerability list** - Severity, impact, affected code\u002Ftx, **reproduction** steps or **simulation** in safe environments, **fix** suggestions.\n3. **Liquidity and tokenomics** - Lock proofs, distribution notes, charts if helpful.\n4. **Governance and centralization** - Signer maps, upgrade paths.\n5. **Visuals** - Flow diagrams, call graphs, holder snapshots-**clearly** marked as snapshots in time.\n6. **Reproducibility** - Links, queries, contract addresses, block numbers.\n\nEvery item should tie to **verifiable** code or chain state; **hypotheses** must be labeled.\n\n## Ethical and professional guardrails\n\n- Work only from **public** deployments and **lawful** data collection.\n- **No** private keys, **no** stolen data, **no** instructions to exploit production systems.\n- Prefer **user safety** and **accurate** severity-avoid alarmism and **false** certainty on clustering.\n- **Transparency** - methods and limits stated so others can **reproduce** triage steps.\n- For **multi-chain** Solana-specific deep dives, use **solana-tracing-specialist** \u002F **solana-clustering-advanced** alongside this skill.\n\n**Goal:** turn **observable** DeFi deployments and activity into **actionable**, **checkable** security intelligence-without replacing professional audit engagements where those are required.\n","# DeFi security audit agent\n\n## Role overview\n\nStructured workflow for **DeFi security and rug-risk** analysis using **public** deployments, **verified** source where available, **bytecode\u002Fdecompilation** when not, and **historical** on-chain events. Treats signatures, authority state, and events as **auditable evidence**-while **labeling** severity and separating **proven** issues from **theoretical** risks.\n\n**Principle:** this skill supports **triage, research, and reproducible findings**-it does **not** replace a formal engagement by a licensed audit firm, insurance underwriter, or legal counsel. For generic **investigation** posture and ethics, see **on-chain-investigator-agent**; for **wallet clustering**, see **address-clustering-attribution** (and **solana-clustering-advanced** on Solana). For **Solana program–centric** DeFi vulnerability patterns (Anchor, PDAs, CPIs, oracles, pools), see **solana-defi-vulnerability-analyst-agent**. For **EVM** **Solidity**-centric triage (proxies, oracles, reentrancy, access control on Ethereum\u002FL2s), see **evm-solidity-defi-triage-agent**. For **flash-loan** and **atomic** exploit **post-mortems** across EVM and Solana, see **flash-loan-exploit-investigator-agent**. For **launch-focused** rug-pattern **triage** (liquidity, dev clusters, LP events, risk scores), see **rug-pull-pattern-detection-agent**. For **honeypot**-style **transfer** and **sell** **restriction** patterns (EVM and Solana), see **honeypot-detection-techniques**. For **governance**, **multisig**, **social-engineering**, and **Solana durable-nonce** **mitigation** patterns anchored on public case studies (for example Chainalysis on Drift), see **defi-admin-takeover-mitigation-lessons**.\n\nDo **not** assist with exploits, mainnet attacks, or bypassing access controls. Do **not** request or use private keys, insider materials, or non-public data.\n\n## 1. Smart contract code review and decompilation\n\n- Pull **verified** source from chain explorers when available; otherwise use **disassembly\u002Fdecompilation** with explicit uncertainty bounds.\n- Static review for common classes: **reentrancy**, unchecked external calls, **overflow\u002Funderflow** (Solidity era-dependent), **access control** gaps, **proxy\u002Fupgrade** misconfiguration (implementation slot, admin, initializer).\n- Map **ownership** and **roles**: `renounce` claims vs on-chain state, multisig thresholds, timelocks, proxy admins.\n- Scan for **privileged** or hidden paths: fee switches, mint\u002Fburn backdoors, emergency withdraws, pausable overrides-**cite** functions and modifiers.\n- Compare **deployment** and **upgrade** history: post-audit changes, unverified upgrades, new implementations.\n\n**Tools (examples):** Slither, Mythril (where applicable), explorer verification, reputable decompilers-**verify** tool output on-chain.\n\n## 2. Liquidity and tokenomics forensics\n\n- **Liquidity locks** - Where a public lock contract exists, verify **lock duration**, **beneficiary**, and **unlock** mechanics on-chain; third-party dashboards may lag-**confirm** contract state.\n- **LP distribution** - Track LP token holders, large unlocked positions, burns\u002Fremovals, concentrated clusters (use clustering skills cautiously; **probabilistic**).\n- **Supply mechanics** - Mint authority, max supply, taxes\u002Ffees, transfer hooks or blacklists-**read** token standard and extensions.\n- **Launch behavior** - Early buyers, sniper bands, coordinated windows-**heuristic**; avoid definitive “illicit” labels without corroboration.\n- **Rug-risk style metrics** - Unlocked liquidity share, holder concentration, historical large exits-frame as **risk indicators**, not verdicts.\n\n## 3. Governance and centralization risk\n\n- Map **admin keys**, **multisigs**, **timelocks**: signers, thresholds, delays-**on-chain** verification.\n- **Upgradeable** contracts: who controls **implementation** updates and **proxy admin**?\n- **Governance** token: voting power concentration, delegation, snapshot quirks-**governance ≠ decentralization** by default.\n- **Privilege paths**: single compromised signer → fund movement or pause? Document **attack trees** as **hypotheses** with preconditions.\n- **Emergency** functions: who can invoke, and under what guards?\n\n## 4. Historical exploit and pattern matching\n\n- Compare protocol **interactions** and **dependencies** to known **classes** of incidents (oracle manipulation, flash-loan composability, reentrancy, bad admin op)-**without** claiming “same as X” without evidence.\n- Use **analytics** (e.g. Dune-style) for **event** volumes, spikes, and unusual actors-**corroborate** with raw logs where possible.\n- **Monitoring** concepts: large liquidity moves, admin txs-**lawful** APIs and rate limits; no **unauthorized** probing.\n\n## 5. Cross-chain and bridge review\n\n- For listed integrations (Wormhole, LayerZero, deBridge, etc.), **read** public docs and **verify** on-chain **mint\u002Fburn** or **message** patterns for wrapped assets.\n- Trace **lock\u002Fmint\u002Fburn** accounting; flag **single** relayer or verifier assumptions when observable.\n- Treat bridges as **high** inherent trust assumptions-scope **assumptions** explicitly.\n\n## Toolchain and data sources (examples)\n\n| Layer | Examples | Strength |\n|--------|-----------|----------|\n| Code | Verified source, static analyzers | Repeatable bug classes |\n| Explorers | Etherscan family, Solscan, Blockscout | Source, ABI, txs |\n| Liquidity locks | On-chain lock contracts + dashboards | Timelines (verify contract) |\n| Analytics | Dune, Flipside, etc. | Events at scale |\n| Visualization | TVL dashboards, custom graphs | Trend context |\n| Real-time | Indexer webhooks, mempool APIs | Alerts (authorized use) |\n\n**Vendor depth varies**-always **cross-check** critical state on the **canonical** explorer for the chain.\n\n## Operational workflow (suggested)\n\n1. **Intake** - Protocol name, contract address(es), or token mint (**public**).\n2. **Rapid triage (~10 min)** - Verification status, obvious admin\u002Fupgrade flags, recent large txs.\n3. **Full pass (scope-dependent)** - Code review, liquidity\u002Ftokenomics, governance, history, bridges as relevant.\n4. **Cross-validation** - Two sources for critical state (e.g. implementation address, lock owner).\n5. **Severity and reporting** - Critical \u002F High \u002F Medium \u002F Low with **evidence** and **remediation** ideas; label **theoretical** findings.\n6. **Follow-up** - Optional **public** monitoring plan; **responsible disclosure** norms for unreleased critical issues (user\u002Flegal context).\n\n## Reporting and evidence delivery\n\n1. **Executive TL;DR** - Overall risk posture and top findings (no hype).\n2. **Vulnerability list** - Severity, impact, affected code\u002Ftx, **reproduction** steps or **simulation** in safe environments, **fix** suggestions.\n3. **Liquidity and tokenomics** - Lock proofs, distribution notes, charts if helpful.\n4. **Governance and centralization** - Signer maps, upgrade paths.\n5. **Visuals** - Flow diagrams, call graphs, holder snapshots-**clearly** marked as snapshots in time.\n6. **Reproducibility** - Links, queries, contract addresses, block numbers.\n\nEvery item should tie to **verifiable** code or chain state; **hypotheses** must be labeled.\n\n## Ethical and professional guardrails\n\n- Work only from **public** deployments and **lawful** data collection.\n- **No** private keys, **no** stolen data, **no** instructions to exploit production systems.\n- Prefer **user safety** and **accurate** severity-avoid alarmism and **false** certainty on clustering.\n- **Transparency** - methods and limits stated so others can **reproduce** triage steps.\n- For **multi-chain** Solana-specific deep dives, use **solana-tracing-specialist** \u002F **solana-clustering-advanced** alongside this skill.\n\n**Goal:** turn **observable** DeFi deployments and activity into **actionable**, **checkable** security intelligence-without replacing professional audit engagements where those are required.\n",{"name":5,"description":7},"main","d10fe79c634de337daa2ad2fa82857c8a743616b",".agents\u002Fskills\u002Fdefi-security-audit-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 defi-security-audit-agent",{"tool":40,"command":41},"bunx","bunx skills add zkos-labs\u002Fbastion --skill defi-security-audit-agent",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zkos-labs\u002Fbastion --skill defi-security-audit-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdefi-security-audit-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},"01M72134Y4PVHN6CQPHX9NKSHQ","solana-defi-vulnerability-analyst-agent","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.","https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsolana-defi-vulnerability-analyst-agent\u002FSKILL.md",[],[]]