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/plan)<a href="https://agentmods.dev/commands/ngocsangyem/meowkit/plan"><img src="https://agentmods.dev/badge/commands/ngocsangyem/meowkit/plan/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/plan"><img src="https://agentmods.dev/badge/commands/ngocsangyem/meowkit/plan.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.00269 |
| Opus 5.5 | $0.00000 | $0.00108 |
| Sonnet 5.5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
plan 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
/plan — Phase 1: Planning
Usage
/mk:plan [feature description] [--html]
--html (composable): after Gate 1 approval and task hydration, also render the plan to a shareable {plan_dir}/plan.html via mk:visual-plan. Opt-in; the markdown plan files stay the source of truth. Not valid on the archive / red-team / validate subcommands.
Purpose
Create an implementation plan through mk:plan-creator. Output is documentation only; no source or test files are written (with --html, a derived plan.html is rendered from the approved plan).
Dispatch
Activate mk:plan-creator with the feature description and any user-provided planning flags. Use the planning skill's references for scope challenge, workflow model selection, codebase scouting, and validation.
Safety notes
- Plan output goes under
tasks/plans/YYMMDD-feature-name/. - Gate 1 requires an explicit human approval before implementation.
- A valid plan contains Goal, Context, Scope, Constraints, and Acceptance Criteria.
Output
A plan directory at tasks/plans/YYMMDD-feature-name/ with plan.md + reports/, awaiting human approval.
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 · 28 lines · 0 tokens per session scan A c15bdef6503f
plan 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 269 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.