All Claude Code modslnodonly/claude-mods
rules-enforcer
Enforces a project's .claude/rules.json: required skills before edits, and doc updates in the same turn
rules-enforcer reaches L2 (writes or runs) and passed claude plugin validate on Claude Code 2.1.303.
- Events hooked: 9
- API methods referenced: 17
- Access from classified calls: L2, writes or runs: runs processes, drives Claude, reads files, reads env vars, reads mod state, persists state, draws
- Reads mod state: the scan does not record whose state, so this does not show that it reads another mod’s values
- Static scan, not a runtime test
Install hint
/plugin install rules-enforcer --marketplace lnodonly/claude-modsFrom the repository's own marketplace. Confirm the plugin name in the repository's README before installing. Mods need Claude Code 2.1.287 or later.
Access
L2 Writes or runsruns processes, drives Claude, reads files, reads env vars, reads mod state, persists state, drawsValidation
Passed on Claude Code 2.1.303View the source on GitHub Back to the list
What the scan recorded
- Observed events
- Edit calls, Write calls, NotebookEdit calls, Bash calls, Monitor calls, Skill calls, every skill, classic hooks, mcp__rules-enforcer__waive_doc_update calls
- Hooks
tool.call {tool=Edit}, tool.call {tool=Write}, tool.call {tool=NotebookEdit}, tool.call {tool=Bash}, tool.call {tool=Monitor}, tool.call {tool=Skill}, skill.prompt, classic.SessionEnd, classic.PostCompact, session.start, tool.call {tool=mcp__rules-enforcer__waive_doc_update}, classic.UserPromptSubmit, classic.Stop, classic.SubagentStop, command.run {command=rules}- API calls
$.clock.now, $.command.register, $.env.get, $.fs.exists, $.fs.list, $.fs.read, $.fs.stat, $.process.run, $.session.cwd, $.state.get, $.state.set, $.store.get, $.store.set, $.tool.register, $.ui.notice, $.ui.status, $.ui.toast- Validation on 2.1.303
- Passed
- Scanned revision
22069a725a4c- Marketplace passed
- claude-mods
These are the hooks and API calls reported by claude plugin validate. Access levels describe the widest reach of those calls and are not safety ratings. Validation is a static check, not a runtime test, and a passing result does not prove that a mod works or is safe. What a mod can access and how the scan works.
More from lnodonly/claude-mods
- context-barShows the context window as a stacked bar (with its percentage) and a legend, drawn by modbar; hide or show w…
- context-dietRemoves escape codes, progress redraws and identical-line runs from Bash output (lossless), and lists the big…
- handoffA note per project folder for the next session: /handoff writes a full one, and with /handoff auto on exit sa…
- modbarDraws the area above the prompt for other mods: their blocks, packed into configurable rows
Badge for your README
Authors can show the latest scan result in their README. Each badge links to this page.
[](https://mods.aidojo.si/mods/lnodonly--claude-mods--rules-enforcer/)
[](https://mods.aidojo.si/mods/lnodonly--claude-mods--rules-enforcer/)