How do I install the Harden skill?

Run npx skillmds@latest add amineorion/harden in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Harden safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Harden?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Harden free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Harden?

amineorion (@amineorion) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Harden by amineorion — Agent Skill

Name: Harden
Author: amineorion

Harden

Install the always-on safety hooks (destructive-command-guard + tenant-scope-guard) into this project. Use when setting up a multi-tenant or production codebase for agent-authored changes, or when the user asks to "harden", "add safety hooks", or "guard prod".

amineorion 5196b2b 4 files · 8.8 KB Updated Sep 17, 2026

File contents

Harden this project

Install the two deterministic guards that block irreversible damage. These run as hooks, not skills, because they must fire on every action regardless of what is loaded. A prompt is a request; a hook is a control.

Steps

Run the installer to copy the hook scripts into .claude/hooks/:
```
bash ${CLAUDE_SKILL_DIR}/scripts/install.sh
```
Merge the printed snippet into .claude/settings.json under "hooks". If a hooks block already exists, merge the arrays — do not overwrite.
Tell the user what got wired, and remind them to tune the blocklists:
- destructive-command-guard.sh — review the SQL and prod-host patterns for their stack.
- tenant-scope-guard.sh — set TENANT_COL if their tenant column isn't one of tenant_id|org_id|account_id|workspace_id.

What each guard does

destructive-command-guard (PreToolUse/Bash): refuses DROP/TRUNCATE, DELETE/UPDATE without WHERE, commands aimed at a production host, force-push to protected branches, rm -rf on absolute paths, curl | sh, and sudo.
tenant-scope-guard (PostToolUse/Edit): warns when a freshly edited data-access line has no visible tenant filter — the missed WHERE tenant_id that becomes a leak.

Over-blocking is worse than under-blocking: if a guard is too aggressive the agent learns to route around it. Keep the lists short and high-signal.

Frequently asked questions