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 skill-templategit 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.
![agentmods badge for [Vendor] [Topic]](/badge/skills/wyre-ai/msp-claude-plugins/skill-template.svg?v=0-45-C){kind=icon}
[](https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/skill-template)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/skill-template"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/skill-template.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.00045 | $0.00777 |
| Opus 5 | $0.00023 | $0.00388 |
| Sonnet 5 | $0.00009 | $0.00155 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade C, and why
[Vendor] [Topic] scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Structure guidance (delete this comment in real skills): - Keep SKILL.md lean. It should carry the knowledge Claude can't infer from the API itself: domain concepts, non-obvious constraints, workflow shape, and gotc How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[Skill Title]
Overview
One short paragraph: what this domain is and what an MSP does with it.
Anti-triggers
Where this skill gets loaded by mistake, and what to load instead. One bullet per case, each naming the correct destination skill:
- [Neighbouring concern] — use
[vendor]-[other-skill]instead. - [Adjacent vendor with overlapping vocabulary] — this skill only speaks the [Vendor] API.
Include this section only when a real routing mistake exists: a
sibling skill in the same plugin covering an adjacent entity, or another
vendor sharing this one's vocabulary. Two skills whose names alone
disambiguate them do not need it. A bullet that just negates the
when_to_use ("do not use for non-[Vendor] questions") is filler —
cut it.
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 · 93 lines · 45 tokens per session scan C 46efda939bd3
[Vendor] [Topic] 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 45 tokens to every session and 777 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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.
meta-feedback
A feedback reporter that collects bug reports and feature requests, then formats them as GitHub Issues. GitHub Issues are shared records used by development teams to track work and problems.