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/extremeclarity/claude-pluginsWrote 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/extremeclarity/claude-plugins/consolidate)<a href="https://agentmods.dev/commands/extremeclarity/claude-plugins/consolidate"><img src="https://agentmods.dev/badge/commands/extremeclarity/claude-plugins/consolidate.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.1 | $0.00008 | $0.00495 |
| Opus 5 | $0.00004 | $0.00247 |
| Sonnet 5 | $0.00002 | $0.00099 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
consolidate 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 6d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consolidate
Remove redundant entries and merge overlapping context.
Execution Model
Silent execution: Do not narrate your reasoning process. Work through steps 1-4 internally, then output only the final plan in step 5.
- Enter plan mode
- Read — Load all context files and framework index
- Plan — Analyze for redundancy and supersession using rules below
- Deep read — If potential framework overlaps detected from index, read the full framework files before making recommendations
- Present — Show only the final plan to user for approval (no preamble, no reasoning)
- Execute — Apply approved changes
What to Look For
Redundant Entries
Two entries express the same idea. Propose:
- Merge — combine into a single, stronger entry
- Remove — delete the weaker/duplicate entry
Superseded Entries
Newer entry contradicts or replaces older one. Propose:
- Remove — delete the stale version
Targets
Terminology
- Same term defined differently across entries
- Different terms meaning the same thing
Principles
- Conflicting guidance (newer supersedes older)
- Same principle restated in different words
Anti-patterns
- Duplicate warnings
- Overlapping anti-patterns that could merge
Insights
- Newer insight invalidates older one
- Same insight captured multiple times
Frameworks
- Scan index for potential overlaps (similar problem types, related summaries)
- If potential overlaps found, read full framework files to confirm before recommending
- Only propose merge/removal after reading actual content
Plan Format
Present proposed changes grouped by action:
## Remove
- [category] "entry text" — reason
## Merge
- [category] "entry A" + "entry B" → "merged entry"
Anti-Patterns
- DO NOT narrate your analysis — work silently, output only the final plan
- DO NOT remove entries that are merely related — they must be truly redundant or superseded
- DO NOT skip plan mode — all changes require approval
- DO NOT auto-merge without showing both originals and proposed result
- DO NOT recommend framework changes based only on index summaries — read full files first
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.
- 6d ago First seen · 83 lines · 8 tokens per session scan A b31d12a5727e
consolidate is a command published in the GitHub repository extremeclarity/claude-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 8 tokens to every session and 495 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.