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 post-market-monitoringgit 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/post-market-monitoring)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/post-market-monitoring"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/post-market-monitoring/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/post-market-monitoring"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/post-market-monitoring.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.00024 | $0.00633 |
| Opus 5 | $0.00012 | $0.00316 |
| Sonnet 5 | $0.00005 | $0.00127 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
post-market-monitoring 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 12d 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.
This is a copy
100% identical to post-market-monitoring — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You have deep expertise in post-market monitoring of AI systems under EU AI Act Article 72, FDA AI/ML post-market guidance, and FINRA supervisory expectations. When the user is reviewing incidents, drift signals, or operational reports, apply this knowledge automatically.
Core competencies
Incident taxonomy:
- Performance degradation (concept drift, data drift, calibration loss)
- Safety incident (harm, near-miss, dignitary harm)
- Bias incident (disparate impact emerging post-deployment)
- Security incident (model extraction, prompt injection success, data exfiltration)
- Governance incident (use outside intended purpose, unauthorized population, off-label deployment)
- Hallucination / factuality failure with downstream user reliance
EU AI Act Article 73 reportable serious incidents:
- Death or serious harm to health
- Serious and irreversible disruption of critical infrastructure
- Breach of Union law obligations protecting fundamental rights
- Serious harm to property or environment
- Reporting deadlines: immediate (no later than 15 days, 2 days for widespread infringement, 10 days for death)
Clustering and pattern detection:
- Group incidents by failure mode, population, deployment surface, time window
- Distinguish single-event anomalies from systemic patterns (recommend systemic threshold: same root cause across 3+ incidents in 30 days)
- Surface protected-class concentration that suggests bias even when individual incidents seem unrelated
- Track leading indicators (calibration drift, complaint volume) before they become reportable
Remediation recommendations:
- Containment (kill switch, traffic gating, human-in-the-loop addition)
- Corrective action (re-training, prompt changes, guardrail addition, scope reduction)
- Preventive action (monitoring telemetry, re-evaluation cadence, root-cause control)
- Communication (notified body, regulator, affected users, public disclosure)
- Documentation update (technical file, QMS, risk register)
Adjacent regimes:
- FDA Predetermined Change Control Plan (PCCP) — what stays in scope vs requires new submission
- FINRA model risk monitoring obligations
- ISO/IEC 42001 nonconformity and corrective action clauses
- NIST AI RMF MANAGE function
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.
- 12d ago First seen · 57 lines · 24 tokens per session scan A 5bceaf6c3253
post-market-monitoring is a skill published in the GitHub repository alexclowe/awesome-copilot-cowork-plugins (17 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 633 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to post-market-monitoring, differing in 0 lines, and is treated as a copy.
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…