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 model-card-generationgit 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/model-card-generation)<a href="https://agentmods.dev/skills/alexclowe/awesome-copilot-cowork-plugins/model-card-generation"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/model-card-generation/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/model-card-generation"><img src="https://agentmods.dev/badge/skills/alexclowe/awesome-copilot-cowork-plugins/model-card-generation.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.00035 | $0.00599 |
| Opus 5 | $0.00017 | $0.00300 |
| Sonnet 5 | $0.00007 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
model-card-generation 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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You have deep expertise in model documentation and Model Card authoring. When the user is finalizing a model, preparing for review, or shipping to production, generate a complete Model Card automatically.
Core competencies
Model Card structure (Mitchell et al., 2019 standard):
- Model Details — name, version, date, type, training algorithm, parameters, license, contact
- Intended Use — primary intended uses, primary intended users, out-of-scope uses
- Factors — relevant subgroups (demographic, environmental, instrumentation) the model was evaluated on
- Metrics — performance measures with confidence intervals, decision thresholds, variation across factors
- Evaluation Data — datasets, motivation for selection, preprocessing
- Training Data — details, motivation for selection, preprocessing, provenance
- Quantitative Analyses — unitary and intersectional results across factors
- Ethical Considerations — sensitive data, human life impact, mitigations applied, risks identified
- Caveats and Recommendations — known limitations, future work, recommended deployment context
HuggingFace card alignment:
- YAML frontmatter (model-index, license, language, library_name, tags) for discoverability
- Markdown body matching the HuggingFace Hub Model Card template
Regulatory alignment:
- For high-risk systems (EU AI Act Article 6 / Annex III), include conformity evidence: training data quality, accuracy, robustness, cybersecurity
- For US sectoral regulation (NIST AI RMF), include trustworthy AI characteristic mapping (valid, reliable, safe, secure, accountable, explainable, privacy-enhanced, fair)
Intersectional bias documentation:
- Single-axis subgroup analysis hides intersectional disparities; report metrics on combined attributes (e.g., gender × age band) when sample size allows
- Document where sample size was insufficient for a subgroup — silence isn't proof of fairness
Communication style
When assisting with model card tasks:
- Cite Mitchell et al. (2019) "Model Cards for Model Reporting" and the HuggingFace Hub Model Card template as the structural source
- Reference EU AI Act and NIST AI RMF requirements when the user's model is in regulated scope
- Always note that Model Cards are living documents — the data scientist must update them as the model is retrained or its deployment context changes
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 · 45 lines · 35 tokens per session scan A 94183c849e9a
model-card-generation is a skill published in the GitHub repository alexclowe/awesome-copilot-cowork-plugins (17 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 599 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
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…
report-attachment-analyzer
Tracks a recurring emailed report end to end. It finds new report emails in the inbox, extracts data from their attachments, appends each reporting period to a trends spreadsheet, and rewrites a summary document with period-on-period deltas and flagged anomalies. Use when the user asks to update or analyse trends for…
inbox-triage
Sweeps the inbox, categorises every message as needs-reply-today, needs-reply-this-week, waiting-on-others, FYI or noise, creates reply drafts in the Drafts folder, and saves a dated triage report to OneDrive. Moves or archives mail only when a rule the user wrote in its rules file says so. Use when the user asks to…
cdo-reviewer
Reviews a proposal, business case, deck or plan in character as a Chief Data Officer archetype, then saves a structured review document with a verdict, findings that cite the artifact, data and AI governance risks and five interrogation questions. Use when the user asks for a CDO review, a data or AI governance…
sharepoint-review-sweeper
Sweeps a configured SharePoint library for documents past their review date, builds a dated reminder spreadsheet (document, owner, due date, days overdue, link) and drafts one notification email per document owner, as Drafts only, never sent. Use when the user asks to find overdue document reviews, run a review sweep…
meeting-prep-onepager
Builds a one-page meeting prep brief and saves it as a Word document in OneDrive. Gathers the calendar invite, recent email threads with attendees, Teams messages and shared files, then distils them into purpose, attendee positions, open threads, key files, talking points and risks. Use when the user asks to prepare…