[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79BM3EFTNQC2NS5KRT2R3ES":3,"skill-same:01M79BM3EFTNQC2NS5KRT2R3ES":46},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M79BM3EFTNQC2NS5KRT2R3ES","cross-contract-analysis",null,"Multi-contract interaction safety analysis. Composability risks, cross-contract reentrancy, state inconsistency across contracts. Used during threat modeling.","sahil-kaushik1\u002FAuditing-Workflow","sahil-kaushik1","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F143880923?v=4","01M79BEEK3947RQYD3WC00K9W3","Sahil Kaushik","01M79BEEKVHPFPTNBDB0GFXBHE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcross-contract-analysis\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cross-contract-analysis\ndescription: >\n  Multi-contract interaction safety analysis. Composability risks, cross-contract\n  reentrancy, state inconsistency across contracts. Used during threat modeling.\n---\n\n# Cross-Contract Analysis Skill\n\n## Purpose\n\nMany real vulnerabilities don't exist inside one contract. Every module may look safe\nindependently while the complete flow is unsafe. This skill catalogs cross-contract\ninteraction patterns that commonly produce vulnerabilities.\n\n## Common Cross-Contract Vulnerability Patterns\n\n### 1. Cross-Contract Reentrancy\nContract A calls Contract B, which calls back into Contract A (or Contract C which\nreads stale state from Contract A).\n\n**Key check**: Does Contract A update its state BEFORE making external calls?\n\n### 2. Inconsistent Oracle Consumption\nMultiple contracts consume the same oracle but at different points in a transaction.\nOne sees the pre-manipulation price, another sees the post-manipulation price.\n\n**Key check**: Is the oracle price cached or re-fetched per call?\n\n### 3. Accounting Desync\nContract A tracks balances internally. Contract B also tracks balances. A state change\nin one is not reflected in the other, creating ghost assets or phantom debt.\n\n**Key check**: Are there multiple sources of truth for the same quantity?\n\n### 4. Privilege Escalation via Composability\nContract A gives Contract B certain permissions. Contract B has a public function that\nContract A's developers didn't consider, allowing an attacker to use B as a proxy to\naffect A's state.\n\n**Key check**: Does the privilege granted to B exceed what's needed?\n\n### 5. State Transition Race Conditions\nMulti-step operations spanning contracts can be front-run or interleaved with other\noperations, leaving the system in an inconsistent state.\n\n**Key check**: Are multi-step operations atomic or interruptible?\n\n### 6. Flash Loan Amplified Cross-Contract Attacks\nA flash loan can temporarily alter state in Contract A (e.g., inflate a balance),\nthen exploit Contract B which reads that inflated state.\n\n**Key check**: Does Contract B rely on Contract A's spot state for critical calculations?\n\n## Analysis Protocol\n\n1. Map all inter-contract call sites (from SAST integrator output)\n2. For each call: what state can the callee observe? What state can it modify?\n3. For each pair of contracts: is there shared state? Shared dependencies?\n4. Generate cross-contract tasks for the Threat Modeler\n\n## Output\n\nFeed observations into the Threat Modeler for task generation. Cross-contract tasks\nshould have explicit multi-contract execution paths in their task definition.\n","# Cross-Contract Analysis Skill\n\n## Purpose\n\nMany real vulnerabilities don't exist inside one contract. Every module may look safe\nindependently while the complete flow is unsafe. This skill catalogs cross-contract\ninteraction patterns that commonly produce vulnerabilities.\n\n## Common Cross-Contract Vulnerability Patterns\n\n### 1. Cross-Contract Reentrancy\nContract A calls Contract B, which calls back into Contract A (or Contract C which\nreads stale state from Contract A).\n\n**Key check**: Does Contract A update its state BEFORE making external calls?\n\n### 2. Inconsistent Oracle Consumption\nMultiple contracts consume the same oracle but at different points in a transaction.\nOne sees the pre-manipulation price, another sees the post-manipulation price.\n\n**Key check**: Is the oracle price cached or re-fetched per call?\n\n### 3. Accounting Desync\nContract A tracks balances internally. Contract B also tracks balances. A state change\nin one is not reflected in the other, creating ghost assets or phantom debt.\n\n**Key check**: Are there multiple sources of truth for the same quantity?\n\n### 4. Privilege Escalation via Composability\nContract A gives Contract B certain permissions. Contract B has a public function that\nContract A's developers didn't consider, allowing an attacker to use B as a proxy to\naffect A's state.\n\n**Key check**: Does the privilege granted to B exceed what's needed?\n\n### 5. State Transition Race Conditions\nMulti-step operations spanning contracts can be front-run or interleaved with other\noperations, leaving the system in an inconsistent state.\n\n**Key check**: Are multi-step operations atomic or interruptible?\n\n### 6. Flash Loan Amplified Cross-Contract Attacks\nA flash loan can temporarily alter state in Contract A (e.g., inflate a balance),\nthen exploit Contract B which reads that inflated state.\n\n**Key check**: Does Contract B rely on Contract A's spot state for critical calculations?\n\n## Analysis Protocol\n\n1. Map all inter-contract call sites (from SAST integrator output)\n2. For each call: what state can the callee observe? What state can it modify?\n3. For each pair of contracts: is there shared state? Shared dependencies?\n4. Generate cross-contract tasks for the Threat Modeler\n\n## Output\n\nFeed observations into the Threat Modeler for task generation. Cross-contract tasks\nshould have explicit multi-contract execution paths in their task definition.\n",{"name":5,"description":7},"main","39a25d63191d67efe43cdce5b7507069e2307f0f",".claude\u002Fskills\u002Fcross-contract-analysis","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1","https:\u002F\u002Fdrive.google.com\u002Ffile\u002Fd\u002F1Te4TcrpgcN4j8DsYqVdjPl4QXVbs5XXo\u002Fview?usp=drive_link","Web3 security researcher \u002F developer","2026-10-18 15:17:21",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add sahil-kaushik1\u002FAuditing-Workflow --skill cross-contract-analysis",{"tool":38,"command":39},"bunx","bunx skills add sahil-kaushik1\u002FAuditing-Workflow --skill cross-contract-analysis",{"tool":41,"command":42},"pnpm","pnpm dlx skills add sahil-kaushik1\u002FAuditing-Workflow --skill cross-contract-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcross-contract-analysis\u002FSKILL.md",true,[],[47,53,59,66,73,80],{"skillNo":48,"name":49,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M79BSEAG0SS9CC2EN1S51K2X","stripe-patterns","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsync\u002Frendertrust\u002F.claude\u002Fskills\u002Fstripe-patterns\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M79BSBAZXQBWCPKYJP38A35B","payment-patterns","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsync\u002Fkeryk-ai\u002F.claude\u002Fskills\u002Fpayment-patterns\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79BS8PKZXFGBNQBS2GHNXZW","testing-patterns","Testing patterns for Jest and Playwright. Use when writing tests, setting up test fixtures, or validating RLS enforcement. Routes to existing test conventions.","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Ftesting-patterns\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79BS3PR92A4QNEJAFNDKB2G","team-coordination","Agent Teams orchestration patterns for multi-agent SAFe workflows. Use when spawning agent teams, coordinating teammates, enforcing quality gates via task dependencies, or orchestrating the 11-agent SAFe pipeline. Covers team creation, messaging, shared task lists, and SAFe gate enforcement. Do NOT use for single-agent or simple subagent workflows.","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fteam-coordination\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79BRZ422QD8D5QHQMXAVPWZ","task-compilation","Compile broad audit goals into structured proof obligations with 9 mandatory fields. Used after decomposition by the Threat Modeler agent.","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Ftask-compilation\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M79BRV2MK2AJZBNSE2BETP28","storage-layout-analysis","Proxy patterns, slot collisions, upgrade safety. Used during decomposition to identify storage-related vulnerabilities in upgradeable contracts.","https:\u002F\u002Fgithub.com\u002Fsahil-kaushik1\u002FAuditing-Workflow\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fstorage-layout-analysis\u002FSKILL.md",[],[]]