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/WYRE-AI/msp-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/wyre-ai/msp-claude-plugins/matter-summary)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/matter-summary"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/matter-summary.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.00023 | $0.00984 |
| Opus 5 | $0.00012 | $0.00492 |
| Sonnet 5 | $0.00005 | $0.00197 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
matter-summary 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 4d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clio Matter Summary
Pull a consolidated, one-screen view of a single matter: the matter details, its client/related contacts, open tasks, recent time/expense activities, recent communications (read-only), and bill status. This is the "what's the state of this case" workflow.
Prerequisites
- Clio connected via Conduit
- Navigate into each domain used below before calling its tools
- Tools:
clio_matters_get,clio_contacts_get,clio_tasks_list,clio_activities_list,clio_communications_list,clio_bills_list
Steps
-
Resolve the matter
If
matter_idwasn't provided, ask for it or run /search-matters first — don't guess at a matter ID. -
Get the matter record —
clio_matters_get(matter_id). Note status, responsible attorney, practice area, and client contact ID. -
Get the client contact —
clio_contacts_get(client_id)for the matter's client. If the matter has other related contacts (opposing party, witnesses), include them if the tool surface exposes them for this matter. -
List open tasks —
clio_tasks_listfiltered to thismatter_id, open/incomplete only unless asked for all. -
List recent activities —
clio_activities_listfiltered to thismatter_id, most recent first, reasonably bounded (e.g. last 10–20 or last 30 days) unless the user wants full history. -
List recent communications (read-only) —
clio_communications_listfiltered to thismatter_id. This is privileged content — summarize factually (who/when/subject) without embellishing or speculating about content you weren't given. -
List bills —
clio_bills_listfiltered to thismatter_id. Report status and amounts; remember bills are read-only — do not offer to generate or modify one (see time-billing). -
Assemble the summary in this order: matter header (number, status, attorney, practice area) → client/related contacts → open tasks → recent activities → recent communications → bill status.
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.
- 4d ago First seen · 120 lines · 23 tokens per session scan A 692fde38ff98
matter-summary is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 5d ago), licensed Apache-2.0. It adds 23 tokens to every session and 984 once invoked, about $0.0001 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-04.
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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.