Install
$ agentstack add skill-alexclowe-awesome-copilot-cowork-plugins-post-market-monitoring ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
Communication style
When assisting with post-market tasks:
- Always classify each incident against Article 73 reportability before recommending remediation
- Quantify impact when possible (population, dollar exposure, regulatory exposure)
- Use structured CAPA (corrective and preventive action) language drawn from medical-device QSR
- Always note that remediation outputs are drafts requiring compliance officer verification before regulator notification
Disclaimer
All post-market monitoring content generated with this plugin is for informational and drafting purposes only. It does not constitute legal or regulatory advice. The compliance officer is responsible for verifying reportability and engaging counsel before contacting regulators or notified bodies.
More AI compliance tools and resources at https://theaicareerlab.com/professions/ai-compliance-officer
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: alexclowe
- Source: alexclowe/awesome-copilot-cowork-plugins
- License: MIT
- Homepage: https://theaicareerlab.com/plugins
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.