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 landscape-jiragit 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/landscape-jira)<a href="https://agentmods.dev/skills/canonical/copilot-collections/landscape-jira"><img src="https://agentmods.dev/badge/skills/canonical/copilot-collections/landscape-jira/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/landscape-jira"><img src="https://agentmods.dev/badge/skills/canonical/copilot-collections/landscape-jira.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.00055 | $0.01680 |
| Opus 5 | $0.00028 | $0.00840 |
| Sonnet 5 | $0.00011 | $0.00336 |
| Haiku 4.5 | $0.00006 | $0.00168 |
Grade A, and why
landscape-jira 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 10d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud ID
Always pass warthogs.atlassian.net as cloudId to every Atlassian MCP tool call.
Issue Type IDs (LNDENG)
| Type | ID | Hierarchy level | Notes |
|---|---|---|---|
| Theme | 10386 |
3 | Strategic, 1–3 year horizon |
| Objective | 10390 |
2 | OKR-level |
| Epic | 10000 |
1 | Must be broken into stories |
| Project-Risk | 12391 |
1 | Risk tracking |
| Project-Issue | 12392 |
1 | Materialized risks / blockers |
| Story | 10002 |
0 | Default work item |
| Task | 10013 |
0 | Small, distinct piece of work |
| Spike | 10037 |
0 | Research / investigation / prototyping |
| Bug | 10015 |
0 | Problem or error |
| Sub-task | 10014 |
-1 | Part of a parent task |
Pass as: "issuetype": {"id": "<id>"}.
Typical hierarchy: Theme → Objective → Epic → Story/Task/Spike/Bug → Sub-task
Key Fields
| Field | Field ID | Notes |
|---|---|---|
| Summary | summary |
Required |
| Description | description |
ADF format for API v3 |
| Acceptance Criteria | customfield_10614 |
ADF format — NOT a plain string. Required for Epics/Objectives, recommended for Stories. See format below. |
| Story Points | customfield_10024 |
Number. Do NOT use customfield_10016 (legacy read-only) |
| Sprint | customfield_10020 |
Numeric sprint ID — plain integer, not an object. Not applicable to Epics/Objectives/Themes. |
| Assignee | assignee |
{"accountId": "..."} |
| Parent | parent |
{"key": "LNDENG-XXXX"} — any parent issue type |
| Issue Type | issuetype |
{"id": "<id>"} — see table above |
| Labels | labels |
Array of strings |
Finding the Current Sprint ID
Never hardcode sprint IDs — they change every two weeks. Always look up the active sprint at call time:
project = LNDENG AND sprint in openSprints() ORDER BY created DESC
Read customfield_10020[0].id from any result. That integer is the sprint ID to pass.
For the next/upcoming sprint use sprint in futureSprints() instead.
Acceptance Criteria — ADF Format
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.
- 10d ago First seen · 155 lines · 55 tokens per session scan A 562e86be6f4d
landscape-jira is a skill published in the GitHub repository canonical/copilot-collections (29 stars, last pushed 7d ago), licensed Apache-2.0. It adds 55 tokens to every session and 1,680 once invoked, about $0.0003 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
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.
backstage-scaffolder
Author Backstage Software Templates and custom scaffolder actions — parameters, pickers, steps, outputs, action backend modules, dry runs, permissions, and failed or stuck tasks.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.