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 lukacf/meerkat --skill hook-authoringgit clone --depth 1 https://github.com/lukacf/meerkatWrote 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/lukacf/meerkat/hook-authoring)<a href="https://agentmods.dev/skills/lukacf/meerkat/hook-authoring"><img src="https://agentmods.dev/badge/skills/lukacf/meerkat/hook-authoring/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/lukacf/meerkat/hook-authoring"><img src="https://agentmods.dev/badge/skills/lukacf/meerkat/hook-authoring.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.00020 | $0.00837 |
| Opus 5.5 | $0.00008 | $0.00335 |
| Sonnet 5.5 | $0.00004 | $0.00167 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
Hook Authoring 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hook Authoring
Use hooks for runtime observation and policy decisions at typed lifecycle points. Hooks can observe and, at policy-capable points, allow or deny; they should not become hidden owners of runtime truth.
Hook Points
Meerkat provides 14 hook points across the agent, runtime, and comms lifecycles:
- RunStarted - When the agent run begins
- PreLlmRequest - Before sending to the LLM
- PostLlmResponse - After receiving the LLM response
- PreToolExecution - Before executing a tool call
- PostToolExecution - After tool execution completes
- TurnBoundary - At the boundary between turns
- RunCompleted - When the agent run completes successfully
- RunFailed - When the agent run fails
- RuntimeInputAccepted - After runtime authority durably admits an input
- RuntimeInputRejected - After an input is terminally rejected without an admission commit
- RuntimeInputDeduplicated - When an idempotent submission resolves to an existing admitted input
- PeerIngressCommitted - After a typed peer input is committed by runtime admission
- PeerEgressCommitted - When a peer send reaches the successful outcome proved by its transport and local lifecycle authority
- InteractionCompleted - After a correlated interaction completion is durably published
The last six points are observe-only: they report already-committed or
terminally-resolved facts. They require capability: observe in either
foreground or background mode. They cannot allow, deny, or otherwise change
the outcome being observed.
Execution Modes
For the eight agent-loop points (RunStarted through RunFailed in the list):
- Foreground hooks run in ascending priority, then registration order. A deny short-circuits later foreground hooks at that point.
- Background hooks run concurrently and must declare
capability: observe. Their decisions are discarded. Use them for logging and analytics, not policy enforcement.
The six observe-only points use post-commit dispatch, which does not await hook execution or grant policy authority even when an entry is foreground.
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 Changed · +23 lines db5a8ade123f
- 1mo ago First seen · 63 lines · 20 tokens per session scan A 7ccde8bf8f78
Hook Authoring is a skill published in the GitHub repository lukacf/meerkat (23 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 837 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
desktop-brand-builder
Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop.
batch-api
Prepare a many-file, single-turn transform (translate, rewrite, extract) as a plan and submit it to the asynchronous, half-price DashScope Batch API; results are delivered as new files hours later. Invoke explicitly with /batch-api.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.