[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M720YCEWA40M945VASE6WEZZ":3,"skill-same:01M720YCEWA40M945VASE6WEZZ":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},"01M720YCEWA40M945VASE6WEZZ","behavioral-risk-screening-concepts",null,"Educational map of behavioral risk screening-volume, velocity, and transit-style heuristics at address and transaction level. Use when the user asks about suspicious pattern detection, structuring-like activity, rapid fund movement, or AML-style behavior rules-not for tuning systems to evade monitoring or for legal conclusions.","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\u002Fbehavioral-risk-screening-concepts\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: behavioral-risk-screening-concepts\ndescription: Educational map of behavioral risk screening-volume, velocity, and transit-style heuristics at address and transaction level. Use when the user asks about suspicious pattern detection, structuring-like activity, rapid fund movement, or AML-style behavior rules-not for tuning systems to evade monitoring or for legal conclusions.\n---\n\n# Behavioral risk screening (concepts)\n\n**Educational reference only.** Heuristic alerts are **not** proof of crime. Investigate with **crypto-investigation-compliance**, **address-clustering-attribution**, and on-chain evidence. For **label-based** exposure (sanctions, scam tags), see **risk-exposure-screening-concepts**. Product specifics live in your vendor docs (**phalcon-compliance-documentation** where applicable).\n\n## Behavioral Risk Engine (idea)\n\nA **behavioral risk engine** flags **suspicious transaction patterns** using **statistics and rules** (thresholds, windows, frequencies) rather than-or in addition to-static address labels. Baselines may be **global**, **peer-group**, or **customer-specific**. False positives are common; triage before escalation.\n\n## Address-level behavior (common templates)\n\nMany compliance stacks offer **address-centric** rules similar to the following:\n\n| Template | What it approximates | Notes |\n|----------|----------------------|--------|\n| **Large-value transfers** | Outbound or aggregate volume **far above** a typical-user or rolling baseline | Often uses USD notional at observation time; threshold is **configurable**. |\n| **High-frequency transfers** | Many transfers in a **short window**, sometimes many **just below** a reporting or alert threshold (“structuring-like” pattern in traditional AML language) | Requires **count** and **time** bounds; may filter by asset. |\n| **Transit \u002F pass-through** | Address **receives** then **sends** most funds **quickly**, acting as an **intermediary** | Used as a **layering**-style signal; legitimate payment processors can resemble this-context matters. |\n\n**Illustrative scenarios (hypothetical):**\n\n- A wallet sends a **single** outbound transfer whose notional is **far above** the configured large-value threshold.  \n- An address sends **fifteen** transfers of **just under** a chosen threshold within **24 hours**.  \n- An address **receives** a large amount and **forwards** nearly all of it **within minutes** to other addresses.\n\nUse **valid** chain identifiers in real work; examples here stay **generic** to avoid implying real flagged wallets.\n\n## Transaction-level behavior (common templates)\n\nAt **single-transaction** granularity, platforms often add:\n\n| Template | What it approximates | Notes |\n|----------|----------------------|--------|\n| **Large-value transfer** | Transfer **amount** exceeds a **user-defined** notional cap | May apply per asset, per corridor, or per counterparty class. |\n| **Rapid transit** | Funds **leave** shortly after **arrival** along a monitored path (same tx chain or multi-hop within a **time** window) | “Rapid” is **policy-defined** (for example within **N** minutes). Overlaps with **transit** heuristics at graph level. |\n\n**Illustrative scenario:** a transfer exceeds a **$100k** policy threshold, or value moves **A → B** within **five minutes** while policy treats **ten minutes** as the rapid-transit window.\n\n## Relationship to exposure screening\n\n| Engine style | Focus |\n|--------------|--------|\n| **Exposure** (see **risk-exposure-screening-concepts**) | **Who** the funds **touched**-labels, hops, taint-style exposure. |\n| **Behavioral** (this skill) | **How** the address or tx **behaves**-size, speed, frequency, pass-through timing. |\n\nBoth may fire together; analysts should **reconcile** narratives and avoid double-counting the same fact pattern.\n\n## Guardrails\n\n- **Do not** assist with **structuring** advice to **evade** reporting thresholds or **gaming** monitoring rules.  \n- **Do not** treat alerts as **adverse media** or **legal** findings without **case-level** review.  \n- **Legitimate** businesses (payroll, market makers, bridges) can trigger **behavioral** rules-use **corroboration** and **off-chain** context when available.\n\n**Goal:** shared vocabulary for **behavioral** AML-style pattern concepts aligned with common commercial monitoring templates, without binding any **specific** product configuration.\n","# Behavioral risk screening (concepts)\n\n**Educational reference only.** Heuristic alerts are **not** proof of crime. Investigate with **crypto-investigation-compliance**, **address-clustering-attribution**, and on-chain evidence. For **label-based** exposure (sanctions, scam tags), see **risk-exposure-screening-concepts**. Product specifics live in your vendor docs (**phalcon-compliance-documentation** where applicable).\n\n## Behavioral Risk Engine (idea)\n\nA **behavioral risk engine** flags **suspicious transaction patterns** using **statistics and rules** (thresholds, windows, frequencies) rather than-or in addition to-static address labels. Baselines may be **global**, **peer-group**, or **customer-specific**. False positives are common; triage before escalation.\n\n## Address-level behavior (common templates)\n\nMany compliance stacks offer **address-centric** rules similar to the following:\n\n| Template | What it approximates | Notes |\n|----------|----------------------|--------|\n| **Large-value transfers** | Outbound or aggregate volume **far above** a typical-user or rolling baseline | Often uses USD notional at observation time; threshold is **configurable**. |\n| **High-frequency transfers** | Many transfers in a **short window**, sometimes many **just below** a reporting or alert threshold (“structuring-like” pattern in traditional AML language) | Requires **count** and **time** bounds; may filter by asset. |\n| **Transit \u002F pass-through** | Address **receives** then **sends** most funds **quickly**, acting as an **intermediary** | Used as a **layering**-style signal; legitimate payment processors can resemble this-context matters. |\n\n**Illustrative scenarios (hypothetical):**\n\n- A wallet sends a **single** outbound transfer whose notional is **far above** the configured large-value threshold.  \n- An address sends **fifteen** transfers of **just under** a chosen threshold within **24 hours**.  \n- An address **receives** a large amount and **forwards** nearly all of it **within minutes** to other addresses.\n\nUse **valid** chain identifiers in real work; examples here stay **generic** to avoid implying real flagged wallets.\n\n## Transaction-level behavior (common templates)\n\nAt **single-transaction** granularity, platforms often add:\n\n| Template | What it approximates | Notes |\n|----------|----------------------|--------|\n| **Large-value transfer** | Transfer **amount** exceeds a **user-defined** notional cap | May apply per asset, per corridor, or per counterparty class. |\n| **Rapid transit** | Funds **leave** shortly after **arrival** along a monitored path (same tx chain or multi-hop within a **time** window) | “Rapid” is **policy-defined** (for example within **N** minutes). Overlaps with **transit** heuristics at graph level. |\n\n**Illustrative scenario:** a transfer exceeds a **$100k** policy threshold, or value moves **A → B** within **five minutes** while policy treats **ten minutes** as the rapid-transit window.\n\n## Relationship to exposure screening\n\n| Engine style | Focus |\n|--------------|--------|\n| **Exposure** (see **risk-exposure-screening-concepts**) | **Who** the funds **touched**-labels, hops, taint-style exposure. |\n| **Behavioral** (this skill) | **How** the address or tx **behaves**-size, speed, frequency, pass-through timing. |\n\nBoth may fire together; analysts should **reconcile** narratives and avoid double-counting the same fact pattern.\n\n## Guardrails\n\n- **Do not** assist with **structuring** advice to **evade** reporting thresholds or **gaming** monitoring rules.  \n- **Do not** treat alerts as **adverse media** or **legal** findings without **case-level** review.  \n- **Legitimate** businesses (payroll, market makers, bridges) can trigger **behavioral** rules-use **corroboration** and **off-chain** context when available.\n\n**Goal:** shared vocabulary for **behavioral** AML-style pattern concepts aligned with common commercial monitoring templates, without binding any **specific** product configuration.\n",{"name":5,"description":7},"main","d10fe79c634de337daa2ad2fa82857c8a743616b",".agents\u002Fskills\u002Fbehavioral-risk-screening-concepts",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 behavioral-risk-screening-concepts",{"tool":40,"command":41},"bunx","bunx skills add zkos-labs\u002Fbastion --skill behavioral-risk-screening-concepts",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zkos-labs\u002Fbastion --skill behavioral-risk-screening-concepts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbehavioral-risk-screening-concepts\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",[],[]]