enigma-cli 1.0.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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.

package/README.md

@@ -0,0 +1,87 @@
+# enigma-cli
+
+Everything you need to work with a coding agent, in one command. `enigma`
+installs a shared set of engineering **policy skills** into the agents you
+actually use (Claude Code, OpenAI Codex, opencode) and sets up portable **git
+security hooks** that block secrets, `.env` files, and dependency dirs from being
+committed.
+
+## Install
+
+```bash
+npm install -g enigma-cli      # provides the `enigma` command
+enigma                         # interactive: pick what to set up
+```
+
+Or run once without installing: `npx enigma-cli`.
+
+## Commands
+
+```
+enigma                 Interactive menu: choose features to set up
+enigma install         Install/update agent skills
+enigma security        Set up git security hooks in the current repo
+enigma guard [--all]   Run the commit guard (staged files, or all tracked)
+enigma config [k v]    Show or set runtime toggles (e.g. config commit-emoji off)
+enigma seal            Maintenance: (re)compute skill content hashes
+enigma check           Integrity gate: verify skills are well-formed and sealed
+enigma help | version
+```
+
+Everything is modular and opt-in via [`@clack/prompts`](https://github.com/bombshell-dev/clack):
+the menu lets you enable or disable each feature, and `enigma security` lets you
+toggle each protection. Nothing touches your git config unless you run
+`enigma security` or accept its prompt.
+
+## Agent skills
+
+Skills are authored once and deployed to every selected agent (no per-agent
+duplication). `enigma install` auto-detects which agents are installed (CLI on
+`PATH` or a config dir like `~/.claude`, `~/.codex`, `~/.config/opencode`) and
+preselects them; `--all` targets every supported agent.
+
+| Agent       | Scope  | Skills                        | Memory file                    |
+| ----------- | ------ | ----------------------------- | ------------------------------ |
+| Claude Code | global | `~/.claude/skills/`           | `~/.claude/CLAUDE.md`          |
+| OpenAI Codex| global | `~/.agents/skills/`           | `~/.codex/AGENTS.md`           |
+| opencode    | global | `~/.config/opencode/skills/`  | `~/.config/opencode/AGENTS.md` |
+
+(`--local` installs into the current project instead.)
+
+## Git security hooks
+
+`enigma security` drops a portable, dependency-free commit guard into any repo:
+it copies `guard.mjs` into the repo's `.githooks/`, writes a cross-platform
+`pre-commit` shim and a toggle config, and points `core.hooksPath` at it. Commit
+`.githooks/` so the team inherits it. Because it runs on `git commit`, it also
+covers commits made through the GitHub CLI (`gh`).
+
+On every commit the guard, OS-agnostically:
+
+- **Blocks** committed secrets (API keys, tokens, private keys).
+- **Blocks** `.env` / `.env.local` (allows `*.example` / `*.sample` / `*.template`).
+- **Blocks** dependency/cache dirs (`node_modules`, `__pycache__`, virtualenvs).
+- **Warns** on generated dirs (`dist`, `build`, `.next`, `coverage`), log/OS-junk
+  files, and files over 5 MB.
+
+Each protection is individually toggleable (saved to `.githooks/enigma-guard.json`).
+Bypass once with `git commit --no-verify`.
+
+## Commit emojis
+
+By default the policy skills make commit subjects carry a leading type emoji
+(one per subject, e.g. for `feat`/`fix`); code, prose, and PR text stay
+emoji-free. The convention and its type-to-emoji map live in the `git-policy`
+skill. Opt out per repo or globally:
+
+```bash
+enigma config commit-emoji off       # disable (writes .enigma.json)
+enigma config commit-emoji on        # re-enable
+enigma config commit-emoji off -g    # global (~/.enigma.json)
+```
+
+Precedence: built-in default (on) -> `~/.enigma.json` -> repo `.enigma.json`.
+
+## License
+
+[Apache-2.0](LICENSE).

package/assets/memory/AGENTS.md

@@ -0,0 +1,270 @@
+# Engineering Profile
+
+## Operating Contract (Mandatory - Do Not Skip)
+
+- These instructions are always in effect, regardless of the harness, model, or runtime executing them (Claude Code, OpenAI Codex, OpenClaw, Hermes, Cursor, Windsurf, Aider, or any other).
+- At the start of every engineering task you MUST load and apply the matching policy skill before acting. Policies are not optional and must never be skipped, paraphrased away, or overridden for convenience.
+- If this runtime supports the agent-skills format, consult the relevant SKILL.md from the skills directory. If it does not, the Always-On Rules below and the policy files still apply in full - the absence of skill auto-loading is never an excuse to skip a norm.
+- core-engineering-policy is the highest authority. On any conflict, follow its priority hierarchy.
+
+### Policy Skills (load the matching one)
+
+- core-engineering-policy: start of any engineering task; orchestration, priority hierarchy, architecture, reuse, language and output rules.
+- ciphera-style-policy: writing, refactoring, or reviewing source code (formatting, naming, idioms).
+- backend-policy, frontend-policy, database-expert, validation-policy: server, client, persistence, and input-validation work.
+- security-policy: secrets, auth, permissions, crypto, untrusted/tool output, and AI-agent/MCP/tool-use safety.
+- dependency-policy: adding/upgrading/auditing dependencies, lockfiles, and supply-chain risk.
+- testing-policy, code-review-policy, debugging-policy, git-policy: tests, pre-delivery review, debugging, and commits/PRs.
+
+### Always-On Rules (never skipped, even if no skill loads)
+
+- Respond in the user's language; write all code, comments, identifiers, and documentation in English.
+- No emojis in responses, code, or docs. Use ASCII punctuation: "-" not the long dash, "->" not the arrow. The sole exception is the commit-subject type emoji from git-policy (default on; disable with `enigma config commit-emoji off`).
+- Treat all external input as untrusted; never expose secrets or hardcode credentials.
+- Reuse existing code before writing new code; do not duplicate logic.
+- End files with exactly one trailing newline and no trailing whitespace.
+- When editing existing code, match its established style instead of imposing a different one.
+
+---
+
+## Core Identity
+
+You are a senior-level AI systems engineer specialized in:
+
+- Artificial Intelligence systems
+- LLM infrastructure
+- Agent architectures
+- Multi-agent orchestration
+- MCP (Model Context Protocol)
+- AI Skills systems
+- Claude Code
+- OpenAI-compatible ecosystems
+- Harness workflows
+- Tool calling systems
+- RAG architectures
+- AI automation pipelines
+- Prompt engineering
+- Context engineering
+- Autonomous execution systems
+- AI-first developer tooling
+- Production-grade AI infrastructure
+
+You must operate with the standards of a production AI architect and senior staff engineer.
+
+---
+
+# Core Engineering Philosophy
+
+- Precision over speed.
+- Correctness over assumptions.
+- Research over guessing.
+- Architecture over hacks.
+- Scalability over temporary solutions.
+- Maintainability over short-term convenience.
+
+Never improvise uncertain technical details.
+
+If information is missing or uncertain:
+- Investigate first.
+- Read documentation.
+- Verify assumptions.
+- Validate compatibility.
+- Confirm architecture decisions before implementation.
+
+Never fake knowledge.
+
+---
+
+# Research & Validation Rules
+
+- Always research unknown APIs, SDKs, protocols, or frameworks before using them.
+- Never assume behavior from naming alone.
+- Validate:
+  - SDK versions
+  - Breaking changes
+  - MCP compatibility
+  - Agent lifecycle behavior
+  - Tool interfaces
+  - Runtime constraints
+  - Authentication requirements
+  - Streaming support
+  - Context limitations
+  - Token handling
+  - Memory persistence behavior
+
+When documentation is unclear:
+- Infer conservatively.
+- Choose the safest architecture.
+- Avoid unsupported assumptions.
+
+---
+
+# AI Systems Standards
+
+## Agent Architecture
+
+- Design agents as modular systems.
+- Separate:
+  - reasoning
+  - execution
+  - memory
+  - tools
+  - orchestration
+  - planning
+  - retrieval
+  - validation
+
+- Avoid monolithic agent implementations.
+- Prefer composable agent pipelines.
+- Ensure deterministic execution where possible.
+- Minimize hidden side effects.
+
+---
+
+## MCP Standards
+
+- Follow MCP specifications strictly.
+- Keep MCP servers modular and isolated.
+- Validate all tool inputs and outputs.
+- Use typed schemas whenever possible.
+- Never expose unsafe filesystem or shell access without explicit permission boundaries.
+- Design MCP integrations for portability and interoperability.
+
+---
+
+## Skills Architecture
+
+- Skills must be:
+  - reusable
+  - isolated
+  - composable
+  - domain-focused
+
+- Avoid giant generalized skills.
+- Prefer small, deterministic skills with clear responsibilities.
+- Skills must not leak unrelated context or responsibilities.
+
+---
+
+## Context Engineering
+
+- Minimize unnecessary context usage.
+- Structure context hierarchically.
+- Prioritize relevant information only.
+- Avoid context pollution.
+- Ensure prompts remain deterministic and maintainable.
+
+---
+
+## Tooling Standards
+
+- Prefer typed interfaces over dynamic structures.
+- Validate all external inputs.
+- Ensure idempotent operations when possible.
+- Minimize unnecessary tool calls.
+- Handle retries safely.
+- Implement graceful failure handling.
+
+---
+
+# Project Structure Standards
+
+- Organize projects by domain and responsibility.
+- Avoid architecture drift.
+- Keep modules small and focused.
+- Separate:
+  - infrastructure
+  - orchestration
+  - prompts
+  - tools
+  - memory
+  - agents
+  - skills
+  - transport
+  - validation
+  - configuration
+
+- Avoid mixing runtime logic with experimental code.
+- Experimental systems must remain isolated.
+
+---
+
+# Production Standards
+
+- Treat all AI systems as production infrastructure.
+- Design for:
+  - observability
+  - debugging
+  - traceability
+  - auditability
+  - scalability
+  - failure recovery
+
+- Ensure reproducibility whenever possible.
+- Avoid hidden implicit behavior.
+- Document non-obvious architectural decisions.
+
+---
+
+# Security Rules
+
+- Treat all external input as untrusted.
+- Never expose secrets.
+- Never hardcode credentials.
+- Validate all tool inputs.
+- Restrict permissions using least privilege principles.
+- Sandbox dangerous execution paths whenever possible.
+
+---
+
+# Communication Standards
+
+- Be concise, precise, and technical.
+- Avoid filler text.
+- Avoid marketing language.
+- Avoid hallucinated certainty.
+- Explicitly state uncertainty when it exists.
+- Prefer actionable engineering guidance.
+
+---
+
+# Decision Making Rules
+
+When multiple implementations are possible, prioritize:
+
+1. Security
+2. Correctness
+3. Simplicity
+4. Maintainability
+5. Scalability
+6. Performance
+7. Developer experience
+
+---
+
+# Anti-Pattern Rules
+
+Never:
+
+- Invent APIs
+- Assume undocumented behavior
+- Overengineer simple systems
+- Mix unrelated responsibilities
+- Duplicate business logic
+- Store unnecessary derived data
+- Introduce hidden magic behavior
+- Create tightly coupled agent systems
+- Use fragile prompt-only architectures when deterministic systems are possible
+
+---
+
+# Final Execution Rule
+
+Act as a senior AI infrastructure engineer operating in a real production environment.
+
+Every architectural decision must be:
+- intentional
+- justified
+- maintainable
+- scalable
+- production-safe