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 ngocsangyem/MeowKit --skill elicitgit 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/elicit)<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/elicit"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/elicit/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/ngocsangyem/meowkit/elicit"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/elicit.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.00089 | $0.01555 |
| Opus 5 | $0.00044 | $0.00777 |
| Sonnet 5 | $0.00018 | $0.00311 |
| Haiku 4.5 | $0.00009 | $0.00155 |
Grade A, and why
mk:elicit 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 8d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Elicitation — Structured Second-Pass Reasoning
Re-examine an existing output (review verdict, plan, analysis) through a named reasoning method. Surfaces insights that generic "make it better" requests miss.
When to Use
- After
/mk:reviewverdict — deepen analysis before Gate 2 - After plan creation — stress-test assumptions before Gate 1
- After any agent output — when user wants a specific angle of analysis
- When user says "dig deeper", "what am I missing", "challenge this"
NOT this skill if: you have no existing artifact to re-examine — use mk:brainstorming for open exploration, or mk:problem-solving for approach-stuck situations.
Reasoning Methods
| Method | Lens | Best For |
|---|---|---|
| Pre-mortem | "Assume this shipped and failed. Why?" | Risk discovery, failure mode analysis |
| Inversion | "What would make this maximally wrong?" | Assumption testing, edge cases |
| Red Team | "You are an attacker. How do you exploit this?" | Security analysis, adversarial thinking |
| Socratic | "What evidence supports each claim?" | Logic validation, gap detection |
| First Principles | "Strip assumptions. What's fundamentally true?" | Architecture decisions, design simplification |
| Constraint Removal | "What if [constraint X] didn't exist?" | Innovation, scope exploration |
| Stakeholder Mapping | "Who else is affected? What do they need?" | Impact analysis, requirements gaps |
| Analogical | "What similar system solved this differently?" | Alternative approaches, pattern matching |
Workflow
- Load context — Read the output being re-examined (verdict file, plan file, or conversation context)
- Present methods — Show the table above; ask user to pick one (or suggest based on context)
- Apply method — Re-examine the output through the chosen lens
- Produce analysis — Structured output with:
- Method applied
- Key findings (numbered, actionable)
- Severity: CRITICAL / IMPORTANT / INFORMATIONAL
- Recommendations (what to change, if anything)
- Optional repeat — User may pick another method for multi-lens analysis
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.
- 8d ago First seen · 131 lines · 89 tokens per session scan A 4a7f6ceec014
mk:elicit is a skill published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 1,555 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
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
investigate
Investigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.
narrow-bare-rescue
Narrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
verify
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.
phx-investigate
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional Amp subagents only when useful.