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 documentation-diataxisgit 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/documentation-diataxis)<a href="https://agentmods.dev/skills/canonical/copilot-collections/documentation-diataxis"><img src="https://agentmods.dev/badge/skills/canonical/copilot-collections/documentation-diataxis/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/documentation-diataxis"><img src="https://agentmods.dev/badge/skills/canonical/copilot-collections/documentation-diataxis.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.00046 | $0.01276 |
| Opus 5.5 | $0.00018 | $0.00510 |
| Sonnet 5.5 | $0.00009 | $0.00255 |
| Haiku 4.5 | $0.00005 | $0.00128 |
Grade A, and why
documentation-diataxis 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 1mo 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diataxis Classification Review
Scope
Diataxis classification only: identify whether each page is a tutorial, how-to guide, explanation, or reference; note structural mismatches between content type and declared category, and suggest improvements where real issues exist. Ground classification in the Diataxis foundations: the two axes of craft (action vs cognition, acquisition vs application) define four user needs (learning, goals, information, understanding).
This skill identifies flaws and provides actionable recommendations; it does not enforce compliance or apply pass/fail criteria.
Inputs
- Documentation file(s) under review.
- Diataxis framework principles (embedded in classification criteria below).
Actions
-
Identify intended category: Determine the declared category based on directory location (
tutorial/,how-to/,explanation/,reference/) and file metadata (front matter keys such ascategory,type,diataxis, or reST.. meta::entries). -
Infer actual category: Analyse the text's structure, tone, and progression to determine which quadrant it actually resembles. Use these classification criteria:
-
Tutorial indicators:
- Step-by-step progression building a complete project
- Imperative mood ("Create a file", "Run this command")
- Learning-focused language ("you will learn", "by the end")
- Safe, controlled environment (specific versions, no branching)
- Frequent reassurance and checkpoints
- Teaches by doing, not explaining
-
How-to guide indicators:
- Problem-solution format with clear goal
- Assumes existing knowledge and competence
- Clearly states prerequisites and applicability scope
- Action-oriented ("To achieve X, do Y")
- Flexible, allows for variation
- Focuses on results, not learning
- Omits explanations unless critical to success
-
Reference indicators:
- Descriptive, declarative statements
- Comprehensive coverage of subject
- Neutral, technical tone
- Structured for lookup (tables, lists, alphabetical)
- Parameters, options, API signatures
- Accuracy over narrative
-
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.
- 1mo ago First seen · 153 lines · 46 tokens per session scan A 331716ee5d24
documentation-diataxis is a skill published in the GitHub repository canonical/copilot-collections (31 stars, last pushed 7d ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,276 once invoked, about $0.0002 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-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.
oncall-handoff
Generate a comprehensive on-call handoff document by aggregating open incidents, ongoing issues, recent deployments, and systems to watch. Orchestrates Splunk On-Call (VictorOps), Jira, and ArgoCD agents. Use during on-call rotation changes or shift handoffs.
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.