hook-safety-review skillA
hook-safety-review is agent-read markdown (skill) from yeaight7/agent-powerups: Use when a hook is about to be enabled or modified -- a hook recipe proposed for activation, a pre/post-tool or lifecycle hook added to agent settings, a git pre-commit hook added to a repo, or a third-party hook snippet pasted in from outside..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
## Purpose Review a hook definition before it is enabled so command injection, data exfiltration, and silent failure cannot ride in on automation. Hooks run automatically with the agent's privileges; a malicious or sloppy hook executes without any further review once it is on. ## When to Use - A hook recipe (safety, quality, productivity) is a candidate for activation - An agent settings file gains or changes a lifecycle hook entry - A git pre-commit or pre-push hook is added or edited - A hook snippet arrives from outside the repo Do not use for broad agent-config audits — that is the agent-config-security-audit skill. This skill is the enablement gate for one hook at a time. ## Inputs - The hook definition: command body, trigger event, matcher pattern - The settings or recipe file that declares it - What the hook can reach: environment variables, file paths, network ## Workflow 1. **Inventory the trigger surface.** Identify the event (pre-tool, post-tool, session start, commit), the matcher pattern, and how often it fires. A catch-all matcher on a high-frequency event deserves the strictest review. …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/hook-safety-review@git:20260606.29053cemdr add yeaight7/agent-powerups/hook-safety-review@sha256:395a4049fea11b53Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_o2t5ebysrbblc3fu)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.29053ce latest | 2026-06-06 | 29053ce | 3,703 B | A | view · diff |
| git:20260504.369cf14 | 2026-05-04 | 369cf14 | 71 B | B | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3703 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yeaight7/agent-powerups · 6 stars · license Apache-2.0 · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_o2t5ebysrbblc3fu GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/hook-safety-review GET https://markdownregistry.com/api/v1/blob/395a4049fea11b53e01e146304fb8fae3402588dc1b4203670b9e2e2ff372e48
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.