[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77XC2JC4ADHG3VNHRSW9FKM":3,"skill-same:01M77XC2JC4ADHG3VNHRSW9FKM":47},{"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":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M77XC2JC4ADHG3VNHRSW9FKM","untrusted-binary-sandbox",null,"Use when asked to safely inspect, sandbox, detonate, run, or dynamically observe untrusted release artifacts, closed-source binaries, JARs, installers, wallet\u002Fprivate-key software, crypto trading bots, or suspicious GitHub releases. Provides a staged static-to-dynamic workflow with VM\u002FDocker isolation, network controls, Solana wallet safety, tracing, evidence capture, and risk reporting.","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fu\u002Funtrusted-binary-sandbox\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: untrusted-binary-sandbox\ndescription: Use when asked to safely inspect, sandbox, detonate, run, or dynamically observe untrusted release artifacts, closed-source binaries, JARs, installers, wallet\u002Fprivate-key software, crypto trading bots, or suspicious GitHub releases. Provides a staged static-to-dynamic workflow with VM\u002FDocker isolation, network controls, Solana wallet safety, tracing, evidence capture, and risk reporting.\n---\n\n# Untrusted Binary Sandbox\n\n## Purpose\n\nUse this skill to plan and execute controlled behavioral observation of untrusted software without trusting the software, its installer, or its documentation. Treat wallet, private-key, trading, MEV, arbitrage, and closed-source crypto tools as high-risk by default.\n\nThis skill does not prove safety. It reduces uncertainty for the exact artifact, configuration, runtime, and observation window tested.\n\n## Non-Negotiables\n\n- Do not run downloaded binaries, JARs, install scripts, release artifacts, or `curl | sh` flows unless the user explicitly approves dynamic execution.\n- Prefer a sacrificial VM\u002FVPS over a production host. Never mount production secrets, SSH keys, browser profiles, Docker socket, cloud credentials, or funded wallets.\n- Never use a real private key during observation. Use invalid keys, empty throwaway wallets, or a tiny-fund wallet only in the final live tier after explicit approval.\n- Pin artifact identity before execution: source URL, version, size, SHA-256, timestamp, and any signature\u002Fdigest metadata.\n- Keep confirmed findings separate from risk signals and unknowns. Report confidence level.\n\n## Workflow\n\n1. Scope the sample:\n   Identify the artifact, claimed purpose, required command, required secrets, network endpoints, supported OS\u002FCPU, and whether the user is asking for static analysis, dynamic observation, or production feasibility.\n\n2. Static triage first:\n   Hash the artifact, inspect archive contents, review scripts\u002Fconfigs, run `file`, `readelf`, `objdump`, `strings`, `jar tf`, or language-specific archive inspection as appropriate. Avoid `ldd` on untrusted ELF files; use `readelf -d` or `objdump -p` instead.\n\n3. Choose the lowest sufficient tier:\n   - Tier 0: no-run static analysis only.\n   - Tier 1: offline Docker run with `network_mode: none`.\n   - Tier 2: internal-only network with mock RPC\u002FAPI\u002FDNS sinks.\n   - Tier 3: controlled egress with allowlisted endpoints and packet\u002FDNS logging.\n   - Tier 4: sacrificial VM\u002FVPS with tiny-fund throwaway wallet for live behavior, only after prior tiers are clean.\n\n4. Build containment:\n   Use non-root users, `read_only` root filesystem, `cap_drop: [ALL]`, `no-new-privileges`, PID\u002FCPU\u002Fmemory limits, tmpfs for scratch, no host networking, no privileged mode, no host path mounts except read-only artifacts\u002Fconfig and writable logs.\n\n5. Instrument before execution:\n   Capture process tree, syscalls, opened files, filesystem writes, DNS queries, outbound connections, child processes, resource use, and any downloaded or modified files. Prefer `strace` inside Linux containers and VM-level packet capture when network is enabled.\n\n6. Execute briefly and repeat:\n   Start with short timeouts such as 60-180 seconds. Repeat with a known-bad config, mock RPC, then controlled egress. Preserve logs and hashes after each run.\n\n7. Report with judgment:\n   Summarize confirmed behavior, suspicious signals, unknowns, confidence, and a go\u002Fno-go recommendation. For wallet software, include a separate private-key exposure assessment.\n\n## Stop Criteria\n\nStop and report immediately if the sample:\n\n- Reads SSH keys, shell history, browser profiles, cloud credentials, `.env` files, unrelated wallet paths, or host-sensitive directories.\n- Writes cron\u002Fsystemd\u002Fprofile startup hooks, modifies shell init files, changes file permissions broadly, or downloads and executes new payloads.\n- Requires root, host networking, Docker socket, privileged mode, broad host mounts, or disabled sandboxing without a clear technical need.\n- Connects to endpoints not declared in config\u002Fdocs, especially paste sites, generic file hosts, Telegram bot APIs, raw IPs, or newly registered domains.\n- Attempts to exfiltrate key material or sends transactions before the expected safe stage.\n\n## Solana And Wallet-Specific Rules\n\n- Never mount `~\u002F.config\u002Fsolana\u002Fid.json` or any funded wallet.\n- Prefer invalid key material or an empty throwaway keypair. Do not print, transform, or store private keys in chat.\n- Use a local mock RPC in Tier 2. In Tier 3, allow only explicit RPC\u002FJito\u002Fsender endpoints.\n- Treat \"encrypt your private key with this binary\" as high-risk behavior, not as a safety feature.\n- Measure failed transactions, priority-fee burn, Jito tips, and RPC rate-limit pressure separately from malware risk.\n\n## Resources\n\n- Read `references\u002Fdocker-sandbox.md` when building the actual Docker or VM containment plan.\n- Read `references\u002Fobservation-checklist.md` when preparing the final evidence report.\n- Use `scripts\u002Fscaffold_sandbox.py` to generate a local sandbox scaffold. It creates Docker Compose files and a mock Solana RPC service, but does not execute the sample by default.\n\n**Appropriate for:** In-depth documentation, API references, database schemas, comprehensive guides, or any detailed information that Codex should reference while working.\n\n### assets\u002F\nFiles not intended to be loaded into context, but rather used within the output Codex produces.\n\n**Examples from other skills:**\n- Brand styling: PowerPoint template files (.pptx), logo files\n- Frontend builder: HTML\u002FReact boilerplate project directories\n- Typography: Font files (.ttf, .woff2)\n\n**Appropriate for:** Templates, boilerplate code, document templates, images, icons, fonts, or any files meant to be copied or used in the final output.\n\n---\n\n**Not every skill requires all three types of resources.**\n","# Untrusted Binary Sandbox\n\n## Purpose\n\nUse this skill to plan and execute controlled behavioral observation of untrusted software without trusting the software, its installer, or its documentation. Treat wallet, private-key, trading, MEV, arbitrage, and closed-source crypto tools as high-risk by default.\n\nThis skill does not prove safety. It reduces uncertainty for the exact artifact, configuration, runtime, and observation window tested.\n\n## Non-Negotiables\n\n- Do not run downloaded binaries, JARs, install scripts, release artifacts, or `curl | sh` flows unless the user explicitly approves dynamic execution.\n- Prefer a sacrificial VM\u002FVPS over a production host. Never mount production secrets, SSH keys, browser profiles, Docker socket, cloud credentials, or funded wallets.\n- Never use a real private key during observation. Use invalid keys, empty throwaway wallets, or a tiny-fund wallet only in the final live tier after explicit approval.\n- Pin artifact identity before execution: source URL, version, size, SHA-256, timestamp, and any signature\u002Fdigest metadata.\n- Keep confirmed findings separate from risk signals and unknowns. Report confidence level.\n\n## Workflow\n\n1. Scope the sample:\n   Identify the artifact, claimed purpose, required command, required secrets, network endpoints, supported OS\u002FCPU, and whether the user is asking for static analysis, dynamic observation, or production feasibility.\n\n2. Static triage first:\n   Hash the artifact, inspect archive contents, review scripts\u002Fconfigs, run `file`, `readelf`, `objdump`, `strings`, `jar tf`, or language-specific archive inspection as appropriate. Avoid `ldd` on untrusted ELF files; use `readelf -d` or `objdump -p` instead.\n\n3. Choose the lowest sufficient tier:\n   - Tier 0: no-run static analysis only.\n   - Tier 1: offline Docker run with `network_mode: none`.\n   - Tier 2: internal-only network with mock RPC\u002FAPI\u002FDNS sinks.\n   - Tier 3: controlled egress with allowlisted endpoints and packet\u002FDNS logging.\n   - Tier 4: sacrificial VM\u002FVPS with tiny-fund throwaway wallet for live behavior, only after prior tiers are clean.\n\n4. Build containment:\n   Use non-root users, `read_only` root filesystem, `cap_drop: [ALL]`, `no-new-privileges`, PID\u002FCPU\u002Fmemory limits, tmpfs for scratch, no host networking, no privileged mode, no host path mounts except read-only artifacts\u002Fconfig and writable logs.\n\n5. Instrument before execution:\n   Capture process tree, syscalls, opened files, filesystem writes, DNS queries, outbound connections, child processes, resource use, and any downloaded or modified files. Prefer `strace` inside Linux containers and VM-level packet capture when network is enabled.\n\n6. Execute briefly and repeat:\n   Start with short timeouts such as 60-180 seconds. Repeat with a known-bad config, mock RPC, then controlled egress. Preserve logs and hashes after each run.\n\n7. Report with judgment:\n   Summarize confirmed behavior, suspicious signals, unknowns, confidence, and a go\u002Fno-go recommendation. For wallet software, include a separate private-key exposure assessment.\n\n## Stop Criteria\n\nStop and report immediately if the sample:\n\n- Reads SSH keys, shell history, browser profiles, cloud credentials, `.env` files, unrelated wallet paths, or host-sensitive directories.\n- Writes cron\u002Fsystemd\u002Fprofile startup hooks, modifies shell init files, changes file permissions broadly, or downloads and executes new payloads.\n- Requires root, host networking, Docker socket, privileged mode, broad host mounts, or disabled sandboxing without a clear technical need.\n- Connects to endpoints not declared in config\u002Fdocs, especially paste sites, generic file hosts, Telegram bot APIs, raw IPs, or newly registered domains.\n- Attempts to exfiltrate key material or sends transactions before the expected safe stage.\n\n## Solana And Wallet-Specific Rules\n\n- Never mount `~\u002F.config\u002Fsolana\u002Fid.json` or any funded wallet.\n- Prefer invalid key material or an empty throwaway keypair. Do not print, transform, or store private keys in chat.\n- Use a local mock RPC in Tier 2. In Tier 3, allow only explicit RPC\u002FJito\u002Fsender endpoints.\n- Treat \"encrypt your private key with this binary\" as high-risk behavior, not as a safety feature.\n- Measure failed transactions, priority-fee burn, Jito tips, and RPC rate-limit pressure separately from malware risk.\n\n## Resources\n\n- Read `references\u002Fdocker-sandbox.md` when building the actual Docker or VM containment plan.\n- Read `references\u002Fobservation-checklist.md` when preparing the final evidence report.\n- Use `scripts\u002Fscaffold_sandbox.py` to generate a local sandbox scaffold. It creates Docker Compose files and a mock Solana RPC service, but does not execute the sample by default.\n\n**Appropriate for:** In-depth documentation, API references, database schemas, comprehensive guides, or any detailed information that Codex should reference while working.\n\n### assets\u002F\nFiles not intended to be loaded into context, but rather used within the output Codex produces.\n\n**Examples from other skills:**\n- Brand styling: PowerPoint template files (.pptx), logo files\n- Frontend builder: HTML\u002FReact boilerplate project directories\n- Typography: Font files (.ttf, .woff2)\n\n**Appropriate for:** Templates, boilerplate code, document templates, images, icons, fonts, or any files meant to be copied or used in the final output.\n\n---\n\n**Not every skill requires all three types of resources.**\n",{"name":5,"description":7},"master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fu\u002Funtrusted-binary-sandbox",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill untrusted-binary-sandbox",{"tool":39,"command":40},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill untrusted-binary-sandbox",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill untrusted-binary-sandbox","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fu\u002Funtrusted-binary-sandbox\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]