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 configure-gh-jira-sync-botgit 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/configure-gh-jira-sync-bot)<a href="https://agentmods.dev/skills/canonical/copilot-collections/configure-gh-jira-sync-bot"><img src="https://agentmods.dev/badge/skills/canonical/copilot-collections/configure-gh-jira-sync-bot/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/configure-gh-jira-sync-bot"><img src="https://agentmods.dev/badge/skills/canonical/copilot-collections/configure-gh-jira-sync-bot.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.00071 | $0.00615 |
| Opus 5.5 | $0.00028 | $0.00246 |
| Sonnet 5.5 | $0.00014 | $0.00123 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
configure-gh-jira-sync-bot 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 yesterday.
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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure gh-jira-sync-bot
Reference: https://github.com/canonical/gh-jira-sync-bot and canonical/platform-engineering-charm-template#165.
Workflow
-
Check whether
.github/.jira_sync_config.yamlexists. If so, keep user-specific values (project key, mappings) and only align it with the template. -
Copy
assets/jira_sync_config.template.yamlto.github/.jira_sync_config.yamlwhen missing. -
Ask the user which Jira component(s) the repository belongs to and set
settings.components(a list, case-sensitive names). Valid names are listed inVALID_COMPONENTSofscripts/validate_config.py. Changejira_project_keyonly if the project is notISD. -
Validate:
uv run scripts/validate_config.py .github/.jira_sync_config.yamlOr, without a local copy of the skill:
uvx --from "git+https://github.com/canonical/copilot-collections#subdirectory=groups/platform-engineering/skills/configure-gh-jira-sync-bot" validate-jira-sync-config .github/.jira_sync_config.yamlFix every reported error and re-run until it prints
OK. -
Remind the user that the GitHub App of the bot must be installed on the repository.
Template conventions
- Keep the 3-line
# template-versionheader; removing it opts the file out of template propagation. labels: [bug, enhancement]prevents "Dependency dashboard" issues from being synced.label_mapping:bug: Bug,enhancement: Story.- No
epic_key. add_gh_comment: true.
Mandatory fields (checked by the validator)
settings.jira_project_key, settings.status_mapping.opened, settings.status_mapping.closed,
a non-empty settings.components list of known Jira components, and settings.labels containing bug and enhancement. settings.epic_key must not be defined. Every template in .github/ISSUE_TEMPLATE/ (next to the config) must have a labels key containing bug or enhancement.
Refreshing the component list
Jira has no component listing through the Atlassian MCP server. Query
project = ISD AND component is not EMPTY with fields: ["components"] and update VALID_COMPONENTS.
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.
- yesterday First seen · 51 lines · 71 tokens per session scan A fc73e632c662
configure-gh-jira-sync-bot is a skill published in the GitHub repository canonical/copilot-collections (31 stars, last pushed 2d ago), licensed Apache-2.0. It adds 71 tokens to every session and 615 once invoked, about $0.0003 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-10-15.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
cuga-github-issues
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…
implement-issue
Implement a Linear brief in a named GitHub repo. Use when the brief skill is implement-issue or the user wants a new branch and draft PR.