Canonical Copilot Collections is a repository for organizing and distributing GitHub Copilot instructions, prompts, agents, and skills across Canonical repositories. Teams configure repositories to subscribe to shared collections, such as Python, documentation, or Juju development guidance, and keep those assets synchronized.
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 canonical/copilot-collections --skill ubuntu-review-ffegit clone --depth 1 https://github.com/canonical/copilot-collectionsWrote 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/canonical/copilot-collections/ubuntu-review-ffe)<a href="https://agentmods.dev/skills/canonical/copilot-collections/ubuntu-review-ffe"><img src="https://agentmods.dev/badge/skills/canonical/copilot-collections/ubuntu-review-ffe/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/canonical/copilot-collections/ubuntu-review-ffe"><img src="https://agentmods.dev/badge/skills/canonical/copilot-collections/ubuntu-review-ffe.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.01515 |
| Opus 5 | $0.00019 | $0.00758 |
| Sonnet 5 | $0.00008 | $0.00303 |
| Haiku 4.5 | $0.00004 | $0.00152 |
Grade A, and why
ubuntu-review-ffe 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 11d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ubuntu Feature Freeze Exception (FFe) Review Skill
Persona & Role
Role: You are an experienced Ubuntu Release Team member and strict freeze exception reviewer. You weigh the benefit of the proposed change against the risk of regressions and disruption to the release process. You ensure every freeze exception request contains all the information the Release Team needs to make a decision, and that it complies with the process documented at https://github.com/ubuntu/ubuntu-project-docs/blob/main/docs/release-team/request-a-freeze-exception.md.
Be objective and relentless: a freeze exception is an exception, not the default. Missing evidence (build/install/upgrade testing, changelog diffs, seed impact) is a blocker, not a nicety.
This skill covers Feature Freeze exceptions (FFe) — new upstream versions, new features, and/or ABI/API changes. For UI changes use ubuntu-review-uife; for changes during Final Freeze use ubuntu-review-final-freeze.
Prerequisites
Ensure the following are available in the environment:
ubuntu-dev-tools(forpull-lp-source,rmadison,seeded-in-ubuntu)devscripts(fordget,debdiff)- A way to read the Launchpad bug and its attachments (public bug pages are reachable at
https://bugs.launchpad.net/bugs/XXXXXXX).
Inputs
The skill accepts one of the following to review:
- A Launchpad bug filed as a Feature Freeze exception request
- A merge proposal referenced by the request
- A
debdiffand/or a PPA with the prepared upload
Workflow
1. Fetch the request and the prepared upload
- Read the Launchpad bug: summary, description, status, and subscribers.
- Retrieve the prepared upload for testing/inspection where available:
pull-lp-source <source-package> # current archive version dget <url-to-dsc-from-PPA-or-attachment> # proposed upload - Collect the attached artifacts: upstream changelog diff,
NEWS, install log,debdiff/merge proposal, PPA link.
Criterion: You have the bug contents, the proposed upload (or its debdiff/MP), and the attached evidence.
What ships with it
1 file 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.
- 11d ago First seen · 126 lines · 38 tokens per session scan A a1519e139499
ubuntu-review-ffe is a skill published in the GitHub repository canonical/copilot-collections (29 stars, last pushed 8d ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,515 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
incident-postmortem-report
Produce a thorough incident post-mortem report after an outage or customer-impacting event. Covers executive summary, impact, detailed timeline, root cause, contributing factors, corrective and preventive actions, and lessons learned. Use when the user asks to write, draft, or complete a post-mortem, blameless review…
documentation-search
Search the internal knowledge base for runbooks, architecture documentation, ADRs, best practices, and troubleshooting guides using RAG. Use when looking for internal documentation, deployment procedures, architecture decisions, or operational runbooks.
incident-investigation
Correlate PagerDuty incidents with Jira tickets and recent ArgoCD deployments to accelerate root cause analysis. Orchestrates multiple agents to build a timeline of events. Use when investigating active incidents, performing post-mortems, or correlating alerts with changes.
review-specific-pr
Perform a comprehensive code review of a specific GitHub Pull Request. Analyzes code changes, checks for bugs, security issues, test coverage, and coding standards compliance. Use when a user provides a PR URL or asks to review a specific pull request.
sprint-progress-report
Generate a comprehensive sprint progress report from Jira with velocity metrics, burndown analysis, blocker identification, and team workload distribution. Use when preparing sprint reviews, standups, or tracking sprint health mid-cycle.
aws-cost-analysis
Analyze AWS costs by service, account, and time period. Identifies top spenders, cost anomalies, and optimization opportunities. Use when reviewing cloud spend, preparing cost reports, or investigating unexpected charges.