safety-hooks

Pre-use safety checks for agent actions. They can block dangerous shell commands, secret leaks, edits to protected files and writes to build artifacts.

In plain words
What is it for?
Use them as guardrails before file edits, file writes and shell commands.
Why use it?
They reduce the chance that an automated action will delete data, expose credentials or change files that should remain untouched.

Plugin for Claude Code

Install

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.

Claude Code
/plugin marketplace add poshan0126/dotclaude
agentmods
npx agentmods add plugins/poshan0126/dotclaude/safety-hooks
Clone the repo
git clone --depth 1 https://github.com/poshan0126/dotclaude

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade C, and why

safety-hooks scanned grade C with 1 finding 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 3d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

"description": "Deterministic guardrails as PreToolUse hooks: blocks dangerous commands (force push, rm -rf, DROP TABLE), secret leaks, edits to protected files, and writes to build artifacts.",
plugins/safety-hooks/.claude-plugin/plugin.json · 19 lines

What it actually says

{
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
  "name": "safety-hooks",
  "version": "2.0.0",
  "description": "Deterministic guardrails as PreToolUse hooks: blocks dangerous commands (force push, rm -rf, DROP TABLE), secret leaks, edits to protected files, and writes to build artifacts.",
  "author": {
    "name": "poshan0126"
  },
  "license": "MIT",
  "homepage": "https://github.com/poshan0126/dotclaude",
  "repository": "https://github.com/poshan0126/dotclaude",
  "keywords": [
    "hooks",
    "safety",
    "secrets",
    "guardrails"
  ]
}
Changes

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.

  1. 3d ago First seen · 19 lines scan C 836652701c48

Subscribe to this mod's changes

safety-hooks is a plugin published in the GitHub repository poshan0126/dotclaude (860 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.