[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ESAWYBEEDD0X8C5A31FJS6":3,"skill-same:01M7ESAWYBEEDD0X8C5A31FJS6":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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7ESAWYBEEDD0X8C5A31FJS6","security-architecture",null,"Optional, opt-in STRIDE threat pass for a sensitive feature — invoked deliberately via \u002Fthreat-model, never forced on ordinary changes. Walks the change's attack surface and security boundaries (governed by ${CLAUDE_PROJECT_DIR}\u002F.codearbiter\u002Fsecurity-controls.md), surfaces threats and unmitigated gaps, and MAY dispatch security-reviewer or auth-crypto-reviewer. Not a routine gate; it can hard-STOP only on a genuinely critical unmitigated threat it surfaces.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fsecurity-architecture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: security-architecture\ndescription: Optional, opt-in STRIDE threat pass for a sensitive feature — invoked deliberately via \u002Fthreat-model, never forced on ordinary changes. Walks the change's attack surface and security boundaries (governed by ${CLAUDE_PROJECT_DIR}\u002F.codearbiter\u002Fsecurity-controls.md), surfaces threats and unmitigated gaps, and MAY dispatch security-reviewer or auth-crypto-reviewer. Not a routine gate; it can hard-STOP only on a genuinely critical unmitigated threat it surfaces.\n---\n\n# security-architecture\n\nOptional, lightweight threat-modeling pass over a design before it is built. Routed to only when the user deliberately invokes `\u002Fthreat-model \u003Cscope>` for a sensitive feature — never forced on an ordinary change. Reviews architectural intent before code exists; for code already written, dispatch `security-reviewer` instead.\n\n## Pre-flight\n\n- Read `${CLAUDE_PROJECT_DIR}\u002F.codearbiter\u002Fsecurity-controls.md` — approved primitives, declared security boundaries and their permitted crossings, what is and is not allowed. If it cannot be read, STOP and surface the gap; do not guess the boundary model.\n- Establish the scope from the user's `\u002Fthreat-model` argument: the feature, component, or design under review.\n\n## Phase 1 — Attack surface · gate: BLOCK\n\nMap what the change exposes. Name, for the scope:\n\n- New or changed entry points — routes, endpoints, message consumers, CLI surfaces.\n- New egress — outbound calls, external dependencies, new data sinks.\n- Security boundaries crossed, as declared in `security-controls.md` (trust transitions, privilege changes, data leaving a controlled zone).\n- The data handled and its sensitivity.\n\nA boundary crossing not described in `security-controls.md` is a finding, not a silent pass. A finding outside this scope gets one line with an inline `[NEEDS-TRIAGE]` marker.\n\nGate: the attack surface and every boundary crossing in scope are enumerated.\n\n## Phase 2 — STRIDE pass · gate: STOP\n\nWalk the surface from Phase 1 through STRIDE. For each relevant category, name the concrete threat and the control expected to mitigate it:\n\n- **Spoofing** — identity\u002Fauthentication of the actor at the boundary.\n- **Tampering** — integrity of data in transit and at rest.\n- **Repudiation** — whether actions are attributable.\n- **Information disclosure** — exposure of sensitive data, including in logs and errors.\n- **Denial of service** — exhaustion or availability impact.\n- **Elevation of privilege** — privilege gained across the boundary.\n\nMark each threat's mitigation `PRESENT`, `PLANNED`, or `GAP`. Skip a category only with a one-line reason it does not apply.\n\nIf the threat depends on auth, crypto, key handling, or secrets, MAY dispatch `${CLAUDE_PLUGIN_ROOT}\u002Fagents\u002Fauth-crypto-reviewer.md`. For broader boundary or surface concerns, MAY dispatch `${CLAUDE_PLUGIN_ROOT}\u002Fagents\u002Fsecurity-reviewer.md`. Both govern by `security-controls.md`.\n\nGate: STOP only on a genuinely critical unmitigated threat — a `GAP` that is exploitable now with high impact. Lesser gaps are surfaced as constraints, not stops.\n\n## Phase 3 — Report · gate: BLOCK\n\nProduce a terse report:\n\n- **Surface** — entry points, egress, boundaries crossed.\n- **Threats** — the STRIDE findings; lead with `GAP`s, then `PLANNED`, summarize `PRESENT` in one line.\n- **Verdict** — `PROCEED` (no open gap), `PROCEED-WITH-CONSTRAINTS` (gaps listed with owner), or `STOP` (a critical unmitigated threat is present; name it).\n\nA decision-worthy gap is escalated to the user or to `${CLAUDE_PROJECT_DIR}\u002F.codearbiter\u002Fdecisions\u002F` via `\u002Fadr` — never authored as an ADR by this skill.\n\nGate: report delivered with a stated verdict; every STOP-level threat from Phase 2 is reflected in it.\n\n## Hard rules\n\n- MUST NOT force this pass on an ordinary change. It is invoked deliberately for sensitive features only.\n- MUST NOT guess the boundary model — read `security-controls.md` or STOP.\n- MUST NOT silently pass an undeclared boundary crossing — surface it.\n- MUST NOT STOP on anything short of a critical, exploitable, unmitigated threat; lesser gaps are constraints.\n- MUST NOT author an ADR — escalate decision-worthy gaps to the user or `\u002Fadr`.\n","# security-architecture\n\nOptional, lightweight threat-modeling pass over a design before it is built. Routed to only when the user deliberately invokes `\u002Fthreat-model \u003Cscope>` for a sensitive feature — never forced on an ordinary change. Reviews architectural intent before code exists; for code already written, dispatch `security-reviewer` instead.\n\n## Pre-flight\n\n- Read `${CLAUDE_PROJECT_DIR}\u002F.codearbiter\u002Fsecurity-controls.md` — approved primitives, declared security boundaries and their permitted crossings, what is and is not allowed. If it cannot be read, STOP and surface the gap; do not guess the boundary model.\n- Establish the scope from the user's `\u002Fthreat-model` argument: the feature, component, or design under review.\n\n## Phase 1 — Attack surface · gate: BLOCK\n\nMap what the change exposes. Name, for the scope:\n\n- New or changed entry points — routes, endpoints, message consumers, CLI surfaces.\n- New egress — outbound calls, external dependencies, new data sinks.\n- Security boundaries crossed, as declared in `security-controls.md` (trust transitions, privilege changes, data leaving a controlled zone).\n- The data handled and its sensitivity.\n\nA boundary crossing not described in `security-controls.md` is a finding, not a silent pass. A finding outside this scope gets one line with an inline `[NEEDS-TRIAGE]` marker.\n\nGate: the attack surface and every boundary crossing in scope are enumerated.\n\n## Phase 2 — STRIDE pass · gate: STOP\n\nWalk the surface from Phase 1 through STRIDE. For each relevant category, name the concrete threat and the control expected to mitigate it:\n\n- **Spoofing** — identity\u002Fauthentication of the actor at the boundary.\n- **Tampering** — integrity of data in transit and at rest.\n- **Repudiation** — whether actions are attributable.\n- **Information disclosure** — exposure of sensitive data, including in logs and errors.\n- **Denial of service** — exhaustion or availability impact.\n- **Elevation of privilege** — privilege gained across the boundary.\n\nMark each threat's mitigation `PRESENT`, `PLANNED`, or `GAP`. Skip a category only with a one-line reason it does not apply.\n\nIf the threat depends on auth, crypto, key handling, or secrets, MAY dispatch `${CLAUDE_PLUGIN_ROOT}\u002Fagents\u002Fauth-crypto-reviewer.md`. For broader boundary or surface concerns, MAY dispatch `${CLAUDE_PLUGIN_ROOT}\u002Fagents\u002Fsecurity-reviewer.md`. Both govern by `security-controls.md`.\n\nGate: STOP only on a genuinely critical unmitigated threat — a `GAP` that is exploitable now with high impact. Lesser gaps are surfaced as constraints, not stops.\n\n## Phase 3 — Report · gate: BLOCK\n\nProduce a terse report:\n\n- **Surface** — entry points, egress, boundaries crossed.\n- **Threats** — the STRIDE findings; lead with `GAP`s, then `PLANNED`, summarize `PRESENT` in one line.\n- **Verdict** — `PROCEED` (no open gap), `PROCEED-WITH-CONSTRAINTS` (gaps listed with owner), or `STOP` (a critical unmitigated threat is present; name it).\n\nA decision-worthy gap is escalated to the user or to `${CLAUDE_PROJECT_DIR}\u002F.codearbiter\u002Fdecisions\u002F` via `\u002Fadr` — never authored as an ADR by this skill.\n\nGate: report delivered with a stated verdict; every STOP-level threat from Phase 2 is reflected in it.\n\n## Hard rules\n\n- MUST NOT force this pass on an ordinary change. It is invoked deliberately for sensitive features only.\n- MUST NOT guess the boundary model — read `security-controls.md` or STOP.\n- MUST NOT silently pass an undeclared boundary crossing — surface it.\n- MUST NOT STOP on anything short of a critical, exploitable, unmitigated threat; lesser gaps are constraints.\n- MUST NOT author an ADR — escalate decision-worthy gaps to the user or `\u002Fadr`.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fsecurity-architecture",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill security-architecture",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill security-architecture",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill security-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fsecurity-architecture\u002FSKILL.md",true,[],[47,55,60,67,74,81],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":54},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":56,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":54},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":54},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":54},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":54},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":54},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]