Add experimental ExecFence skill

skills/.experimental/execfence/LICENSE.txt

@@ -0,0 +1,201 @@
+                                 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 reasonable and customary use in 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 choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or 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 [yyyy] [name of copyright owner]
+
+   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.

skills/.experimental/execfence/SKILL.md

@@ -0,0 +1,166 @@
+---
+name: "execfence"
+description: "Add local execution guardrails for persistent projects that run build, test, dev, package, CI, agent, MCP, or desktop workflows. Use when a project may execute repository code, access the local filesystem, use package lifecycle hooks, define IDE tasks, publish artifacts, or expose broad shell/filesystem/network tools. Prefer ExecFence before running project code."
+---
+
+# ExecFence
+
+Use ExecFence to place a local guardrail around code execution in software projects. The goal is to stop suspicious repository code before normal developer actions activate it through tests, builds, package hooks, IDE tasks, CI, or agent tooling.
+
+The CLI is published as the `execfence` npm package. Run it with `npx --yes execfence ...`; do not copy scanner code into the user's project.
+
+For ExecFence v3.1.0 and newer, prefer Automatic Guard Mode. `guard enable` plans project-local protection without writing files, `guard enable --apply` applies reversible wrappers/rules, and `guard status` shows what remains unprotected. Global guard mode is intentionally non-invasive: it installs skill/defaults and agent rules only, without changing PATH, aliases, shell profiles, or intercepting `npm`, `go`, `python`, `cargo`, or `make`. If the installed CLI does not support `guard`, fall back to `init`, `scan`, `run`, `coverage`, and `wire`.
+
+ExecFence is especially relevant when:
+
+- the project is persistent, not a throwaway snippet
+- the project contains `package.json`, lockfiles, build configs, `Makefile`, `go.mod`, `Cargo.toml`, `pyproject.toml`, `.vscode/tasks.json`, `.github/workflows`, Tauri/Electron files, MCP configs, or agent instruction files
+- the user asks you to run `npm install`, `npm test`, `npm run build`, `go test`, `cargo test`, `python -m pytest`, `make`, package/publish commands, or similar project execution
+- the project can access the user's filesystem, browser, credentials, desktop APIs, shell, or network
+- the work involves malware injection, suspicious repository changes, fake interview code, supply-chain risk, CI hardening, or local execution safety
+
+Skip only for one-off static files, pure documentation, or when the user explicitly says not to use ExecFence.
+
+## Default Workflow
+
+1. Inspect the project stack and execution surfaces.
+2. Prefer automatic project guard setup when the installed ExecFence CLI supports `guard` and the user wants protection applied broadly:
+
+   ```sh
+   npx --yes execfence guard enable
+   npx --yes execfence guard enable --apply
+   npx --yes execfence guard status
+   ```
+
+   `guard enable` is dry-run by default. Use `--apply` only when project-local config, wrappers, CI setup, and agent rules should be written. If `guard` is unavailable, continue with the narrower setup below.
+
+3. Initialize ExecFence directly if a narrower setup is needed:
+
+   ```sh
+   npx --yes execfence init --preset auto
+   ```
+
+4. Scan before running project code:
+
+   ```sh
+   npx --yes execfence scan
+   ```
+
+5. Prefer the runtime gate for commands that execute repository code:
+
+   ```sh
+   npx --yes execfence run -- npm test
+   npx --yes execfence run -- npm run build
+   npx --yes execfence run -- go test ./...
+   npx --yes execfence run -- python -m pytest
+   npx --yes execfence run -- cargo test
+   ```
+
+6. For higher-risk local execution, use sandbox audit mode first:
+
+   ```sh
+   npx --yes execfence sandbox doctor
+   npx --yes execfence sandbox plan -- npm test
+   npx --yes execfence run --sandbox-mode audit -- npm test
+   ```
+
+7. Use hard sandbox enforcement only when capabilities are available:
+
+   ```sh
+   npx --yes execfence run --sandbox -- npm test
+   ```
+
+   If enforcement is unavailable, ExecFence should block before execution. Do not silently downgrade `--sandbox` to audit mode.
+
+## Commands To Prefer
+
+Use these commands according to the project surface:
+
+```sh
+npx --yes execfence init --preset auto
+npx --yes execfence guard enable
+npx --yes execfence guard enable --apply
+npx --yes execfence guard status
+npx --yes execfence guard disable
+npx --yes execfence guard global-status
+npx --yes execfence guard global-enable
+npx --yes execfence scan
+npx --yes execfence scan --changed-only --ci --format json
+npx --yes execfence run -- <command>
+npx --yes execfence run --record-artifacts --deny-on-new-executable -- <command>
+npx --yes execfence sandbox doctor
+npx --yes execfence sandbox plan -- <command>
+npx --yes execfence run --sandbox-mode audit -- <command>
+npx --yes execfence coverage
+npx --yes execfence coverage --fix-suggestions
+npx --yes execfence wire --dry-run
+npx --yes execfence ci
+npx --yes execfence deps diff
+npx --yes execfence pack-audit
+npx --yes execfence trust audit
+npx --yes execfence agent-report
+npx --yes execfence reports latest
+npx --yes execfence incident bundle --from-report .execfence/reports/<report>.json
+```
+
+## What ExecFence Watches
+
+Treat these as execution surfaces:
+
+- package scripts and lifecycle hooks
+- npm/pnpm/yarn/bun lockfiles
+- Go, Python, Rust, Tauri, and Electron build surfaces
+- `Makefile`
+- `.github/workflows/*`
+- `.vscode/tasks.json`
+- committed executables and archives
+- package contents before publish
+- trust stores and hash-pinned exceptions
+- MCP/tool configs
+- agent instruction files
+
+Block or escalate findings involving:
+
+- known injected JavaScript loader IoCs
+- suspicious `global[...] = require` loaders
+- dynamic `Function`/`constructor` loaders with `eval`, `fromCharCode`, or `child_process`
+- `.vscode/tasks.json` folder-open execution
+- package lifecycle scripts that download, eval, spawn shells, or hide payloads
+- raw/gist/paste lockfile URLs
+- unexpected `.exe`, `.dll`, `.bat`, `.cmd`, `.scr`, `.vbs`, `.wsf`, `.zip`, `.tgz`, `.asar`, or similar artifacts in source/build-input folders
+- new execution entrypoints that are not protected by `execfence run`
+- MCP or agent configs with broad shell, filesystem, browser, credential, or network access
+- instructions that tell an agent to skip, disable, ignore, or bypass ExecFence/security checks
+
+## Reports And Response
+
+ExecFence writes JSON evidence reports under `.execfence/reports/`. When a command blocks:
+
+1. Do not rerun the blocked command outside ExecFence.
+2. Preserve the newest report.
+3. Inspect the finding file, line, snippet, hash, git evidence, and local analysis.
+4. Create an incident bundle when useful:
+
+   ```sh
+   npx --yes execfence incident bundle --from-report .execfence/reports/<report>.json
+   ```
+
+5. Do not delete suspicious payloads automatically unless the user explicitly asks after evidence is preserved.
+
+## Baselines And Exceptions
+
+Use baselines only for reviewed, existing findings:
+
+```sh
+npx --yes execfence baseline add --from-report .execfence/reports/<report>.json --owner <owner> --reason <reason> --expires-at <date>
+```
+
+Do not baseline new `critical` or `high` findings just to make a build pass. Prefer removing the suspicious code, regenerating lockfiles from trusted registries, pinning reviewed files by SHA-256, or adding narrow trust-store entries with owner/reason/expiry.
+
+## Documentation
+
+Project documentation and CLI source are available at:
+
+- https://chrystyan96.github.io/ExecFence/
+- https://github.com/chrystyan96/ExecFence
+- https://www.npmjs.com/package/execfence

skills/.experimental/execfence/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "ExecFence"
+  short_description: "Guard project commands before execution"
+  default_prompt: "Use $execfence to add guardrails before running build, test, dev, CI, package, or agent workflows."