microsoft/cat-agent-skills is a static website that catalogs reusable instruction sets and related packages for AI agents. People use it to search, filter, rate, and download skills for Cowork, Copilot Studio, and Scout, along with Copilot plugins and Scout automations. The catalogue entries are the skills, instructions, plugins, and settings displayed by the site.
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 microsoft/cat-agent-skills --skill patient-instructionsgit clone --depth 1 https://github.com/microsoft/cat-agent-skillsWrote 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/microsoft/cat-agent-skills/patient-instructions)<a href="https://agentmods.dev/skills/microsoft/cat-agent-skills/patient-instructions"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/patient-instructions/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/microsoft/cat-agent-skills/patient-instructions"><img src="https://agentmods.dev/badge/skills/microsoft/cat-agent-skills/patient-instructions.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.00139 | $0.01728 |
| Opus 5.5 | $0.00056 | $0.00691 |
| Sonnet 5.5 | $0.00028 | $0.00346 |
| Haiku 4.5 | $0.00014 | $0.00173 |
Grade A, and why
patient-instructions 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 2d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Patient Instructions
Action level: L1 (draft for human approval). Instructions are drafted for the discharging clinician to give to the patient; nothing is sent to the patient by this plugin.
Purpose
Give the patient an instruction sheet they can actually act on.
When to use
After med-reconcile, in parallel with summary-draft. Typical triggers: "write the patient instructions", "make this readable for the patient", "plain-language discharge sheet", "just give the patient the same list".
When NOT to use
When NOT to use: do not use it to produce the clinical record (summary-draft), the medication diff (med-reconcile) or the follow-up checklist (followup-plan). Do not use it to reword the clinical summary verbatim into a patient sheet - it is derived from the same evidence, not mechanically simplified. Do not use it to claim a reading level without running the engine, to include a medication still flagged as an unresolved discrepancy, or to send anything directly to the patient.
Inputs
encounter; reconciliation_report.expected_discharge_meds; reconciliation_report.stopped_meds and
reconciliation_report.discrepancies; cited discharge orders and instruction sets on the
contract (discharge_instruction_notes[] - each carries source_note, documented_date and verbatim lines per
section - plus followup_checklist and pending_results); config/readability-rules.json
(metric, max_grade_level, max_sentence_words, banned_jargon, required_sections).
Steps
- If
reconciliation_reportis absent, run med-reconcile first (engine toolpython3 base/scripts/med_reconcile.py --question <payload> --out <payload>); never re-derive the list here. - Draft instructions in plain language, covering every section listed in config/readability-rules.json
required_sections; omit any medication flagged as an unresolved discrepancy, and keep each timing or administration line directly under the medication it belongs to. Under the medicines section write one "take" line perexpected_discharge_medsentry, then one explicit stop/hold line perstopped_medsentry that has no discrepancy for the same drug (for example "Stop taking metformin, including the pills you have at home, until your care team tells you to start again."), carrying that entry's reason,source_noteanddocumented_datein the source list. A documented stop is never left off the sheet - the patient may still have a home supply. - Run the readability_check engine tool (
python3 base/scripts/readability_check.py --question <payload> --config config/readability-rules.json --out <payload>) overpatient_instructions. - Read
readability_report: grade level againstmax_grade_level, long sentences, jargon hits, missing sections. - Revise the wording and re-run until
readability_report.passedis true - the verdict is engine output, never self-asserted; after each revision re-check that every medication line still matches the reconciled dose or stop, and that no instruction moved under a different medication. - Write
patient_instructionsto the contract and hand off for clinician approval.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 96 lines · 139 tokens per session scan A ec0dd5b028cc
patient-instructions is a skill published in the GitHub repository microsoft/cat-agent-skills (101 stars, last pushed yesterday), licensed MIT. It adds 139 tokens to every session and 1,728 once invoked, about $0.0006 per session on Opus 5.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-11-06.
patient-instructions compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| patient-instructionsmicrosoft/cat-agent-skills | Skill | 101 | yesterday | MIT | A | 139 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | yesterday | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 100k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| browser-automationopenclaw/openclaw | Skill | 394k | today | MIT | A | 36 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 4d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |