[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M720ZZREBKCKXPJ3AZXE871B":3,"skill-same:01M720ZZREBKCKXPJ3AZXE871B":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},"01M720ZZREBKCKXPJ3AZXE871B","crypto-investigation-compliance",null,"Maps high-level crypto crime categories, safe and ethical OSINT plus on-chain investigation workflow, and victim reporting posture. Use when the user asks about scam types, pig butchering, rug pulls, tracing stolen funds ethically, compliance-adjacent investigation, or how to document cases for authorities.","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\u002Fcrypto-investigation-compliance\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: crypto-investigation-compliance\ndescription: Maps high-level crypto crime categories, safe and ethical OSINT plus on-chain investigation workflow, and victim reporting posture. Use when the user asks about scam types, pig butchering, rug pulls, tracing stolen funds ethically, compliance-adjacent investigation, or how to document cases for authorities.\n---\n\n# Crypto investigation and compliance awareness\n\nEducational workflow guidance only. **Not** legal advice. Do **not** assist with laundering, sanctions evasion, harassment, or non-consensual deanonymization.\n\n## Crypto crime - conceptual map (high level)\n\n**Crypto crime** spans theft, fraud, laundering, ransomware, sanctions evasion, terrorist financing, market abuse, and more. Responses blend **chain tracing**, **OSINT**, and **legal** process.\n\n**Common terms (non-exhaustive):**\n\n- **Pig butchering** - long-build trust → fake investment platform  \n- **Rug pull** - insiders drain or abandon  \n- **Ponzi \u002F yield scam** - returns from new money  \n- **DeFi exploit \u002F bridge hack** - contract or infra failure  \n- **Mixer \u002F tumbler** - trail obfuscation (lawful privacy vs illicit use is context-specific)  \n- **Drainer \u002F phishing** - malicious signing  \n- **Pump-and-dump \u002F wash trading** - manipulation  \n\nChains attract misuse due to **pseudonymity**, **speed**, **cross-border** reach, **programmability**; obfuscation complicates but rarely perfects hiding.\n\n**Victims:** report quickly via **official** national cybercrime channels where applicable; on-chain timelines can support **law enforcement** filings-check **local** rules.\n\n## CEX deposits, stablecoins, and off-chain gaps\n\n- **Exchange deposits and withdrawals** - On-chain you often see transfers into a labeled hot-wallet cluster; tying that to a specific customer account usually requires exchange cooperation or legal process-do not treat analytics labels as proof alone.\n- **Stablecoins (USDC, USDT, etc.)** - Track mints, burns, and large transfers on-chain; issuer blacklists and freezes are not fully observable from public RPC alone.\n- **Documentation** - Separate on-chain facts from what requires custodial or legal follow-up.\n\n## Ethical investigation workflow\n\n1. **Anchor** - hashes, addresses, contracts, amounts, times  \n2. **Explore** - explorers; contract path  \n3. **Cluster** - treat as probabilistic (see **address-clustering-attribution**)  \n4. **Attribute cautiously** - strong evidence only  \n5. **Document** - sources, fact vs inference  \n6. **Escalate** - professionals \u002F authorities for recovery  \n\n**Do not:** doxx, accuse without evidence, bypass legal process.\n\n## Related skills\n\n- **address-clustering-attribution** - clustering mechanics  \n- **blockchain-analytics-operations** - AML-style platform context  \n- **bellingcat-investigation-toolkit** - [Bellingcat’s OSINT tool catalog](https:\u002F\u002Fbellingcat.gitbook.io\u002Ftoolkit) (general open-source investigation tools; verify live links)  \n- **evm-solidity-defi-triage-agent** - EVM Solidity DeFi contract triage (complements chain tracing)  \n- **solana-onchain-intelligence-resources** - includes [Solana Policy Institute](https:\u002F\u002Fwww.solanapolicyinstitute.org\u002F) for **public** policy and regulatory **education** on Solana (not legal advice); use for context separate from per-case facts  \n- **range-ai-investigation-playbook** - structured **Range MCP** investigation steps (risk, sanctions, flows, cross-chain) and prompt template; labels are **not** legal findings  \n- **phalcon-compliance-documentation** - canonical URL for **Phalcon Compliance** **public** documentation (product operator reference; not legal advice)  \n- **risk-exposure-screening-concepts** - risk **indicator** categories, exposure metrics, address vs transaction screening templates (commercial screening vocabulary; not a legal finding)  \n- **behavioral-risk-screening-concepts** - volume, velocity, transit-style **behavior** rules at address and transaction level (alerts are not proof of crime)  \n- **address-screening-workflow-concepts** - tags\u002Fmarkers, bulk import, address list\u002Fdetail, blacklist\u002Fwhitelist **policy** patterns in screening UIs (not legal advice)  \n- **transaction-screening-workflow-concepts** - tx\u002Ftransfer screening, **deposit** vs **withdrawal**, STR-style **export** hooks in products (not legal filing advice)  \n","# Crypto investigation and compliance awareness\n\nEducational workflow guidance only. **Not** legal advice. Do **not** assist with laundering, sanctions evasion, harassment, or non-consensual deanonymization.\n\n## Crypto crime - conceptual map (high level)\n\n**Crypto crime** spans theft, fraud, laundering, ransomware, sanctions evasion, terrorist financing, market abuse, and more. Responses blend **chain tracing**, **OSINT**, and **legal** process.\n\n**Common terms (non-exhaustive):**\n\n- **Pig butchering** - long-build trust → fake investment platform  \n- **Rug pull** - insiders drain or abandon  \n- **Ponzi \u002F yield scam** - returns from new money  \n- **DeFi exploit \u002F bridge hack** - contract or infra failure  \n- **Mixer \u002F tumbler** - trail obfuscation (lawful privacy vs illicit use is context-specific)  \n- **Drainer \u002F phishing** - malicious signing  \n- **Pump-and-dump \u002F wash trading** - manipulation  \n\nChains attract misuse due to **pseudonymity**, **speed**, **cross-border** reach, **programmability**; obfuscation complicates but rarely perfects hiding.\n\n**Victims:** report quickly via **official** national cybercrime channels where applicable; on-chain timelines can support **law enforcement** filings-check **local** rules.\n\n## CEX deposits, stablecoins, and off-chain gaps\n\n- **Exchange deposits and withdrawals** - On-chain you often see transfers into a labeled hot-wallet cluster; tying that to a specific customer account usually requires exchange cooperation or legal process-do not treat analytics labels as proof alone.\n- **Stablecoins (USDC, USDT, etc.)** - Track mints, burns, and large transfers on-chain; issuer blacklists and freezes are not fully observable from public RPC alone.\n- **Documentation** - Separate on-chain facts from what requires custodial or legal follow-up.\n\n## Ethical investigation workflow\n\n1. **Anchor** - hashes, addresses, contracts, amounts, times  \n2. **Explore** - explorers; contract path  \n3. **Cluster** - treat as probabilistic (see **address-clustering-attribution**)  \n4. **Attribute cautiously** - strong evidence only  \n5. **Document** - sources, fact vs inference  \n6. **Escalate** - professionals \u002F authorities for recovery  \n\n**Do not:** doxx, accuse without evidence, bypass legal process.\n\n## Related skills\n\n- **address-clustering-attribution** - clustering mechanics  \n- **blockchain-analytics-operations** - AML-style platform context  \n- **bellingcat-investigation-toolkit** - [Bellingcat’s OSINT tool catalog](https:\u002F\u002Fbellingcat.gitbook.io\u002Ftoolkit) (general open-source investigation tools; verify live links)  \n- **evm-solidity-defi-triage-agent** - EVM Solidity DeFi contract triage (complements chain tracing)  \n- **solana-onchain-intelligence-resources** - includes [Solana Policy Institute](https:\u002F\u002Fwww.solanapolicyinstitute.org\u002F) for **public** policy and regulatory **education** on Solana (not legal advice); use for context separate from per-case facts  \n- **range-ai-investigation-playbook** - structured **Range MCP** investigation steps (risk, sanctions, flows, cross-chain) and prompt template; labels are **not** legal findings  \n- **phalcon-compliance-documentation** - canonical URL for **Phalcon Compliance** **public** documentation (product operator reference; not legal advice)  \n- **risk-exposure-screening-concepts** - risk **indicator** categories, exposure metrics, address vs transaction screening templates (commercial screening vocabulary; not a legal finding)  \n- **behavioral-risk-screening-concepts** - volume, velocity, transit-style **behavior** rules at address and transaction level (alerts are not proof of crime)  \n- **address-screening-workflow-concepts** - tags\u002Fmarkers, bulk import, address list\u002Fdetail, blacklist\u002Fwhitelist **policy** patterns in screening UIs (not legal advice)  \n- **transaction-screening-workflow-concepts** - tx\u002Ftransfer screening, **deposit** vs **withdrawal**, STR-style **export** hooks in products (not legal filing advice)  \n",{"name":5,"description":7},"main","d10fe79c634de337daa2ad2fa82857c8a743616b",".agents\u002Fskills\u002Fcrypto-investigation-compliance",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 crypto-investigation-compliance",{"tool":40,"command":41},"bunx","bunx skills add zkos-labs\u002Fbastion --skill crypto-investigation-compliance",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zkos-labs\u002Fbastion --skill crypto-investigation-compliance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcrypto-investigation-compliance\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",[],[]]