@blamejs/exceptd-skills 0.9.1

package/CONTEXT.md

@@ -0,0 +1,203 @@
+# exceptd Security — AI Context
+
+This file gives any AI assistant the context it needs to use this skill repository effectively. It is AI-system-agnostic and does not assume any particular assistant runtime.
+
+---
+
+## What This Repository Is
+
+exceptd Security is a library of AI security skills grounded in mid-2026 threat reality. Each skill is a structured instruction file that tells an AI assistant how to perform a specific security analysis — what questions to ask, what data to query, how to score risk, and what output to produce.
+
+**The core insight:** Every major compliance framework (NIST 800-53, ISO 27001, SOC 2, PCI-DSS) was written for environments that no longer describe how attacks happen. These skills explicitly map where framework coverage ends and real attacker capability begins.
+
+---
+
+## How Skills Work
+
+Each skill is a Markdown file at `skills/<name>/skill.md` with a YAML frontmatter header and a structured body.
+
+### Frontmatter Fields
+
+```yaml
+name: skill-name          # Unique identifier
+version: "1.0.0"          # Semantic version
+description: "..."        # One-line description for skill matching
+triggers:                 # Phrases that invoke this skill
+  - kernel lpe
+  - privilege escalation
+data_deps:                # Data files this skill reads
+  - cve-catalog.json
+atlas_refs:               # MITRE ATLAS TTP IDs referenced
+  - AML.T0051
+attack_refs:              # MITRE ATT&CK TTP IDs referenced
+  - T1068
+framework_gaps:           # Framework controls this skill exposes as insufficient
+  - NIST-800-53-SI-2
+forward_watch:            # Upcoming changes to watch for skill updates
+  - FIPS 206 finalization
+last_threat_review:       # Date of last threat currency review
+  "2026-05-01"
+```
+
+### Skill Body Structure
+
+Every skill has these sections:
+
+1. **Threat Context** — Current exploitation reality, not theoretical risk
+2. **Framework Lag Declaration** — Per-framework gap statements with specific control IDs
+3. **TTP Mapping** — ATLAS/ATT&CK IDs with framework coverage gap flags
+4. **Exploit Availability Matrix** — PoC status, KEV listing, AI-acceleration factor
+5. **Analysis Procedure** — Step-by-step instructions for performing the analysis
+6. **Output Format** — Exact structure the analysis should produce
+7. **Compliance Theater Check** — Specific test distinguishing paper compliance from real posture
+
+---
+
+## Data Files
+
+Skills read from `data/`. These are the authoritative data sources:
+
+| File | Purpose |
+|------|---------|
+| `cve-catalog.json` | 5 CVEs with CVSS, RWEP score, EPSS estimates, CISA KEV flags, PoC and live-patch availability |
+| `atlas-ttps.json` | MITRE ATLAS v5.1.0 (November 2025) techniques and mappings with framework gap flags |
+| `framework-control-gaps.json` | 49 framework control gap entries: designed-for vs. what each control misses |
+| `exploit-availability.json` | Per-CVE PoC locations, weaponization stage, AI-acceleration factor, live-patch status |
+| `global-frameworks.json` | 22+ jurisdictions (expanding to 29+) — framework registry with patch SLAs and notification windows |
+| `zeroday-lessons.json` | Learning-loop entries: zero-day → attack vector → control gap → framework gap → new control requirement |
+| `cwe-catalog.json` | 30 CWE entries pinned to CWE v4.17 (Top 25 2024 plus AI- and supply-chain-relevant weaknesses) for root-cause classification |
+| `d3fend-catalog.json` | 21 MITRE D3FEND defensive techniques pinned to D3FEND v1.0.0; used to map offensive findings to specific defensive countermeasures |
+| `rfc-references.json` | 19 IETF RFC / Internet-Draft references with status, errata count, replaces / replaced-by, and `last_verified` dates |
+| `dlp-controls.json` | 21 DLP control entries indexed by channel, classifier, surface, enforcement mode, and evidence type for DLP-relevant skills |
+
+---
+
+## Invoking Skills
+
+To use a skill, match its trigger phrases and follow its Analysis Procedure. Example invocations:
+
+```
+kernel-lpe-triage           — Assess Linux kernel LPE exposure
+ai-attack-surface           — AI/ML attack surface assessment
+framework-gap-analysis      — Feed a control ID + threat → get the gap
+compliance-theater          — Detect where audit compliance ≠ real security
+global-grc NIS2             — Map a threat to NIS2 + companion jurisdictions
+exploit-scoring CVE-2026-31431  — RWEP score with full factor breakdown
+security-maturity-tiers     — MVP / Practical / Overkill roadmap for any domain
+zeroday-gap-learn CVE-...   — Run the zero-day learning loop on a new CVE
+pqc-first                   — Post-quantum cryptography readiness assessment
+```
+
+---
+
+## Risk Scoring: RWEP
+
+The repository uses Real-World Exploit Priority (RWEP) scoring, not CVSS alone. CVSS is reported alongside RWEP but never as the sole score.
+
+RWEP formula (0–100):
+```
+base = cisa_kev(+25) + poc_public(+20) + ai_factor(+15)
+     + active_exploitation(+20) + blast_radius(0-30)
+     - patch_available(-15) - live_patch(-10) + reboot_required(+5)
+
+ai_factor = ai_discovered OR ai_assisted_weaponization
+blast_radius = 0-30 scale (30 = all-Linux or 150M+ installations)
+reboot_required = +5 always when patch requires reboot
+```
+
+Example: CVE-2026-31431 (Copy Fail) — CVSS 7.8 / **RWEP 90**
+- CVSS 7.8 suggests "high, patch within 30 days"
+- RWEP 90 means: deterministic root in < 1 second, CISA KEV, 732-byte public PoC, AI-discovered, blast radius = all Linux >= 4.14 — 30 days is exploitation acceptance
+
+The RWEP scoring engine is at `lib/scoring.js`.
+
+---
+
+## Compliance Theater
+
+This repository uses the term "compliance theater" for a specific, measurable condition: an organization that passes an audit of a security control while remaining exposed to the threat that control is supposed to address.
+
+Seven documented patterns:
+1. **Patch Management Theater** — meets framework SLA, still exposed to active exploitation
+2. **AI Access Control Theater** — service account is compliant; prompt injection bypasses it entirely
+3. **Vendor Management Theater** — vendor controls pass audit; AI tool plugins (MCP servers) are out of scope
+4. **Malware Protection Theater** — signatures are current; AI-generated novel code evades all signatures
+5. **Supply Chain Theater** — software supply chain passes review; developer-installed AI plugins are excluded
+6. **Encryption Theater** — classical encryption is compliant; HNDL exposure is unaddressed
+7. **Detection Theater** — monitoring is compliant; AI C2 channels and AI-querying malware are not detected
+
+Run `lib/framework-gap.js` → `theaterCheck()` to detect these patterns programmatically.
+
+---
+
+## Orchestration Layer
+
+The `orchestrator/` directory provides:
+- **Scanner** — discovers kernel versions, MCP configs, crypto posture, framework claims
+- **Dispatcher** — routes scanner findings to relevant skills via manifest triggers
+- **Pipeline** — coordinates `threat-researcher` → `source-validator` → `skill-updater` → `report-generator`
+- **Event bus** — triggers skill updates on CISA KEV additions, ATLAS releases, framework amendments
+- **Scheduler** — runs weekly currency checks and annual full audits
+
+Entry point: `node orchestrator/index.js`
+
+### Agents vs. Skills
+
+The four orchestration components above (`threat-researcher`, `source-validator`, `skill-updater`, `report-generator`) are **agent definitions** living under `agents/`. They are pipeline workers that run inside the orchestrator — not user-invokable skills.
+
+Skills live under `skills/<name>/skill.md` and are matched by trigger phrases. The `researcher` **skill** (separate from the `threat-researcher` **agent**) is the user-facing entry-point dispatcher: when an operator drops in raw threat intel without knowing which specialized skill to call, the `researcher` skill cross-joins the data catalogs, produces an RWEP-anchored dispatch report, and routes to the right specialized skill(s).
+
+Naming convention to keep straight:
+- `agents/threat-researcher/` — orchestrator pipeline worker (autonomous, background)
+- `skills/researcher/skill.md` — user-invoked triage dispatcher (interactive, front door)
+
+They share a thematic name but are different artifacts with different runtimes.
+
+---
+
+## AI System Integration Notes
+
+### How to Load Skills
+
+1. Read `manifest.json` to get the full skill registry
+2. Match user intent against `triggers` arrays
+3. Load the matched `skill.md` into context
+4. Follow the skill's **Analysis Procedure** step by step
+5. Pull data from the referenced `data_deps` files as needed
+6. Produce output matching the skill's **Output Format**
+
+### Context Budget Guidance
+
+- `manifest.json` — load first, always (small, high-value index)
+- `data/cve-catalog.json` — load on demand for any CVE-specific analysis
+- `data/framework-control-gaps.json` — load for gap analysis and theater detection
+- `data/global-frameworks.json` — load for multi-jurisdiction questions
+- `data/atlas-ttps.json` — load for AI attack surface and C2 detection work
+- Individual skill files — 15–40KB each; load on match, not preemptively
+
+### What This Repo Does Not Contain
+
+- No code that executes automatically in your environment
+- No network calls — all data is local and static
+- No credentials or keys
+- Skills are instruction text — the AI implements them, not the files themselves
+
+---
+
+## Key Concepts Quick Reference
+
+| Term | Definition |
+|------|------------|
+| RWEP | Real-World Exploit Priority — risk score beyond CVSS |
+| KEV | CISA Known Exploited Vulnerabilities catalog |
+| ATLAS | MITRE ATLAS v5.1.0 — AI threat framework |
+| MCP | Model Context Protocol — AI tool integration standard |
+| HNDL | Harvest-Now-Decrypt-Later — quantum threat to current crypto |
+| Framework lag | The gap between what a framework requires and what current TTPs demand |
+| Theater | Audit-passing compliance that doesn't close the real attack path |
+| RWEP 90+ | Priority 1: live-patch or isolate same-day |
+| Copy Fail | CVE-2026-31431 — RWEP 90, CISA KEV, 732-byte deterministic root |
+| Dirty Frag | CVE-2026-43284/43500 — IPsec subsystem LPE chain |
+| SesameOp | AI API as covert C2 channel (ATLAS AML.T0096) |
+| PROMPTFLUX | Malware querying LLMs for real-time AV evasion code |
+| PROMPTSTEAL | Malware querying LLMs for target intelligence |

