All Claude Code modsscaso01/claude-risk-guardrails
guardrails-monitoring
Ongoing monitoring: keep watching the agent after approval, and watch the controls themselves.
guardrails-monitoring reaches L2 (writes or runs) and passed claude plugin validate on Claude Code 2.1.302.
- Events hooked: 9
- API methods referenced: 11
- Access from classified calls: L2, writes or runs: runs processes, writes files, drives Claude, reads files, reads env vars, draws
- Static scan, not a runtime test
Install hint
/plugin install guardrails-monitoring --marketplace scaso01/claude-risk-guardrailsFrom 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, writes files, drives Claude, reads files, reads env vars, drawsValidation
Passed on Claude Code 2.1.302View the source on GitHub Back to the list
What the scan recorded
- Observed events
- classic hooks, Agent calls, every prompt, Edit|Write calls
- Hooks
classic.SubagentStart, classic.SubagentStop, classic.SessionStart, classic.UserPromptSubmit, tool.call {tool=Agent}, prompt.submit, command.run {command=full-reply}, turn.step, tool.call {tool=Edit|Write}, session.start, command.run {command=guardrails-status}- API calls
$.clock.now, $.command.register, $.env.get, $.fs.exists, $.fs.list, $.fs.read, $.fs.write, $.model.complete, $.process.run, $.session.surfaces, $.ui.status- Validation on 2.1.302
- Passed
- Scanned revision
5827ad293ec2- Marketplace warnings
- claude-risk-guardrails
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. How the scan works.
More from scaso01/claude-risk-guardrails
- guardrails-approvalA human signs off before anything that can't be undone: publishing, killing protected processes, editing secr…
- guardrails-challengeEffective challenge: hold answers to evidence under pushback, and check agents' commit claims against git.
- guardrails-developmentDevelopment standards: look before building, test what changed, pass the repo's checks, keep the rules in vie…
- guardrails-outcomesOutcomes analysis: check what a reply claims against what the evidence supports.
- guardrails-recordsDocumentation: leave a trail a reviewer can follow, and keep what can't be rebuilt.
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/scaso01--claude-risk-guardrails--guardrails-monitoring/)
[](https://mods.aidojo.si/mods/scaso01--claude-risk-guardrails--guardrails-monitoring/)