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 alexclowe/awesome-copilot-cowork-plugins --skill pet-owner-communicationgit clone --depth 1 https://github.com/alexclowe/awesome-copilot-cowork-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/alexclowe/awesome-copilot-cowork-plugins/pet-owner-communication)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/pet-owner-communication"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/pet-owner-communication/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/alexclowe/awesome-copilot-cowork-plugins/pet-owner-communication"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/pet-owner-communication.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.00025 | $0.00890 |
| Opus 5 | $0.00013 | $0.00445 |
| Sonnet 5 | $0.00005 | $0.00178 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
pet-owner-communication 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 9d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You understand how to communicate veterinary information to pet owners effectively. When the user is preparing client-facing materials, emails, or discussion guides, apply these principles automatically.
Empathetic language for difficult conversations
When communicating about serious diagnoses, poor prognosis, or end-of-life decisions:
- Always use the pet's name — never "the animal" or "your pet" alone
- Acknowledge the human-animal bond: "I know how much [Pet Name] means to your family"
- Present information honestly but gently — lead with what you know, then what it means
- Avoid euphemisms that create confusion, but soften clinical bluntness:
- "The cancer has spread" not "metastatic neoplasia" — but also not "it's really bad"
- "This condition cannot be cured, but we can keep [Pet Name] comfortable" rather than "there's nothing we can do"
- Offer all options without judgment — treatment, palliative care, hospice, euthanasia
- For euthanasia discussions, use the word directly but compassionately: "If and when you feel it's time, we can help [Pet Name] pass peacefully"
- Provide quality-of-life frameworks (Villalobos HHHHHMM scale: Hurt, Hunger, Hydration, Hygiene, Happiness, Mobility, More good days than bad)
- Close every difficult conversation with support: "There is no wrong decision here — we're here to support you and [Pet Name]"
Cost discussion frameworks
Veterinary costs are a sensitive topic. When drafting cost-related communications:
- Be transparent about costs upfront — surprises erode trust
- Present estimate ranges (low to high) rather than single figures
- Break down what each component covers so clients understand the value
- Acknowledge that cost is a real concern: "We understand that finances are an important part of this decision"
- Present payment options without judgment: payment plans, CareCredit, pet insurance filing assistance, third-party financing
- If a client cannot afford the ideal treatment, offer tiered options:
- Gold standard: Full workup and treatment
- Middle ground: Essential diagnostics and treatment
- Minimum viable: Symptomatic management with monitoring
- Never make the client feel guilty for choosing a less expensive option
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.
- 9d ago First seen · 78 lines · 25 tokens per session scan A dcf0f54afa93
pet-owner-communication is a skill published in the GitHub repository alexclowe/awesome-copilot-cowork-plugins (17 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 890 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-03.
Other skills, from other repositories
commitment-catcher
Scans the last 24 hours of email, Teams chats and meeting transcripts for commitments in both directions, things the user promised to others and things others promised to the user. Maintains a running commitments.md ledger with open, done and overdue statuses, flags overdue items first, and creates To Do entries with…
custom-daily-brief
Builds a role-tuned morning brief as a Word document covering emails that need replies, today's calendar, Teams mentions and upcoming deadlines, using section presets from an editable config file. Use when the user asks for their daily brief, morning brief, start-of-day summary or custom briefing, or wants to change…
project-dashboard-builder
Generates a self-contained single-file HTML project dashboard (status banner, milestones, risks heat list, decisions log, links) from the tracker files in /Documents/Cowork/projects/, saved as dashboard- -YYYY-MM-DD.html. Use when the user asks for a project dashboard, a shareable or pinnable status page, an HTML…
chro-reviewer
Reviews a proposal, business case, deck or plan in character as a Chief Human Resources Officer archetype, then saves a structured review document with a verdict, findings that cite the artifact, people and organisation risks and five interrogation questions. Use when the user asks for a CHRO or HR review, a…
customer-advocate-reviewer
Reviews a proposal, business case, deck or plan in character as a Customer Advocate archetype, then saves a structured review document with a verdict, findings that cite the artifact, customer-side risks and five interrogation questions. Use when the user asks for a customer advocate review, a customer-lens or…
frontline-skeptic-reviewer
Reviews a proposal, business case, deck or rollout plan in character as a Frontline Skeptic archetype, the experienced staff member who will have to live with the change, then saves a structured review with a verdict, findings that cite the artifact, adoption risks and five interrogation questions. Use when the user…