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/search-contacts)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/search-contacts"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/search-contacts/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/wyre-ai/msp-claude-plugins/search-contacts"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/search-contacts.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.00011 | $0.00561 |
| Opus 5 | $0.00005 | $0.00280 |
| Sonnet 5 | $0.00002 | $0.00112 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
search-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 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search Clio Contacts
Search for people and companies in Clio's contact list. Useful for resolving a client before creating a matter or logging a time entry, or for checking whether a contact already exists before creating a new one.
Prerequisites
- Clio connected via Conduit
- Navigate into the
contactsdomain (clio_navigate) - Tools:
clio_contacts_list,clio_contacts_get
Steps
-
Navigate into the contacts domain if you haven't already.
-
Search — call
clio_contacts_listwith the query matched against name, company, and email. Law firms commonly have multiple contacts with similar or identical names across different matters, so don't assume the first hit is the right one. -
Page if needed before declaring results complete.
-
Format and return results, distinguishing people from companies, and noting matter associations if the user's context needs disambiguation (e.g. "which Acme contact — the one on the 2024 litigation matter or the 2023 lease matter?").
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| query | string | Yes | Name, company name, or email to search |
Examples
/search-contacts "Acme"
/search-contacts "[email protected]"
/search-contacts "John Smith"
Output
Found 2 contacts matching "John Smith"
+-------------+------+----------------------------+------------------------+
| Name | Type | Email | Notes |
+-------------+------+----------------------------+------------------------+
| John Smith | Person | [email protected] | Client — Acme Corp |
| John Smith | Person | [email protected] | Opposing party — Beta |
+-------------+------+----------------------------+------------------------+
These are different people with the same name — confirm which one before
using either in a matter or time entry.
No Results
No contacts found matching "Jane Doe"
Suggestions:
- Check spelling
- Try searching by email instead of name
- If this is a brand-new client, create the contact rather than searching further
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 · 86 lines · 11 tokens per session scan A b20645750e9a
search-contacts is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 6d ago), licensed Apache-2.0. It adds 11 tokens to every session and 561 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.
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.