feat(plugin): split compliance-posture into 3 plugins (#256) - #264
Merged
Conversation
Closes #256. Per CEO direction, shipping three separate opt-in plugins instead of one bundled "compliance-posture" — keeps installs granular so a workspace that only wants CVE scanning doesn't carry OWASP policy or append-only audit retention. - plugins/molecule-compliance/ — wraps compliance.py (OWASP OA-01 prompt injection + OA-03 excessive agency). Skill: owasp-agentic. - plugins/molecule-audit/ — wraps audit.py (EU AI Act Art. 12/13/17 append-only JSONL log, SIEM-friendly). Skill: ai-act-audit-log. - plugins/molecule-security-scan/ — wraps security_scan.py (Snyk or pip-audit CVE gate on skill requirements.txt). Skill: skill-cve-gate. Each plugin ships a manifest + one SKILL.md with: - When to install / when to skip - Configuration shape (config.yaml blocks) - Anti-patterns to avoid - Cross-references to the other two plugins so an operator can reason about the full compliance surface All three wrap code that already exists in workspace-template/builtin_tools/ — no Python changes. Install per workspace via POST /workspaces/:id/plugins {"source":"builtin://molecule-<name>"}. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This was referenced Apr 15, 2026
Closed
molecule-ai Bot
pushed a commit
that referenced
this pull request
Apr 21, 2026
…re-split feat(plugin): split compliance-posture into 3 plugins (#256)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #256. Per CEO direction, shipping three separate opt-in plugins instead of one bundled `compliance-posture`.
Rationale
The three builtin_tools files that #256 proposed bundling aren't tightly coupled — `compliance.py` (OWASP runtime policy), `audit.py` (append-only log for EU AI Act), and `security_scan.py` (supply-chain CVE gate) each make sense independently. Bundling would force every workspace that wants, say, CVE scanning to also carry OWASP runtime checks and a JSONL audit file path. Granular installs keep the footprint honest.
What ships
Each plugin has:
Cross-plugin story
Install all three for a coherent compliance posture:
Install just one — e.g. only `molecule-audit` on a tenant that handles regulated data but trusts its agents — and the other two remain available for later.
No Python code
All implementation already exists in `workspace-template/builtin_tools/`. This PR is pure manifest + skill documentation. Same pattern as `molecule-hitl` (#262).
Test plan
Related
🤖 Generated with Claude Code