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 WYRE-AI/msp-claude-plugins --skill mattersgit 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/skills/wyre-ai/msp-claude-plugins/matters)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/matters"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/matters/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/wyre-ai/msp-claude-plugins/matters"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/matters.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.01253 |
| Opus 5 | $0.00023 | $0.00626 |
| Sonnet 5 | $0.00009 | $0.00251 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
Clio Matters 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 5d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clio Matters
Overview
A matter is Clio's core object — the case or client file. It is the
hub that almost everything else in Clio (activities, tasks, communications,
documents, calendar entries, bills) references via matter_id. See the
api-patterns skill for the full matters-as-hub
picture and the deliberate v1 scope limits that apply across every domain.
Tools: clio_matters_list, clio_matters_get, clio_matters_create,
clio_matters_update. Navigate into the matters domain first
(clio_navigate) — these tools aren't visible until you do.
No delete tool exists for matters. A matter that shouldn't exist anymore gets closed (status change), not removed — see below.
Key Fields
A matter typically carries:
- Client — the contact (person or company) the matter is for. Every matter has exactly one client contact; see the contacts skill for how a contact can be party to many matters in different roles.
- Responsible attorney — the attorney of record on the matter
- Status — see lifecycle below
- Practice area — the area of law the matter falls under (e.g. Litigation, Real Estate, Family Law) — usually a firm-configured picklist
- Matter number / display number — Clio's human-readable matter identifier (distinct from the internal numeric ID)
- Description — free-text summary of what the matter is
- Custom fields — firm-specific fields configured in Clio; treat these as opaque key/value pairs unless the firm has told you what they mean
Matter Status Lifecycle
Matters move through a small set of statuses. Typical values:
| Status | Meaning |
|---|---|
| Open | Active matter, currently being worked |
| Pending | Not yet fully active — e.g. awaiting engagement signature, conflict check, or intake completion |
| Closed | Matter has concluded — no more billable work expected |
Treat status as the primary signal for "is this matter live." When a user asks for "my open matters" or "what's still active," filter on status rather than trying to infer activity from recency of activities/tasks alone — a matter can be quiet-but-open (waiting on a court date) or closed-but-recently-touched (final billing cleanup).
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.
- 5d ago First seen · 117 lines · 47 tokens per session scan A 84ddf9dd9b97
Clio Matters is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 6d ago), licensed Apache-2.0. It adds 47 tokens to every session and 1,253 once invoked, about $0.0002 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 skills, from other repositories
legal-contract-review
A tool for reviewing and drafting legal documents such as contracts, terms of service, privacy policies, and service-level agreements (SLAs). An SLA is a contract that defines expected service performance and remedies.
hr-resume-screener
A resume and cover-letter screening aid based on Korea's National Competency Standards, a framework for describing job skills. It gives human reviewers scores and evidence while masking sensitive personal information.
collab-vendor
A supplier-management guide for comparing vendors, organising contracts, and tracking risks in the supply chain. It also covers cross-border purchasing tasks such as customs documents and trade terms.
legal-patent-analyzer
A patent analysis tool that turns patent data into technology trends, prior-art reports, freedom-to-operate (FTO) reviews, and draft patent applications. FTO means checking whether a product may infringe existing patent claims.
legal-service-launch-checklist
A pre-launch legal compliance checklist for apps, websites, online stores, and content services. It checks areas such as privacy, consumer sales, advertising, app permissions, subscriptions, and AI-generated content under South Korean rules.
legal-patent-search
A search tool for Korean patents, utility models, designs, and trademarks using KIPRIS Plus, a public intellectual-property search service. It collects publication details, key patent claims, and classification information.