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 generate-repo-instructionsgit 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/generate-repo-instructions)<a href="https://agentmods.dev/skills/canonical/copilot-collections/generate-repo-instructions"><img src="https://agentmods.dev/badge/skills/canonical/copilot-collections/generate-repo-instructions/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/generate-repo-instructions"><img src="https://agentmods.dev/badge/skills/canonical/copilot-collections/generate-repo-instructions.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.00082 | $0.02416 |
| Opus 5 | $0.00041 | $0.01208 |
| Sonnet 5 | $0.00016 | $0.00483 |
| Haiku 4.5 | $0.00008 | $0.00242 |
Grade A, and why
generate-repo-instructions 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Instructions Generator
Overview
This skill generates the global .github/copilot-instructions.md file through comprehensive LLM-driven repository analysis. It autonomously discovers project characteristics, then populates a constitutional template with discovered values.
Works for all repository types:
- Code repositories: Tech stack, build systems, coding conventions
- Documentation repositories: Doc generators, writing style, content structure
- Data repositories: Schemas, pipelines, quality standards
- Mixed repositories: Adapts to whatever it finds
Key principle: Leverage LLM strengths for analysis and synthesis rather than rigid scripts.
Workflow
Step 1: Intent Validation
Confirm the user wants to create the global .github/copilot-instructions.md file.
Decision tree:
- User wants global instructions? → Continue to Step 2
- User wants path-specific instructions (e.g., "only for src/components/")?
- → STOP. Redirect them to use
generate-path-instructionsskill instead - Explain: Path instructions use
applyToglob patterns for targeted loading
- → STOP. Redirect them to use
- User wants a custom agent or skill?
- → STOP. Clarify asset type using Asset Decision Matrix
- Agent = role-based, Skill = capability-based
Proceed only if creating global instructions.
Step 2: Comprehensive Repository Analysis
Perform deep codebase discovery following the checklist in references/analysis_checklist.md.
Load the analysis checklist:
cat references/analysis_checklist.md
Work through all 7 phases systematically:
- Documentation Discovery - README, CONTRIBUTING, ARCHITECTURE docs
- Tech Stack Detection - Languages, frameworks, package managers
- Build System Discovery - Build/test/lint commands
- Code Pattern Analysis - Indentation, formatting, async patterns
- Project Structure Mapping - Directory purposes
- Configuration Files - .env, .editorconfig, git configs
- Security & Quality - Secret scanning, quality tools
What ships with it
4 files 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.
- 12d ago First seen · 297 lines · 82 tokens per session scan A 50944365958e
generate-repo-instructions is a skill published in the GitHub repository canonical/copilot-collections (29 stars, last pushed 9d ago), licensed Apache-2.0. It adds 82 tokens to every session and 2,416 once invoked, about $0.0004 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.