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.
/plugin marketplace add athola/claude-night-marketnpx agentmods add plugins/athola/claude-night-market/hookifygit clone --depth 1 https://github.com/athola/claude-night-marketWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/plugins/athola/claude-night-market/hookify)<a href="https://agentmods.dev/plugins/athola/claude-night-market/hookify"><img src="https://agentmods.dev/badge/plugins/athola/claude-night-market/hookify.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
hookify scanned grade A with 0 findings 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 today.
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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"name": "hookify",
"version": "1.9.19",
"description": "Create custom behavioral rules through markdown configuration files - prevent unwanted behaviors with pattern matching",
"commands": [
"./commands/configure.md",
"./commands/from-hook.md",
"./commands/help.md",
"./commands/hookify.md",
"./commands/install.md",
"./commands/list.md"
],
"skills": [
"./skills/writing-rules",
"./skills/rule-catalog"
],
"agents": [],
"keywords": [
"hooks",
"rules",
"safety",
"validation",
"patterns",
"behavioral-constraints",
"governance"
],
"author": {
"name": "Alex Thola",
"url": "https://github.com/athola"
},
"license": "MIT"
}
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.
- today First seen · 33 lines scan A c8f48d1ab044
hookify is a plugin published in the GitHub repository athola/claude-night-market (335 stars, last pushed today), 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 A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other plugins, from other repositories
sound
Code taste as installable rules. Probe a repo's stack, select only the rules its code shows a surface for (evidence-cited per rule), confirm, and scaffold a browsable .claude/sound/ rule map (surfaced by the sound:prime skill). Installed rules are user-owned; re-runs reconcile.
brand-guardian
Use this agent when establishing brand guidelines, ensuring visual consistency, managing brand assets, or evolving brand identity. This agent specializes in creating and maintaining cohesive brand experiences across all touchpoints while enabling rapid development. Examples:\n\n \nContext: Creating brand guidel.
specweaver
Comprehensive feature development workflow with spec-driven implementation, atomic phasing, and multi-agent collaboration.
claude-hook-advisor
Intelligent command history tracking with automatic failure detection. Tracks all bash commands Claude runs (successful and failed) with semantic directory aliasing and command mapping.
code-architect
Use this agent when you need to design scalable architecture and folder structures for new features or projects. Examples include: when starting a new feature module, refactoring existing code organization, planning microservice boundaries, designing component hierarchies, or establishing project structure conventions.
debug-session
Ask Claude Code to help you debug an issue.