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 directorygit 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/directory)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/directory"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/directory.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.00048 | $0.00753 |
| Opus 5 | $0.00024 | $0.00377 |
| Sonnet 5 | $0.00010 | $0.00151 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
3CX Directory & 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 8d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
3CX Directory & Contacts
Overview
3CX exposes read-only lookups across three sources: the PBX's own phonebooks (company and personal entries), the PBX's user/extension list, and — where the PBX has a CRM connector configured — contacts synced in from that CRM. All of it is read-only; nothing in this skill creates or edits a contact or extension.
Anti-triggers
- The CRM record itself — this skill only reads what 3CX has synced in
or is querying live from a connected CRM. To create or edit the actual
CRM contact, use
hubspot-contactsorsalesbuildr-companies-contacts. - The client's documentation record — extension lists and phone trees
that belong in runbooks live in
hudu-companies, not here.
Capabilities
Exact tool names are not published by 3CX — see the api-patterns skill
for why, and call tools/list for the authoritative names on a connected
PBX. The read-only capabilities this skill covers:
- Find a contact by email
- Find a contact by exact extension
- Search CRM-integrated contacts
- Search 3CX phonebooks
- List PBX users/extensions
Common Workflows
Resolve a caller
- If you have an email address or an exact extension number, use the matching exact-match lookup first — it's the most reliable signal.
- If that comes back empty, fall back to a phonebook search or a CRM-integrated contact search for a partial or fuzzy match.
- If you only have a name, search the phonebook and the CRM-integrated contacts in parallel — one may have an entry the other doesn't.
Cross-reference with the PSA or CRM
A miss on CRM-integrated contact search means "not synced to this PBX," not "doesn't exist in the CRM." The sync is whatever CRM connector is configured on that specific PBX — confirm the connector is active before concluding a contact genuinely doesn't exist anywhere.
Gotchas
- Extension lookup is exact-match, not fuzzy. A partial or slightly-wrong extension number won't resolve — fall back to the user list or a phonebook search instead of retrying the same lookup.
- CRM-integrated results reflect the PBX's own sync, not a live CRM query. Staleness depends entirely on how that PBX's CRM connector is configured — this skill has no visibility into that connector's refresh interval.
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.
- 8d ago First seen · 76 lines · 48 tokens per session scan A 4de11ae7248d
3CX Directory & Contacts is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 5d ago), licensed Apache-2.0. It adds 48 tokens to every session and 753 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-08-30.
Other skills, from other repositories
review
5-pass structured code review — correctness, security, performance, readability, consistency.
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
content-card-news
A planning tool for four-card social media carousels on Instagram, Threads, and Kakao Channel, combining card copy, design guidance, image prompts, captions, and hashtags.
design-copywriting
A copywriting workflow for marketing and product pages that uses a brand voice and returns structured text for page sections.
cs-voc-triage
A customer-feedback analysis tool that combines reviews and support contacts from multiple channels. VOC means “voice of the customer”: the comments, questions, complaints, and praise customers leave about a business.
data-realestate
A lookup tool for reported South Korean property transactions using Ministry of Land data. It covers sales and rental deals for apartments, officetels, multi-family homes, houses, and commercial or office properties.