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 contactsgit 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/contacts)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/contacts"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/contacts.svg" alt="Measured on agentmods" 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.01247 |
| Opus 5 | $0.00023 | $0.00624 |
| Sonnet 5 | $0.00009 | $0.00249 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
Clio Contacts 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clio Contacts
Overview
A contact in Clio is a person or a company. Contacts exist
independently of any single matter — the same contact can be the client on
one matter, opposing counsel on another, and a witness on a third. Tools:
clio_contacts_list, clio_contacts_get, clio_contacts_create,
clio_contacts_update. Navigate into the contacts domain first.
No delete tool exists for contacts — same rule as everywhere else in this integration (see api-patterns). A contact that's no longer relevant doesn't get removed through this integration.
Anti-triggers
- An MSP client, its billing entity, or a service-desk contact — every
other plugin here says "contact", "client", and "company" too, and none
of them mean a party to a legal matter. Use
autotask-crm,connectwise-psa-contacts,halopsa-clients,hubspot-contacts, orqbo-customers. - Everyone connected to a case — a contact is a party record, not the
case file. The relationship (client, opposing party, witness) is carried
on the matter; use
clio-mattersto resolve the matter first. - Removing someone's data on request — no delete tool exists here, and legal retention obligations are exactly why. That request goes to the firm, in Clio, with a human deciding.
People vs. Company Contacts
Clio contacts come in two shapes:
| Type | Examples | Notes |
|---|---|---|
| Person | An individual client, an opposing party who is a person, a witness, an individual attorney at another firm | Has first/last name fields |
| Company | A corporate client, an opposing party that's a business entity, a vendor | Has a company/organization name; may have associated people (e.g. a primary contact at the company) |
When creating a contact, get the type right up front — person vs. company determines which fields are meaningful (a company doesn't have a first/last name; a person isn't "incorporated"). If a user describes an entity ambiguously ("Acme" could be a company or could be shorthand for a person at Acme), ask rather than guess, especially before creating a new contact — search first (see below).
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 · 114 lines · 47 tokens per session scan A c3de274687ad
Clio Contacts 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,247 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.
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.
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-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.