[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72124MNA9EGH0KT0SHK0Q5P":3,"skill-same:01M72124MNA9EGH0KT0SHK0Q5P":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},"01M72124MNA9EGH0KT0SHK0Q5P","osec-solana-auditor-introduction",null,"Points to Otter Sec (osec.io) blog post “Solana: An Auditor’s Introduction”-runtime-oriented primer on Sealevel execution, accounts, BPF entrypoint deserialization, attacker-controlled vs runtime-enforced fields, and native programs (e.g. System Program). Use when the user cites this article or needs fundamentals next to neodyme-solana-security-workshop and sealevel-attacks-solana-not as current protocol spec (verify Solana docs and post-2022 runtime changes).","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\u002Fosec-solana-auditor-introduction\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: osec-solana-auditor-introduction\ndescription: \"Points to Otter Sec (osec.io) blog post “Solana: An Auditor’s Introduction”-runtime-oriented primer on Sealevel execution, accounts, BPF entrypoint deserialization, attacker-controlled vs runtime-enforced fields, and native programs (e.g. System Program). Use when the user cites this article or needs fundamentals next to neodyme-solana-security-workshop and sealevel-attacks-solana-not as current protocol spec (verify Solana docs and post-2022 runtime changes).\"\n---\n\n# Osec - Solana: An Auditor’s Introduction (reference)\n\n**Educational routing only.** This skill does **not** reproduce the full article or code excerpts. Read the **live** post for complete detail.\n\n## Canonical URL\n\n- **[Solana: An Auditor’s Introduction](https:\u002F\u002Fosec.io\u002Fblog\u002F2022-03-14-solana-security-intro)** - [osec.io](https:\u002F\u002Fosec.io\u002F) blog, **14 March 2022**.\n\n**Publisher:** [Otter Sec](https:\u002F\u002Fosec.io\u002F) \u002F Otter Audits LLC (smart contract security audits; per site footer).\n\n## What the article covers (outline)\n\nThe post frames **Solana program security** from a **researcher \u002F auditor** lens: how the **runtime** executes contracts, where **trust boundaries** sit, and what an attacker can influence.\n\n| Theme | Topics (high level) |\n|-------|---------------------|\n| **Execution model** | Programs as **eBPF ELF** loaded via **BPF Loader**; accounts as **pubkey-addressed** state; invocations = program id + **account list** + **instruction data**; no EVM-style “methods” at the syscall boundary-dispatch via **instruction bytes** (e.g. enums). **Memory map** regions (code\u002Fstack\u002Fheap\u002Finputs) at a glance; **Rust** reducing typical memory-corruption focus. |\n| **Entry \u002F deserialization** | Common **`entrypoint`** and deserialization helpers; distinction between data **serialized by the runtime** vs fields under **attacker control** (e.g. **instruction data**; **account list** selection)-and metadata enforced by the runtime (**signers**, **writable**, **owner**). Links **type confusion** \u002F wrong-account issues to lack of execution-level typing (mitigations such as **hardcoded pubkeys**, **discriminators**-often formalized today via **Anchor**). |\n| **Native programs** | **System Program** and illustrative **CreateAccount** vs **Transfer** **signer** requirements; **ownership** constraints (e.g. SPL token accounts vs system-owned accounts). |\n\nThe introduction explicitly recommends **[Neodyme’s Security Workshop](https:\u002F\u002Fworkshop.neodyme.io\u002F)** for hands-on vulnerability classes; this article complements it with **fundamentals-first** runtime context.\n\n## How to combine with blockint\n\n| Need | Skill |\n|------|--------|\n| Hands-on vulnerable levels | **neodyme-solana-security-workshop** |\n| Anchor exploit\u002Fmitigation snippets | **sealevel-attacks-solana** |\n| Audit \u002F review workflow | **solana-defi-vulnerability-analyst-agent** |\n| Doc indexes & tooling | **solana-onchain-intelligence-resources** |\n\n## Guardrails\n\n- **Staleness** - published **2022**; Solana **runtime**, **program IDs**, and **best practices** evolve-cross-check **[Solana documentation](https:\u002F\u002Fsolana.com\u002Fdocs)** and current **SIMD** \u002F release notes for material facts.  \n- **Not a specification** - blog is **pedagogical**; final authority is **source code** and **on-chain behavior**.  \n- **Ethics** - use understanding for **defense**, **audits**, and **responsible disclosure**, not theft or unauthorized exploitation.\n\n**Goal:** a stable pointer to **[osec.io Solana security intro](https:\u002F\u002Fosec.io\u002Fblog\u002F2022-03-14-solana-security-intro)** for **runtime-aware** Solana security reasoning in blockint.\n","# Osec - Solana: An Auditor’s Introduction (reference)\n\n**Educational routing only.** This skill does **not** reproduce the full article or code excerpts. Read the **live** post for complete detail.\n\n## Canonical URL\n\n- **[Solana: An Auditor’s Introduction](https:\u002F\u002Fosec.io\u002Fblog\u002F2022-03-14-solana-security-intro)** - [osec.io](https:\u002F\u002Fosec.io\u002F) blog, **14 March 2022**.\n\n**Publisher:** [Otter Sec](https:\u002F\u002Fosec.io\u002F) \u002F Otter Audits LLC (smart contract security audits; per site footer).\n\n## What the article covers (outline)\n\nThe post frames **Solana program security** from a **researcher \u002F auditor** lens: how the **runtime** executes contracts, where **trust boundaries** sit, and what an attacker can influence.\n\n| Theme | Topics (high level) |\n|-------|---------------------|\n| **Execution model** | Programs as **eBPF ELF** loaded via **BPF Loader**; accounts as **pubkey-addressed** state; invocations = program id + **account list** + **instruction data**; no EVM-style “methods” at the syscall boundary-dispatch via **instruction bytes** (e.g. enums). **Memory map** regions (code\u002Fstack\u002Fheap\u002Finputs) at a glance; **Rust** reducing typical memory-corruption focus. |\n| **Entry \u002F deserialization** | Common **`entrypoint`** and deserialization helpers; distinction between data **serialized by the runtime** vs fields under **attacker control** (e.g. **instruction data**; **account list** selection)-and metadata enforced by the runtime (**signers**, **writable**, **owner**). Links **type confusion** \u002F wrong-account issues to lack of execution-level typing (mitigations such as **hardcoded pubkeys**, **discriminators**-often formalized today via **Anchor**). |\n| **Native programs** | **System Program** and illustrative **CreateAccount** vs **Transfer** **signer** requirements; **ownership** constraints (e.g. SPL token accounts vs system-owned accounts). |\n\nThe introduction explicitly recommends **[Neodyme’s Security Workshop](https:\u002F\u002Fworkshop.neodyme.io\u002F)** for hands-on vulnerability classes; this article complements it with **fundamentals-first** runtime context.\n\n## How to combine with blockint\n\n| Need | Skill |\n|------|--------|\n| Hands-on vulnerable levels | **neodyme-solana-security-workshop** |\n| Anchor exploit\u002Fmitigation snippets | **sealevel-attacks-solana** |\n| Audit \u002F review workflow | **solana-defi-vulnerability-analyst-agent** |\n| Doc indexes & tooling | **solana-onchain-intelligence-resources** |\n\n## Guardrails\n\n- **Staleness** - published **2022**; Solana **runtime**, **program IDs**, and **best practices** evolve-cross-check **[Solana documentation](https:\u002F\u002Fsolana.com\u002Fdocs)** and current **SIMD** \u002F release notes for material facts.  \n- **Not a specification** - blog is **pedagogical**; final authority is **source code** and **on-chain behavior**.  \n- **Ethics** - use understanding for **defense**, **audits**, and **responsible disclosure**, not theft or unauthorized exploitation.\n\n**Goal:** a stable pointer to **[osec.io Solana security intro](https:\u002F\u002Fosec.io\u002Fblog\u002F2022-03-14-solana-security-intro)** for **runtime-aware** Solana security reasoning in blockint.\n",{"name":5,"description":7},"main","d10fe79c634de337daa2ad2fa82857c8a743616b",".agents\u002Fskills\u002Fosec-solana-auditor-introduction",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 osec-solana-auditor-introduction",{"tool":40,"command":41},"bunx","bunx skills add zkos-labs\u002Fbastion --skill osec-solana-auditor-introduction",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zkos-labs\u002Fbastion --skill osec-solana-auditor-introduction","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fosec-solana-auditor-introduction\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",[],[]]