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 agentmods add skills/ngocsangyem/meowkit/helpnpx skills add ngocsangyem/MeowKit --skill helpgit 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/skills/ngocsangyem/meowkit/help)<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/help"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/help.svg" alt="Measured on agentmods" 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 | $0.00079 | $0.02818 |
| Opus 5 | $0.00039 | $0.01409 |
| Sonnet 5 | $0.00016 | $0.00564 |
| Haiku 4.5 | $0.00008 | $0.00282 |
Grade A, and why
mk:help 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 yesterday.
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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Navigation Help
Answers "What should I do next?" by scanning project state and mapping to the 7-phase pipeline.
How It Works
mk:help is the FORWARD-looking navigator (what to do next). Backward-looking delivery
analysis stays with /mk:status (project-manager) — this skill never reproduces it.
Collect candidates from ALL scan sources below, then RANK them and emit the top 3 — do NOT stop at the first hit. The rank-1 candidate equals what the old "stop at first actionable hit" behavior would have returned (back-compat); ranks 2–3 are alternates with one-line rationale. This skill is read-only: it reads state, never writes it.
1. Paused Step-File Workflows
Check session-state/*-progress.json for any in-progress step-file workflow.
- Found → "Resume [skill] at step [N]. Run
/mk:[skill]to continue."
2. In-Progress Plans
Check tasks/plans/ for plan files without matching review verdicts.
- Plan exists, no tests → "Plan approved. Next: run tester agent (Phase 2 — RED)"
- Plan exists, tests failing → "Tests failing. Next: run developer agent (Phase 3 — GREEN)"
- Plan exists, tests passing, no review → "Tests green. Next: run reviewer agent (Phase 4 — Review)"
3. Pending Reviews
Check tasks/reviews/ for verdict files with WARN or action items.
- WARN verdict → "Review has warnings. Acknowledge and approve for Gate 2, or fix findings."
- FAIL verdict → "Review failed. Fix required changes, then re-run reviewer."
4. Uncommitted Changes
Check git status for staged/unstaged changes.
- Changes exist + review approved → "Ready to ship. Run
/mk:ship(Phase 5)" - Changes exist, no review → "Changes detected but no review. Run reviewer first."
5. Clean State
No plans, no reviews, no changes.
- "Everything clean. Options: start a new task with planner, run
/mk:retro, or ask me anything."
Additional Scan Sources (read after sources 1–5)
ALL four may be absent at rest (e.g. session-state/checkpoints/ does not exist until
runtime). Absent file → skip silently; note the skip only under --verbose. Never error
on a missing source.
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.
- yesterday First seen · 202 lines · 79 tokens per session scan A 8f3dc5ea9677
mk:help is a skill published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 2,818 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
evolving-ai-agents
Provides guidance for automatically evolving and optimizing AI agents across any domain using LLM-driven evolution algorithms. Use when building self-improving agents, optimizing agent prompts and skills against benchmarks, or implementing automated agent evaluation loops.
template-selector
Recommend the right skill bundle, agent, and workflow sequence for a new project — so media professionals can start producing instead of browsing a 394-skill library.
skill-federation
Consult the current state of practice before doing expert work — search a federated catalog of vetted agent skills, read the ones that matter as field notes, install only what you'll reuse. Use at the START of planning (to shape the approach), at the END of planning, when you hit a capability gap mid-task, or on…
beat-setup-guide
Generate a beat setup guide for a journalist starting a new coverage area: source map, document inventory, recurring calendar, key contacts, institutional landscape, and a 30-day ramp-up plan.
welcome-email-writer
Writes the automated welcome email that new subscribers receive immediately after signing up, establishing the newsletter's voice, making the editorial promise concrete, and setting expectations that reduce early unsubscribes.
github-discoverability
Make a GitHub repo or Agent Skill discoverable across the skill-aggregator ecosystem — GitHub topics, scraper-visible SKILL.md paths, instant directories (awesomeskills.dev / SkillsMP), gh skill + agentskills.io conformance, and the MCP registry. Use when someone wants their skill or repo to be "found", indexed…