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/status)<a href="https://agentmods.dev/commands/ngocsangyem/meowkit/status"><img src="https://agentmods.dev/badge/commands/ngocsangyem/meowkit/status/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/status"><img src="https://agentmods.dev/badge/commands/ngocsangyem/meowkit/status.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.00876 |
| Opus 5.5 | $0.00000 | $0.00350 |
| Sonnet 5.5 | $0.00000 | $0.00175 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
status 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mk:status — Delivery Status Report
Usage
/mk:status
/mk:status <plan-dir>
/mk:status <plan-slug>
Behavior
Generates a classified, evidence-based delivery status report for the active plan via the project-manager agent. Report is co-located inside the plan dir at {plan-dir}/status-reports/{YYMMDD}-status.md.
This is the foreground entry point for the project-manager agent. Use it when the agent's background auto-invocation (via post-phase-delegation.md rule) is not applicable — e.g., when asking on demand or when disambiguation between multiple active plans is needed.
For "what should I do next" advice, use /mk:help instead. PM is backward-looking ("what's done, what's blocked"); mk:help is forward-looking.
Execution Steps
1. Resolve the plan
- If an argument is given → treat as
{plan-dir}or{plan-slug}:- If it's an absolute or relative path to a plan dir → use directly
- If it's a slug → resolve via
ls -d tasks/plans/*{slug}* - If not found → print "Plan not found: {arg}. Use tasks/plans// form." → exit
- If no argument → Glob
tasks/plans/*/plan.mdfiltered by frontmatterstatusnot in{completed, cancelled, archived}:- 0 results → print "No active plan. Run
/mk:planto create one." → exit (no file written) - 1 result → use it
- 2+ results → prompt via
AskUserQuestion:- header: "Active plan"
- question: "Which plan should I report on?"
- options: one per plan (label = title + created date from frontmatter)
- 0 results → print "No active plan. Run
2. Delegate to project-manager
Invoke the project-manager agent with the resolved plan dir:
@project-manager Generate delivery status for plan at <plan-dir>.
Write report to <plan-dir>/status-reports/{YYMMDD}-status.md
(create the status-reports/ subdir if absent).
Load template from tasks/templates/pm-status-template.md.
Foreground invocation — do NOT include "run in the background" in the prompt. The command must wait for PM to return the report path before step 3.
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 · 78 lines · 0 tokens per session scan A eb7a936ce65b
status 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 876 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-09-03.
Other commands, from other repositories
runs
List live and persisted CCAM-launched Claude Code and Codex runs.
project-health
Audit and manage project configuration — permissions, context, docs.
tasks
../../vertical-plugins/scenarios/commands/tasks.md.
finish-tasks
Finalize a work item after all tasks are done — cleanup (currently closing the ticket) and mark the work complete.
stat
A project-status command for an embedded-software project. It reads saved project notes and shows the current state, progress, next action, or a fuller project overview.
rec
A project-recovery command that reads a small set of status files and shows the current work and next action.