ocentra/ocentra-enforcer

Standalone enforcement system for indexed rules, validators, Codex skills, MCP, hooks, and CI adapters.

This repository also configures its own agents. See what ocentra-enforcer tells them →

0Stars on the repository
8Mods indexed here, across every type
1mo agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

ocentra-enforcer

01

ocentra/ocentra-enforcer

Skill Claude CodeCodex needs its repo

Compatibility workflow for the frozen Node-based Ocentra Enforcer service. Do not use its commands as the native Rust CLI contract.

not rated 0 changed 1mo ago A 31 tokens original MIT

enforcer-onboarding

02

ocentra/ocentra-enforcer

Skill Claude CodeCodex

Onboard a project onto the current native Rust Enforcer without assuming unreleased installer, MCP, proof, or CI capabilities.

not rated 0 1mo ago A 30 tokens original MIT

enforcer

03

ocentra/ocentra-enforcer

Skill Claude CodeCodex

Use the current native Rust Enforcer CLI for focused repository validation and its presently wired MCP status, coordination-status/claim, or UI tools.

not rated 0 1mo ago A 31 tokens original MIT

plan

04

ocentra/ocentra-enforcer

Skill Claude CodeCodex

Author, scaffold, and self-validate Ocentra-methodology workpack plans. Use when creating a new docs/plans/ / directory, authoring or auditing workpack documents, running the PLAN- structure validators against a plan, or wiring the /plan harness command.

not rated 0 1mo ago A 58 tokens original MIT

security-testing

06

ocentra/ocentra-enforcer

Skill Claude CodeCodex

Money-critical & security-testing mandate walkthrough — route, classify, threat-map, invariants, mechanics, and CI tooling for any system handling money/payments/value behind untrusted infrastructure. Use when a change touches value transfer, signing, time-based state, rollback/compensation, or kill switches.

not rated 0 1mo ago A 62 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: