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.
npx skills add Totes-MickGOATs/opus-pocus --skill muffliato-hookusgit clone --depth 1 https://github.com/Totes-MickGOATs/opus-pocusWrote 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/skills/totes-mickgoats/opus-pocus/muffliato-hookus)<a href="https://agentmods.dev/skills/totes-mickgoats/opus-pocus/muffliato-hookus"><img src="https://agentmods.dev/badge/skills/totes-mickgoats/opus-pocus/muffliato-hookus/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/skills/totes-mickgoats/opus-pocus/muffliato-hookus"><img src="https://agentmods.dev/badge/skills/totes-mickgoats/opus-pocus/muffliato-hookus.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.00140 | $0.01011 |
| Opus 5 | $0.00070 | $0.00505 |
| Sonnet 5 | $0.00028 | $0.00202 |
| Haiku 4.5 | $0.00014 | $0.00101 |
Grade A, and why
muffliato-hookus 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
✨ Muffliato Hookus
"Your hooks talk too much. 81% of the noise is one guy."
Every hook that injects additionalContext charges every prompt. Individually reasonable
hooks compound into thousands of tokens of standing overhead — and the noise is rarely even:
in one measured repo, a single keyword-matching dispatch hint accounted for ~81% of all
injection, much of it false-positive matches (a regex for \bai\b matching every path
containing .ai/).
What to scan
- Hook wiring in
.claude/settings*.json(which events, which matchers) - Every hook script that emits
additionalContext,systemMessage, or stdout the model sees - Recent session transcripts, if accessible — the ground truth for what actually got injected
Measurement first
Rank before fixing. Per emitter: fires per session × average bytes per fire = injection share. Transcripts give this directly (grep injected blocks by their headers and measure); without transcripts, instrument each hook to log its output size for a few sessions (→ The Pensieve). Fixing the #4 emitter while #1 stands is wand-waving.
Anti-patterns to find
- Keyword matchers with false-positive regexes. Word-boundary patterns that match paths, substrings matching unrelated terms. Symptom: the hint names an obviously wrong target.
- Every-prompt injection of once-per-session facts. Environment info, standing rules, and rosters re-injected on each prompt instead of once at SessionStart.
- Unconditional emitters. Hooks that always print something — status lines, reminders — with no relevance gate. Silence must be an output.
- Over-broad event matchers. A PostToolUse hook on
*doing work only meaningful forWrite|Edit. - Full-payload dumps. Hooks injecting whole file lists, logs, or reports where a count and a path would do; oversized payloads that should spill to a file with a one-line pointer.
- Advisory duplication. Two hooks reporting the same condition from different angles — double the tokens, and the twin re-raises what the first already reported (→ also feeds Finite Recursum spirals).
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.
- 9d ago First seen · 70 lines · 140 tokens per session scan A 46ac1ba4dc99
muffliato-hookus is a skill published in the GitHub repository Totes-MickGOATs/opus-pocus (10 stars, last pushed 1mo ago), licensed MIT. It adds 140 tokens to every session and 1,011 once invoked, about $0.0007 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-08-31.
Other skills, from other repositories
claude-md-architect
Design, create, extract, or audit CLAUDE.md files and their supporting docs/ folder structure for Claude Code projects. Use this skill whenever the user asks to create a new CLAUDE.md, extract context from a long session into a CLAUDE.md system, audit/refactor an existing CLAUDE.md that has bloated, review whether…
huggingface-llm-trainer
Train or fine-tune language models with TRL or Unsloth on Hugging Face Jobs, including SFT, DPO, GRPO, reward models, and GGUF conversion. Use for cloud LLM training; use huggingface-vision-trainer for vision tasks.
feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
memstack-development-refactor-planner
Use this skill when the user says 'refactor', 'refactoring plan', 'code cleanup', 'reduce duplication', 'simplify code', 'tech debt', 'god class', 'tight coupling', or needs to systematically improve existing code. Identifies targets, assesses risk, and builds incremental execution plans. Do NOT use for writing new…
memstack-product-feedback-analyzer
Use this skill when the user says 'analyze feedback', 'feedback analysis', 'what are customers asking for', or has support tickets, reviews, or survey data to categorize, score, and prioritize into actionable reports. Do NOT use for competitor analysis or market research.