package/LICENSE

@@ -0,0 +1,200 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for describing the origin of the Work and
+      reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may accept and charge a
+      fee for, or grant rights consistent with, this License. However,
+      in accepting such obligations, You may act only on Your own behalf
+      and on Your sole responsibility, not on behalf of any other
+      Contributor, and only if You agree to indemnify, defend, and hold
+      each Contributor harmless for any liability incurred by, or claims
+      asserted against, such Contributor by reason of your accepting any
+      such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Robert Lee
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,82 @@
+exceptd-skills
+Copyright 2026 blamejs contributors
+
+This product includes software developed by the exceptd Security project
+(https://exceptd.com), part of the blamejs organization.
+
+Licensed under the Apache License, Version 2.0. See LICENSE for the full text.
+
+================================================================================
+Third-Party Data Sources
+================================================================================
+
+exceptd-skills has zero npm runtime dependencies and depends on Node.js stdlib
+only. The repository does include one vendored code subset, attributed below.
+
+--------------------------------------------------------------------------------
+Vendored:    blamejs (subset)
+URL:         https://github.com/blamejs/blamejs
+Pinned at:   commit 1442f17758a4bd511c63877561c0ffa759f66a87 (0.9.0 fix-up)
+License:     Apache-2.0 (compatible — exceptd is Apache-2.0). Full text at
+             vendor/blamejs/LICENSE.
+Vendored:    vendor/blamejs/retry.js, vendor/blamejs/worker-pool.js
+Used for:    Battle-tested exponential-backoff retry + circuit breaker
+             (used by lib/job-queue.js for upstream-fetch retry semantics)
+             and worker_threads pool (used by scripts/build-indexes.js
+             --parallel and any future CPU-bound fan-out).
+Notice:      Flattened-and-stripped to leaf files with no transitive blamejs
+             imports. Strip rules + provenance hashes are recorded in
+             vendor/blamejs/_PROVENANCE.json and verified on every predeploy
+             via lib/validate-vendor.js. The vendored copy is © blamejs
+             contributors under the Apache-2.0 grant; see vendor/blamejs/README.md
+             for re-vendor instructions and the list of upstream files NOT
+             vendored (and why).
+--------------------------------------------------------------------------------
+
+The threat-intelligence data the skills are grounded in is sourced from the
+following public catalogs. Each source retains its own copyright and licensing;
+exceptd-skills references their identifiers (CVE IDs, ATLAS TTP IDs, framework
+control IDs) under fair-use research conventions, but does not redistribute
+their content verbatim.
+
+--------------------------------------------------------------------------------
+Source:      MITRE ATLAS
+URL:         https://atlas.mitre.org
+Version:     v5.1.0 (November 2025)
+Used for:    Adversarial Threat Landscape for AI Systems — TTP IDs cited in
+             skills/*, data/atlas-ttps.json, and manifest.json. Pinned per
+             CLAUDE.md hard rule #12.
+Notice:      ATLAS is © The MITRE Corporation, released under the terms at
+             https://atlas.mitre.org/resources/terms-of-use.
+--------------------------------------------------------------------------------
+Source:      MITRE ATT&CK
+URL:         https://attack.mitre.org
+Used for:    Enterprise technique IDs (T-numbers) cited in skill TTP mappings.
+Notice:      ATT&CK is © The MITRE Corporation; redistribution terms at
+             https://attack.mitre.org/resources/terms-of-use/.
+--------------------------------------------------------------------------------
+Source:      NIST National Vulnerability Database (NVD)
+URL:         https://nvd.nist.gov
+Used for:    CVE metadata (CVSS scores, vectors, descriptions) cited in
+             data/cve-catalog.json and cross-checked by
+             sources/validators/cve-validator.js.
+Notice:      U.S. Government work; not subject to copyright. Use must comply
+             with NVD's terms-of-use including rate-limiting guidance.
+--------------------------------------------------------------------------------
+Source:      CISA Known Exploited Vulnerabilities (KEV) Catalog
+URL:         https://www.cisa.gov/known-exploited-vulnerabilities-catalog
+Used for:    KEV status flags driving the RWEP scoring formula in lib/scoring.js.
+Notice:      U.S. Government work; CISA publishes the catalog for free public use.
+--------------------------------------------------------------------------------
+Source:      Compliance frameworks (NIST 800-53, ISO/IEC 27001:2022, SOC 2, PCI
+             DSS, NIS2, DORA, EU AI Act, EU CRA, ASD Essential 8, MAS TRM,
+             CERT-In Directions, and the others enumerated in
+             data/global-frameworks.json)
+Used for:    Control IDs cited in framework_gaps fields and in skill body
+             "Framework Lag Declaration" sections. exceptd-skills does NOT
+             redistribute framework text; it only cites identifiers and
+             explains where current TTPs bypass the cited controls.
+Notice:      Each framework retains the licensing terms of its publisher.
+             Refer to the source listed in data/global-frameworks.json for
+             redistribution constraints.
+--------------------------------------------------------------------------------