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/configure)<a href="https://agentmods.dev/commands/athola/claude-night-market/configure"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/configure/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/configure"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/configure.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.00009 | $0.00308 |
| Opus 5.5 | $0.00004 | $0.00123 |
| Sonnet 5.5 | $0.00002 | $0.00062 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
configure 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 1mo 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 Configure Command
Interactive configuration for enabling and disabling rules.
Usage
/hookify:configure
Interactive Flow
- Shows list of all rules
- Prompts for which rule to configure
- Asks to enable, disable, or delete
- Updates rule file immediately
Example Session
Hookify Rules
=============
1. ✅ dangerous-rm (bash, block)
2. ⚠️ warn-console-log (file, warn)
3. ❌ require-tests (stop, warn) [DISABLED]
Select rule number (1-3) or 'q' to quit: 3
Rule: require-tests
Status: Disabled
Event: stop
Action: warn
Actions:
[e] Enable rule
[d] Delete rule
[q] Cancel
Choice: e
✅ Rule 'require-tests' enabled!
Quick Enable/Disable
You can also edit files directly:
# Disable a rule
vi .claude/hookify.dangerous-rm.local.md
# Change: enabled: false
# Enable a rule
# Change: enabled: true
See Also
/hookify:list- View all rules/hookify- Create new rule
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.
- 1mo ago First seen · 70 lines · 9 tokens per session scan A 253a0c514166
configure is a command published in the GitHub repository athola/claude-night-market (343 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 308 once invoked, about $0.0000 per session on Opus 5.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
prompt
System instructions for writing effective prompts. Apply when generating commands, skills, agents, or any LLM instructions.
analyze-codebase
Generate comprehensive analysis and documentation of entire codebase.
audit
Perform security audit on codebase.
anti-slop-designer
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.
codex-review
Run OpenAI Codex code review on current changes or a specific branch/commit.
design-critic
Use when you want an honest read on a design instead of encouragement. What is wrong, ranked by severity, with the reason attached. Works on a screenshot, a mockup, or a described screen.