Borrowing it
Nothing to install: this file belongs to that0n3guy/mealie-mcp-server-ts. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/that0n3guy/mealie-mcp-server-ts/main/.claude/commands/clavix/summarize.mdgit clone --depth 1 https://github.com/that0n3guy/mealie-mcp-server-tsWrote 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/that0n3guy/mealie-mcp-server-ts/summarize)<a href="https://agentmods.dev/commands/that0n3guy/mealie-mcp-server-ts/summarize"><img src="https://agentmods.dev/badge/commands/that0n3guy/mealie-mcp-server-ts/summarize/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/that0n3guy/mealie-mcp-server-ts/summarize"><img src="https://agentmods.dev/badge/commands/that0n3guy/mealie-mcp-server-ts/summarize.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.12867 |
| Opus 5 | $0.00000 | $0.06434 |
| Sonnet 5 | $0.00000 | $0.02573 |
| Haiku 4.5 | $0.00000 | $0.01287 |
Grade C, and why
summarize scanned grade C with 2 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.
Subtle steeringmediumPrompt injection
Instructions that bias recommendations or shape behaviour without the user noticing.
**⚠️ Never tell the user a file was saved without verifying it exists.** Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
> Here's the improved version: [show prompt]" How it starts
The opening of the file, as written. The whole thing — 1,596 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clavix: Turn Our Chat Into Requirements
Time to capture what we discussed! I'll go through our conversation, pull out the key requirements, and create clear documentation you can use.
What This Does
When you run /clavix:summarize, I:
- Read our conversation - Everything we talked about
- Extract the requirements - What you want to build
- Organize and improve them - Make them clear and actionable
- Create documentation - Mini-PRD and optimized prompt files
- Flag unclear areas - Things we might need to discuss more
I'm capturing what we discussed, not building anything yet.
CLAVIX MODE: Extraction Only
I'm in extraction mode. Summarizing our conversation.
What I'll do:
- ✓ Analyze everything we discussed
- ✓ Pull out the key requirements
- ✓ Organize them into a clear structure
- ✓ Create documentation files
- ✓ Tell you what's still unclear
What I won't do:
- ✗ Write code for the feature
- ✗ Start implementing anything
- ✗ Make up requirements we didn't discuss
I'm documenting what we talked about, not building it.
For complete mode documentation, see: .clavix/instructions/core/clavix-mode.md
Self-Correction Protocol
DETECT: If you find yourself doing any of these 6 mistake types:
| Type | What It Looks Like |
|---|---|
| 1. Implementation Code | Writing function/class definitions, creating components, generating API endpoints, test files, database schemas, or configuration files for the user's feature |
| 2. Skipping Pre-Validation | Not checking conversation completeness before extracting requirements |
| 3. Missing Confidence Indicators | Not annotating requirements with [HIGH], [MEDIUM], [LOW] confidence |
| 4. Not Creating Output Files | Not creating mini-prd.md, optimized-prompt.md, and quick-prd.md files |
| 5. No Optimization Applied | Not applying quality patterns to extracted requirements |
| 6. Capability Hallucination | Claiming features Clavix doesn't have, inventing workflows |
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 · 1,596 lines · 0 tokens per session scan C 5bb2086822a2
summarize is a command published in the GitHub repository that0n3guy/mealie-mcp-server-ts (0 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 12,867 tokens. A static security scan graded it C with 2 findings (subtle steering, asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.