[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D468XKGE4HE0J20VJS0VNH":3,"skill-same:01M7D468XKGE4HE0J20VJS0VNH":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":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7D468XKGE4HE0J20VJS0VNH","code-audit",null,"Static security audit of a codebase with inkdex - inkdex-vuln indexes the repository locally, follows data from entry points to sinks and reports vulnerabilities (injections, path traversal, SSRF, secrets, weak crypto, dangerous settings, vulnerable dependencies), then mlab.sh enriches the CVEs. Use when the user asks to scan or audit source code for vulnerabilities, run SAST, map an app's attack surface or unauthenticated routes, trace a data flow, or review the security impact of a change or PR.","mlab-sh\u002Fmlab-claude","mlab-sh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F197380970?v=4","01M7D45Z8NKEZYYHGF1F1HFZ00","Mlab.sh","01M7D45Z9FXN34R73J4E5D9F63",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fcode-audit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: code-audit\ndescription: Static security audit of a codebase with inkdex - inkdex-vuln indexes the repository locally, follows data from entry points to sinks and reports vulnerabilities (injections, path traversal, SSRF, secrets, weak crypto, dangerous settings, vulnerable dependencies), then mlab.sh enriches the CVEs. Use when the user asks to scan or audit source code for vulnerabilities, run SAST, map an app's attack surface or unauthenticated routes, trace a data flow, or review the security impact of a change or PR.\n---\n\n# Code Audit (inkdex)\n\n> CLI details, preflight and output shapes: `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Finkdex-reference.md`. mlab output shapes: `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Ftool-reference.md`.\n\nLocal analysis, cloud context. inkdex finds the path from input to impact in the code; mlab says how exploited the vulnerable dependencies are.\n\n## Workflow\n\n### 1. Preflight\n\n`inkdex-vuln --version` and `inkdex license status` (see the reference: install paths, license activation). Confirm the target: a repository directory. An application (has routes \u002F a main) is scanned as is; a library (package, crate, module) with `--library`.\n\n### 2. Scan\n\n```\ninkdex-vuln scan \u003Cpath> --update --json\n```\n\n`--update` builds or refreshes `.inkdex\u002F`. Add `--library` for a library. Add `--local-sources` only if the user asks to treat environment \u002F arguments \u002F local files as untrusted (a CLI tool, a script run by others). If the network or the license's dependency check is unavailable, the scan still runs: say dependencies were not checked.\n\nFor a PR or change instead of the whole repo: `inkdex index --commit \u003Cbase>`, `inkdex index`, then `inkdex diff \u003Cbase> --sec --markdown` (and `--gate` to tell whether it adds an unsanitized flow).\n\n### 3. Understand the findings\n\n- Start from `critical` \u002F `high` and `proven`. For each, read `meta.steps` (source → sink); if the path is not obvious, `inkdex sec flows --trace` on the sink's category, or `inkdex explain \u003Cfile> --line \u003Cn>` to see what inkdex understood on the line.\n- `verify` findings need the evidence read: decide true \u002F false with the code, say which and why.\n- Attack surface: `inkdex routes --unauthenticated` - list the entry points with no authentication found, and which of them reach a finding.\n- Group findings by root cause (one unvalidated parameter reaching three sinks is one fix).\n\n### 4. Pivot the dependency findings through mlab\n\nFor `VULN-DEP` findings: `meta.aliases` (CVE ids) → `cve_detail` (KEV, EPSS, fixed range), then `actors_by_cve` on KEV \u002F EPSS > 0.5. A dependency marked `imported: false` is declared but never used by the code: lower priority, often a removal.\n\n### 5. Report\n\n```\n## Code audit: \u003Crepo> - verdict \u003CCLEAN | ISSUES | CRITICAL>\n\n**Bottom line:** \u003Cone sentence>\n\n### Exploitable now\n\u003Cper root cause: rule + CWE, route \u002F entry point, source → sink, file:line, why it is reachable, fix>\n\n### To verify\n\u003Cverify findings with your call on each: true \u002F false positive, and why>\n\n### Secrets and settings\n\u003Ckeys to rotate first; TLS off, debug, cookies, CORS - with the config line>\n\n### Vulnerable dependencies\n\u003CKEV \u002F EPSS-prioritized: package, version, CVE, fixed version, imported or not>\n\n### Attack surface\n\u003Cunauthenticated entry points, and which reach a finding>\n\n### Actions\n\u003Cordered fixes; the CI line to keep it fixed: inkdex-vuln scan . --update --fail-on high>\n```\n\n## Rules\n\n- Never run, build or install the audited project to \"confirm\" a finding - the analysis is static on purpose.\n- Never handle the license key: the user activates it (`inkdex license activate`) or sets `INKDEX_KEY` \u002F `INKDEX_TOKEN` themselves.\n- A CLEAN result covers what inkdex models (its languages, frameworks and rules); say what was out of scope (other languages, logic bugs, missing authentication as a design flaw).\n- `scan` exit 1 with `--fail-on` is the gate, not an error; exit 2 is (no index, no license): read stderr.\n","# Code Audit (inkdex)\n\n> CLI details, preflight and output shapes: `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Finkdex-reference.md`. mlab output shapes: `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Ftool-reference.md`.\n\nLocal analysis, cloud context. inkdex finds the path from input to impact in the code; mlab says how exploited the vulnerable dependencies are.\n\n## Workflow\n\n### 1. Preflight\n\n`inkdex-vuln --version` and `inkdex license status` (see the reference: install paths, license activation). Confirm the target: a repository directory. An application (has routes \u002F a main) is scanned as is; a library (package, crate, module) with `--library`.\n\n### 2. Scan\n\n```\ninkdex-vuln scan \u003Cpath> --update --json\n```\n\n`--update` builds or refreshes `.inkdex\u002F`. Add `--library` for a library. Add `--local-sources` only if the user asks to treat environment \u002F arguments \u002F local files as untrusted (a CLI tool, a script run by others). If the network or the license's dependency check is unavailable, the scan still runs: say dependencies were not checked.\n\nFor a PR or change instead of the whole repo: `inkdex index --commit \u003Cbase>`, `inkdex index`, then `inkdex diff \u003Cbase> --sec --markdown` (and `--gate` to tell whether it adds an unsanitized flow).\n\n### 3. Understand the findings\n\n- Start from `critical` \u002F `high` and `proven`. For each, read `meta.steps` (source → sink); if the path is not obvious, `inkdex sec flows --trace` on the sink's category, or `inkdex explain \u003Cfile> --line \u003Cn>` to see what inkdex understood on the line.\n- `verify` findings need the evidence read: decide true \u002F false with the code, say which and why.\n- Attack surface: `inkdex routes --unauthenticated` - list the entry points with no authentication found, and which of them reach a finding.\n- Group findings by root cause (one unvalidated parameter reaching three sinks is one fix).\n\n### 4. Pivot the dependency findings through mlab\n\nFor `VULN-DEP` findings: `meta.aliases` (CVE ids) → `cve_detail` (KEV, EPSS, fixed range), then `actors_by_cve` on KEV \u002F EPSS > 0.5. A dependency marked `imported: false` is declared but never used by the code: lower priority, often a removal.\n\n### 5. Report\n\n```\n## Code audit: \u003Crepo> - verdict \u003CCLEAN | ISSUES | CRITICAL>\n\n**Bottom line:** \u003Cone sentence>\n\n### Exploitable now\n\u003Cper root cause: rule + CWE, route \u002F entry point, source → sink, file:line, why it is reachable, fix>\n\n### To verify\n\u003Cverify findings with your call on each: true \u002F false positive, and why>\n\n### Secrets and settings\n\u003Ckeys to rotate first; TLS off, debug, cookies, CORS - with the config line>\n\n### Vulnerable dependencies\n\u003CKEV \u002F EPSS-prioritized: package, version, CVE, fixed version, imported or not>\n\n### Attack surface\n\u003Cunauthenticated entry points, and which reach a finding>\n\n### Actions\n\u003Cordered fixes; the CI line to keep it fixed: inkdex-vuln scan . --update --fail-on high>\n```\n\n## Rules\n\n- Never run, build or install the audited project to \"confirm\" a finding - the analysis is static on purpose.\n- Never handle the license key: the user activates it (`inkdex license activate`) or sets `INKDEX_KEY` \u002F `INKDEX_TOKEN` themselves.\n- A CLEAN result covers what inkdex models (its languages, frameworks and rules); say what was out of scope (other languages, logic bugs, missing authentication as a design flaw).\n- `scan` exit 1 with `--fail-on` is the gate, not an error; exit 2 is (no index, no license): read stderr.\n",{"name":5,"description":7},"main","0678f3559c0b5576fd964874a3debae3f6b5a31c","plugins\u002Fmlab\u002Fskills\u002Fcode-audit",0,"https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude","https:\u002F\u002Fgithub.com\u002Fmlab-sh","https:\u002F\u002Fmlab.sh","MLAB is a modular security analysis platform for IOC analysis at scale","2026-10-22 03:39:43",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add mlab-sh\u002Fmlab-claude --skill code-audit",{"tool":39,"command":40},"bunx","bunx skills add mlab-sh\u002Fmlab-claude --skill code-audit",{"tool":42,"command":43},"pnpm","pnpm dlx skills add mlab-sh\u002Fmlab-claude --skill code-audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fcode-audit\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},"01M7D494QGV4DTD8PE8NTDHRM4","threat-watch","Generate a threat landscape digest from mlab.sh - recent critical\u002FKEV CVEs filtered to a declared technology stack, with actor attribution. Use when the user asks what is new in vulnerabilities, wants a daily\u002Fweekly threat brief, asks about recent CVEs for a product, or sets up a recurring watch on their stack.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fthreat-watch\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},"01M7D48Z3YTQN4ZHMGTH1EXXR5","supply-chain-audit","Full supply-chain audit of a project - postmortem detects malicious code, install hooks and risky dependencies locally, then mlab.sh enriches what it finds (hashes, endpoints, actors, CVEs). Use when the user asks to audit a project's dependencies or supply chain, check a repo for malicious packages, or vet a codebase before adoption or deployment.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fsupply-chain-audit\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},"01M7D48RXRAHKVAE6SWQT2EN6H","smishing-campaign","Analyze a batch of reported SMS\u002Ftext messages through mlab.sh - score each for smishing, cluster them into campaigns, and extract the shared infrastructure (URLs, callback numbers, sender patterns). Use when the user has multiple reported SMS from users\u002Femployees, or investigates an SMS phishing wave. For a single message, phishing-triage does the job.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fsmishing-campaign\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},"01M7D48KBNYFBJNS9MEHHWMW80","script-triage","Statically analyze a suspicious shell script through mlab.sh - install.sh, cron payloads, CI steps, curl-pipe-sh one-liners. Flags dangerous constructs (download-piped-to-shell, base64 decoding, reverse shells, persistence, anti-forensics, destructive deletes), extracts every IOC and enriches them. Use when the user pastes shell code and asks if it is safe\u002Fmalicious, or provides a .sh file to vet before running it.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fscript-triage\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},"01M7D48E9ZYDPAN85NXAED50E6","sbom-export","Generate a CycloneDX SBOM locally with postmortem and push it through mlab.sh vulnerability scanning - for projects or container images where no single lockfile can be pasted. Use when the user asks for an SBOM, needs vuln scanning of a container image or a multi-ecosystem repo, or when sbom-audit lacks a usable lockfile.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fsbom-export\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},"01M7D487A4AZ6KK5CV214QG013","sbom-audit","Audit a dependency lockfile or SBOM for known vulnerabilities via mlab.sh, prioritize findings by KEV status and EPSS, and attribute actively exploited CVEs to threat actors. Use when the user provides a lockfile (package-lock.json, yarn.lock, pnpm-lock.yaml, Cargo.lock, requirements.txt, poetry.lock, uv.lock, Pipfile.lock, go.sum, composer.lock, Gemfile.lock, pom.xml, gradle.lockfile, packages.lock.json, pubspec.lock, mix.lock) or a CycloneDX \u002F SPDX SBOM, or asks to check dependencies for vulnerabilities.","https:\u002F\u002Fgithub.com\u002Fmlab-sh\u002Fmlab-claude\u002Fblob\u002Fmain\u002Fplugins\u002Fmlab\u002Fskills\u002Fsbom-audit\u002FSKILL.md",[],[]]