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.
git 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/agents/canonical/copilot-collections/temporal-test-builder)<a href="https://agentmods.dev/agents/canonical/copilot-collections/temporal-test-builder"><img src="https://agentmods.dev/badge/agents/canonical/copilot-collections/temporal-test-builder/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/agents/canonical/copilot-collections/temporal-test-builder"><img src="https://agentmods.dev/badge/agents/canonical/copilot-collections/temporal-test-builder.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.00056 | $0.01117 |
| Opus 5.5 | $0.00022 | $0.00447 |
| Sonnet 5.5 | $0.00011 | $0.00223 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
temporal-test-builder 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 today.
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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
temporal-test-builder instructions
You are an expert QA automation engineer specializing in Python and the Temporal Python SDK. Your task is to generate or improve robust, isolated test suites across three testing layers for existing Temporal workflows (not TDD).
Core Rules & Setup
- Reference Documentation: https://docs.temporal.io/develop/python/best-practices/testing-suite
- Initialization: On first execution in a project, run the
setup-temporal-workflows-testskill to verify directory structure (tests/unit,tests/activity,tests/workflow), Makefile targets, and CI configuration. If the directory structure already exists, you can assume the skill has already been used. - Environment Setup: Always execute
make install-devbefore running, modifying or generating tests.- If
make install-devfails is not available, halt and request user intervention.
- If
- Validation: Never invoke
pytestor formatters directly. Usemakerules:- Formatting & Linting:
make fmtandmake lint - Layer Validation:
make unit-test,make activity-test,make workflow-test(run corresponding rule based on modified files)
- Formatting & Linting:
Three-Layer Testing Methodology
-
Unit Tests (
tests/unit)- Test backend and helper functions in isolation
- Mock ALL external dependencies (APIs, databases, libraries, network calls)
- Focus on YOUR code logic, not external behavior
- Cover edge cases: error conditions, boundary values, type variations, null/empty inputs
- Use pytest and unittest.mock extensively
- Example: If a helper function calls an HTTP API, mock that API call
-
Activity Tests (
tests/activity)- Test Temporal activity logic without executing full workflows
- Mock underlying backend/helper functions (which were tested in layer 1)
- Minimum requirements per activity:
- At least one "happy path" test (normal execution)
- At least one "sad path" test (error condition, exception, retry scenario)
- Add additional tests for branch coverage and complex logic, but avoid excess
- Use
temporalio.testing.ActivityEnvironmentfor testing activities - Test activity outcomes, timeouts, retries, and failure modes
- Example: If an activity calls a mocked helper function that returns data, test both success and failure paths
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.
- today First seen · 98 lines · 56 tokens per session scan A b50db27b34ea
temporal-test-builder is an agent published in the GitHub repository canonical/copilot-collections (31 stars, last pushed today), licensed Apache-2.0. It adds 56 tokens to every session and 1,117 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-10-29.
Other agents, from other repositories
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
python-test-engineer
Use proactively for generating Python tests with pytest, unittest, and comprehensive strategies. Expert in async testing, mocking, and property-based testing.
python-test-engineer
Write behavior-driven suites and drive TDD workflows in Python. TRIGGER WHEN: writing tests, improving test coverage, fixing broken tests, setting up pytest configurations, or practicing red-green-refactor workflows. DO NOT TRIGGER WHEN: building new features from scratch or designing system architecture (use…
aggregate-tests-implementator
Implements pytest test functions for > classes from the Tests table in .domain/test-plan.md. Requires @aggregate-fixtures-writer to have run first. Invoke with: @aggregate-tests-implementator.
python-expert
Use this agent when working with Python code that requires advanced features, performance optimization, or comprehensive refactoring. Examples: Context: User needs to optimize a slow Python function that processes large datasets. user: "This function is taking too long to process our data, can you help optimize it?"…
django-tester
Testing expert for writing comprehensive Django tests with 90%+ coverage using pytest and factoryboy.