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/ngocsangyem/MeowKitWrote 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/ngocsangyem/meowkit/fix)<a href="https://agentmods.dev/commands/ngocsangyem/meowkit/fix"><img src="https://agentmods.dev/badge/commands/ngocsangyem/meowkit/fix/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/ngocsangyem/meowkit/fix"><img src="https://agentmods.dev/badge/commands/ngocsangyem/meowkit/fix.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.00000 | $0.00293 |
| Opus 5.5 | $0.00000 | $0.00117 |
| Sonnet 5.5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
fix 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
/fix — Bug Fix
Usage
/fix [bug description, error message, or CI failure log]
/fix [bug description] --tdd
/fix [bug description] --no-capture
Purpose
Diagnose and fix a defect root-cause-first. Accepts direct bug descriptions, error
messages, stack traces, and CI failure logs. The authoritative procedure — mode selection,
memory check, scout, diagnosis, complexity routing, verification, and capture — lives in
mk:fix.
Dispatch
Activate mk:fix with the user's bug description and any user-provided flags. Do not
classify, diagnose, or fix in this command; the skill owns the whole flow.
Flags
--tdd— Force a failing regression test before the fix. Default: regression tests are recommended but not gated.--no-capture— Suppress the skill's memory capture step.--auto|--review|--quick|--parallel— Execution mode. Seemk:fixArguments; the skill prompts for a mode when none is given.
Safety notes
- Gate 1 and Gate 2 are human-approved per
.claude/rules/gate-rules.md; the skill's own routing decides which apply to a given fix, including the documented complexity=simple Gate 1 bypass.
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 · 32 lines · 0 tokens per session scan A 34f073d30be9
fix is a command published in the GitHub repository ngocsangyem/MeowKit (15 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 293 tokens. 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 commands, from other repositories
tail-events
Show the latest N ingested events with timestamp, eventtype, and toolname.
health
One-line reliability verdict (OK / DEGRADED / FAILING) for Claude Code usage.
replay
Summarize one Agent Monitor session by id — header plus a concise transcript recap.
tidy
The structural baseline is empty. scripts/code-quality-baseline.json has no entries, so every gate is live: a new violation is now a hard failure with nothing to hide behind. That is the regime this session works in.
paydown
Pay down the frozen code-quality baseline and run a full QA sweep.
test-and-fix
Run tests, auto-fix fmt and lint, and fix failures until green or stuck.