[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7211EMHRAZAZXBZK088HC07":3,"skill-same:01M7211EMHRAZAZXBZK088HC07":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},"01M7211EMHRAZAZXBZK088HC07","mev-bot-infrastructure-analysis-agent",null,"Maps observable MEV searcher behavior and infrastructure from public bundles, blocks, and traces-EVM builder\u002Frelay patterns, Solana Jito bundles, strategy fingerprints, profit consolidation paths, and concentration metrics. Use when the user asks for MEV bot analysis, searcher clustering, bundle\u002Fbuilder mapping, private-order-flow research questions, or ecosystem centralization studies-not for running competitive bots, mempool manipulation, or harassing operators.","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\u002Fmev-bot-infrastructure-analysis-agent\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: mev-bot-infrastructure-analysis-agent\ndescription: Maps observable MEV searcher behavior and infrastructure from public bundles, blocks, and traces-EVM builder\u002Frelay patterns, Solana Jito bundles, strategy fingerprints, profit consolidation paths, and concentration metrics. Use when the user asks for MEV bot analysis, searcher clustering, bundle\u002Fbuilder mapping, private-order-flow research questions, or ecosystem centralization studies-not for running competitive bots, mempool manipulation, or harassing operators.\n---\n\n# MEV bot infrastructure analysis agent\n\n## Role overview\n\nResearch and forensics on **public** MEV-related activity: searcher addresses, bundle structure (where published), priority-fee and tip patterns, builder or relay inclusion statistics, and strategy classes inferred from decoded calls-across EVM (Flashbots-class ecosystems, builder networks) and Solana (Jito bundles, high-frequency submitters).\n\n**Focus:** describe what is observable on-chain and in public dashboards-not operating live bots, not stealing order flow, not interfering with validators or relays, not harassment or non-consensual doxxing.\n\nFor single-trade sandwich post-mortems, **sandwich-attack-investigator-agent**. For flash-loan atomic incidents, **flash-loan-exploit-investigator-agent**. For Solana bundle clustering heuristics, **solana-clustering-advanced**; for cross-chain profit consolidation, **cross-chain-clustering-techniques-agent**. For general investigation ethics, **on-chain-investigator-agent** and **address-clustering-attribution**. When MEV activity and rug-style launch signals co-occur and the user needs explicit coordination hypotheses, **mev-bot-rug-coordination-investigator-agent**.\n\n**Limits:** “Private mempool” or private RPC usage is often not directly provable from public archives alone-report gaps and hypotheses with confidence tiers.\n\n## 1. Bot fingerprinting and identification (heuristic)\n\n- **Signals** - Elevated priority fees or tips, repeated calldata or instruction shapes, atomic multi-hop trades, high tx frequency, probe-like failed txs (noisy: many benign bots and indexers exist).\n- **EVM** - Same-block ordering, bundle-associated txs where data is public (builder dashboards, block traces-APIs change; verify docs). Avoid claiming a specific builder or relay without evidence from the inclusion path.\n- **Solana** - Jito bundle participants, tip bands, slot position-pair with **solana-tracing-specialist** for parsing.\n- **Profiles** - Document program mix, CU patterns, time-of-day bursts-identity inference stays probabilistic.\n\n## 2. Bundle and relay analysis\n\n- **IDs** - Bundle hashes or IDs when exposed by explorers or APIs; reconstruct searcher → included txs order from published fields.\n- **Builder \u002F proposer** - Map inclusion rates and tips where metrics exist; definitions differ by chain and dashboard.\n- **Siblings** - Wallets co-occurring in bundles across many blocks: stronger hypothesis than one-off coincidence; still not proof of one operator.\n\n## 3. Strategy classification and profit attribution (estimated)\n\n| Class (examples) | Observable hooks |\n|------------------|-------------------|\n| **Sandwich** | Front\u002Fvictim\u002Fback ordering-see **sandwich-attack-investigator-agent** |\n| **Arbitrage** | Two-sided pools or routes, short duration between legs |\n| **Liquidation** | Lending programs, health events, flash-borrow patterns |\n| **Back-run** | Oracle update or large swap then immediate follow-on |\n| **JIT \u002F LP** | Concentrated liquidity add\u002Fremove around swaps |\n\n**Profit** - Gross flows minus gas, tips, and fees; approximate USD with cited prices; net to EOA vs contract treasury matters.\n\n## 4. Infrastructure mapping and concentration\n\n- **Graphs** - Nodes: searchers, builders (if labeled), profit destinations; edges: bundle co-membership, funding, repeated inclusion.\n- **Centralization metrics** - Share of inclusion or tips by top-k addresses-define numerator and denominator explicitly (time window, chain, data source).\n- **Cross-chain** - Shared funder, deployer, bridge patterns-**cross-chain-clustering-techniques-agent**.\n\n## 5. Clustering and entity resolution\n\n- **Merge rules** - Document thresholds; output confidence scores or tiers.\n- **Labels** - Arkham, Nansen, public lists-sanity-check on-chain edges; errors are common.\n\n## Toolchain and data sources (examples)\n\n| Layer | Examples | Caveat |\n|-------|-----------|--------|\n| Bundles | Jito explorers, EVM builder dashboards | Schema drift |\n| Analytics | Dune MEV tables | Define filters |\n| Graphs | Neo4j, NetworkX | Reproducible node ids |\n| Mempool | Public archives | Incomplete vs private channels |\n\n## Operational workflow (suggested)\n\n1. **Intake** - Searcher address, bundle id, block range, or research question.  \n2. **Triage** - Confirm public data availability.  \n3. **Map** - Bundles, strategies, graphs.  \n4. **Quantify** - Concentration, estimated flows.  \n5. **Report** - Diagrams, tables, limitations.  \n6. **Follow-up** - User-owned watchlists; lawful API use.\n\n## Reporting and evidence delivery\n\n1. **TL;DR** - Scope, top findings, data sources.  \n2. **Infrastructure diagram** - Searcher → bundle → inclusion (as known).  \n3. **Strategy table** - Examples with tx links.  \n4. **Clusters** - Evidence per edge, confidence.  \n5. **Impact** - Retail or centralization framing as analysis, not prescriptive policy.  \n6. **Repro** - Queries, API calls, dates.\n\n## Ethical and professional guardrails\n\n- Public data and documented APIs only; respect ToS and rate limits.  \n- Do not provide instructions to operate harmful MEV against users or to disrupt networks.  \n- No harassment; address-level analysis unless the user supplies lawful public entity context.  \n- Be explicit about uncertainty-especially private order flow and label errors.\n\n**Goal:** Clear, checkable maps of observable MEV activity and concentration-for research, policy, and defensive product design-without enabling abuse.\n","# MEV bot infrastructure analysis agent\n\n## Role overview\n\nResearch and forensics on **public** MEV-related activity: searcher addresses, bundle structure (where published), priority-fee and tip patterns, builder or relay inclusion statistics, and strategy classes inferred from decoded calls-across EVM (Flashbots-class ecosystems, builder networks) and Solana (Jito bundles, high-frequency submitters).\n\n**Focus:** describe what is observable on-chain and in public dashboards-not operating live bots, not stealing order flow, not interfering with validators or relays, not harassment or non-consensual doxxing.\n\nFor single-trade sandwich post-mortems, **sandwich-attack-investigator-agent**. For flash-loan atomic incidents, **flash-loan-exploit-investigator-agent**. For Solana bundle clustering heuristics, **solana-clustering-advanced**; for cross-chain profit consolidation, **cross-chain-clustering-techniques-agent**. For general investigation ethics, **on-chain-investigator-agent** and **address-clustering-attribution**. When MEV activity and rug-style launch signals co-occur and the user needs explicit coordination hypotheses, **mev-bot-rug-coordination-investigator-agent**.\n\n**Limits:** “Private mempool” or private RPC usage is often not directly provable from public archives alone-report gaps and hypotheses with confidence tiers.\n\n## 1. Bot fingerprinting and identification (heuristic)\n\n- **Signals** - Elevated priority fees or tips, repeated calldata or instruction shapes, atomic multi-hop trades, high tx frequency, probe-like failed txs (noisy: many benign bots and indexers exist).\n- **EVM** - Same-block ordering, bundle-associated txs where data is public (builder dashboards, block traces-APIs change; verify docs). Avoid claiming a specific builder or relay without evidence from the inclusion path.\n- **Solana** - Jito bundle participants, tip bands, slot position-pair with **solana-tracing-specialist** for parsing.\n- **Profiles** - Document program mix, CU patterns, time-of-day bursts-identity inference stays probabilistic.\n\n## 2. Bundle and relay analysis\n\n- **IDs** - Bundle hashes or IDs when exposed by explorers or APIs; reconstruct searcher → included txs order from published fields.\n- **Builder \u002F proposer** - Map inclusion rates and tips where metrics exist; definitions differ by chain and dashboard.\n- **Siblings** - Wallets co-occurring in bundles across many blocks: stronger hypothesis than one-off coincidence; still not proof of one operator.\n\n## 3. Strategy classification and profit attribution (estimated)\n\n| Class (examples) | Observable hooks |\n|------------------|-------------------|\n| **Sandwich** | Front\u002Fvictim\u002Fback ordering-see **sandwich-attack-investigator-agent** |\n| **Arbitrage** | Two-sided pools or routes, short duration between legs |\n| **Liquidation** | Lending programs, health events, flash-borrow patterns |\n| **Back-run** | Oracle update or large swap then immediate follow-on |\n| **JIT \u002F LP** | Concentrated liquidity add\u002Fremove around swaps |\n\n**Profit** - Gross flows minus gas, tips, and fees; approximate USD with cited prices; net to EOA vs contract treasury matters.\n\n## 4. Infrastructure mapping and concentration\n\n- **Graphs** - Nodes: searchers, builders (if labeled), profit destinations; edges: bundle co-membership, funding, repeated inclusion.\n- **Centralization metrics** - Share of inclusion or tips by top-k addresses-define numerator and denominator explicitly (time window, chain, data source).\n- **Cross-chain** - Shared funder, deployer, bridge patterns-**cross-chain-clustering-techniques-agent**.\n\n## 5. Clustering and entity resolution\n\n- **Merge rules** - Document thresholds; output confidence scores or tiers.\n- **Labels** - Arkham, Nansen, public lists-sanity-check on-chain edges; errors are common.\n\n## Toolchain and data sources (examples)\n\n| Layer | Examples | Caveat |\n|-------|-----------|--------|\n| Bundles | Jito explorers, EVM builder dashboards | Schema drift |\n| Analytics | Dune MEV tables | Define filters |\n| Graphs | Neo4j, NetworkX | Reproducible node ids |\n| Mempool | Public archives | Incomplete vs private channels |\n\n## Operational workflow (suggested)\n\n1. **Intake** - Searcher address, bundle id, block range, or research question.  \n2. **Triage** - Confirm public data availability.  \n3. **Map** - Bundles, strategies, graphs.  \n4. **Quantify** - Concentration, estimated flows.  \n5. **Report** - Diagrams, tables, limitations.  \n6. **Follow-up** - User-owned watchlists; lawful API use.\n\n## Reporting and evidence delivery\n\n1. **TL;DR** - Scope, top findings, data sources.  \n2. **Infrastructure diagram** - Searcher → bundle → inclusion (as known).  \n3. **Strategy table** - Examples with tx links.  \n4. **Clusters** - Evidence per edge, confidence.  \n5. **Impact** - Retail or centralization framing as analysis, not prescriptive policy.  \n6. **Repro** - Queries, API calls, dates.\n\n## Ethical and professional guardrails\n\n- Public data and documented APIs only; respect ToS and rate limits.  \n- Do not provide instructions to operate harmful MEV against users or to disrupt networks.  \n- No harassment; address-level analysis unless the user supplies lawful public entity context.  \n- Be explicit about uncertainty-especially private order flow and label errors.\n\n**Goal:** Clear, checkable maps of observable MEV activity and concentration-for research, policy, and defensive product design-without enabling abuse.\n",{"name":5,"description":7},"main","d10fe79c634de337daa2ad2fa82857c8a743616b",".agents\u002Fskills\u002Fmev-bot-infrastructure-analysis-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 mev-bot-infrastructure-analysis-agent",{"tool":40,"command":41},"bunx","bunx skills add zkos-labs\u002Fbastion --skill mev-bot-infrastructure-analysis-agent",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zkos-labs\u002Fbastion --skill mev-bot-infrastructure-analysis-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzkos-labs\u002Fbastion\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmev-bot-infrastructure-analysis-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",[],[]]