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.
git 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/commands/athola/claude-night-market/help)<a href="https://agentmods.dev/commands/athola/claude-night-market/help"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/help/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/athola/claude-night-market/help"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/help.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00006 | $0.00398 |
| Opus 5 | $0.00003 | $0.00199 |
| Sonnet 5 | $0.00001 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
help 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 5d 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.
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
Hookify Help
Overview
Hookify enables creation of custom behavioral rules through markdown configuration files. Prevent unwanted behaviors with pattern matching - no complex JSON or coding required.
Quick Start
-
Create a rule:
/hookify Don't use console.log in files -
View your rules:
/hookify:list -
Manage rules:
/hookify:configure
Commands
/hookify [instruction]- Create rule or analyze conversation/hookify:list- Show all rules/hookify:configure- Enable/disable rules interactively/hookify:help- This help message
Rule Files
Rules are stored in .claude/hookify.{name}.local.md
Example Rule
---
name: dangerous-rm
enabled: true
event: bash
pattern: rm\s+-rf
action: block
---
🛑 **Dangerous rm command!**
This could delete files.
Event Types
- bash - Bash commands
- file - File edits
- stop - Before stopping
- prompt - User input
- all - All events
Actions
- warn - Show warning, allow operation (default)
- block - Prevent operation
Learn More
For detailed rule syntax and examples:
Skill(hookify:writing-rules)
For hook scope decisions:
Skill(abstract:hook-scope-guide)
Support
Issues and questions: https://github.com/athola/claude-night-market/issues
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.
- 5d ago First seen · 89 lines · 6 tokens per session scan A be6ad6c2a593
help is a command published in the GitHub repository athola/claude-night-market (336 stars, last pushed 3d ago), licensed MIT. It adds 6 tokens to every session and 398 once invoked, about $0.0000 per session on Opus 5. 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 commands, from other repositories
explain-code
Explain complex Solana/blockchain code with visual diagrams and step-by-step breakdowns.
code-explainer
Use when a designer needs to understand code that already works. What a file does, what a line means, which parts are safe to change. Plain language with Figma analogies, no developer jargon.
setup-guide
Use when someone is starting from nothing and the terminal is unfamiliar. Installing Node and Claude Code, creating a first project, and what to do when a command fails.
debug-session
Start a comprehensive debugging session.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.