Hookify Rules
Add pattern guardrails to Muse with hookify rules: markdown files with YAML frontmatter that warn or block on bash, file, prompt, or stop events, matched by regex or conditions.
- What
- Add pattern guardrails to Muse with hookify rules: markdown files with YAML frontmatter that warn or block on bash, file, prompt, or stop events, matched by regex or conditions.
- Cost
- Free
- Needs
- Use "Hookify Rules" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a guide to writing hookify rules, the pattern guardrails that make Muse warn or block itself at exactly the right moment. A rule is a markdown file with YAML frontmatter stored as .claude/hookify.<name>.local.md: name in verb-first kebab-case (warn-*, block-*, require-*), enabled toggle, event type (bash, file, prompt, stop, or all), action warn or block, and a regex pattern or multi-condition set. The guide walks through the frontmatter fields, then the event guide with concrete matches: dangerous bash patterns like rm -rf, dd if=, sudo, and chmod 777; file events for console.log and debugger leftovers, eval and innerHTML risks, and sensitive .env, credentials, and .pem files; stop events for completion checks; prompt events for workflow enforcement. Pattern writing tips cover regex escaping, the classic pitfalls of too-broad (log matches login) versus too-specific patterns, and YAML escaping, with a python3 one-liner to test patterns before deploying them. It also documents the /hookify slash commands to create, list, configure, and get help, plus file organization and the gitignore recommendation for local rules. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: this is guidance for writing rules, not the hookify runtime itself; over-blocking slows Muse down, start with warn and graduate to block. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Hookify Rules" with your Muse. Prerequisites: none to install. Pure guidance; a .claude/ directory in your project helps. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/hookify-rules/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Write a hookify rule that [describe what to guard, e.g. blocks rm -rf commands / warns when API keys are added to .env]." 3. Review the generated rule file, place it in .claude/hookify.<name>.local.md, and test the pattern with the python3 one-liner from the guide. Tip: start with action warn on new rules, graduate to block only once you trust the pattern. Safety: a skill is plain-text instructions; it runs nothing by itself. Review generated commands before running them.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.