Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/ocentra/ocentra-enforcer/enforcernpx skills add ocentra/ocentra-enforcer --skill enforcergit clone --depth 1 https://github.com/ocentra/ocentra-enforcerWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ocentra/ocentra-enforcer/enforcer)<a href="https://agentmods.dev/skills/ocentra/ocentra-enforcer/enforcer"><img src="https://agentmods.dev/badge/skills/ocentra/ocentra-enforcer/enforcer.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00031 | $0.00569 |
| Opus 5 | $0.00015 | $0.00284 |
| Sonnet 5 | $0.00006 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
enforcer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enforcer
binary: single native `enforcer` executable
scopes: "paths | --base/--head | --all"
wired_cli: "check, scan, serve, ui, install, verify, advise, architecture, onboard"
reserved_cli: "plan, proof, coordination/ledger are visible but not wired"
wired_mcp: "mcp_status, coordination_status, coordination_claim, ui"
banned: "bypass comments, skipped tests, broad waivers, re-export shims, rule downgrades"
Use this skill for the native Rust implementation. Do not infer runtime support from registered command or MCP schemas; execute only the boundaries listed as wired above.
Workflow
- Confirm the exact binary with
enforcer --help. - Choose one explicit scope: paths, a
--base/--headdiff pair, or--all. - Run the smallest relevant
check,scan, orverifycommand. - Repair violations without suppressions or policy weakening.
- Run the repository's compiler, lint, and test commands directly when they
are required; native
runandrunscommands are not available. - Widen validation before reporting completion.
Current CLI
enforcer check path/to/file
enforcer scan --base origin/main --head HEAD
enforcer verify --mode local --all
enforcer architecture check --language rust --all
enforcer advise literals
enforcer install accepts no flags. It registers the absolute native binary
with all supported user-level harness adapters and runs an internal read-only
health check. Public doctor, init, update, and uninstall commands are
not exposed. plan, proof, and coordination (ledger) return not-wired
errors.
Current MCP
The Rust MCP router currently wires:
ocentra_enforcer_mcp_status
ocentra_enforcer_coordination_status
ocentra_enforcer_coordination_claim
ocentra_enforcer_ui
Routing, validation, diagnostics, proof, and broader coordination tools may appear in discovery but currently return a structured not-wired error. Use the native CLI for source validation.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 70 lines · 31 tokens per session scan A 02fdc648f609
enforcer is a skill published in the GitHub repository ocentra/ocentra-enforcer (0 stars, last pushed 9d ago), licensed MIT. It adds 31 tokens to every session and 569 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…