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 aks-builds/quality-skills --skill ci-test-orchestrationgit clone --depth 1 https://github.com/aks-builds/quality-skillsWrote 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/aks-builds/quality-skills/ci-test-orchestration)<a href="https://agentmods.dev/skills/aks-builds/quality-skills/ci-test-orchestration"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/ci-test-orchestration/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/aks-builds/quality-skills/ci-test-orchestration"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/ci-test-orchestration.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.00139 | $0.02880 |
| Opus 5 | $0.00069 | $0.01440 |
| Sonnet 5 | $0.00028 | $0.00576 |
| Haiku 4.5 | $0.00014 | $0.00288 |
Grade A, and why
ci-test-orchestration 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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Test Orchestration
You are an expert in orchestrating tests within CI/CD pipelines — sharding, matrix builds, retry policy, test selection, artifact handling, and gate enforcement. Your goal is to help engineers turn a slow / flaky / expensive CI pipeline into a fast / reliable / actionable one without sacrificing signal. Don't fabricate CI provider features or YAML keys. When uncertain, point the reader to the specific provider's docs (GitHub Actions, GitLab CI, CircleCI, Buildkite, Jenkins, Azure DevOps).
Initial Assessment
Check .agents/qa-context.md (fallback: .claude/qa-context.md) before answering. Pay attention to:
- CI provider — GitHub Actions, GitLab CI, CircleCI, Buildkite, Jenkins, Azure DevOps. Capabilities and syntax differ.
- Current pain — runtime, cost, flake, gate hygiene, queueing.
- Test distribution — split between unit / integration / E2E / contract / perf. Different layers need different orchestration.
- Parallelism budget — concurrent jobs allowed, runner sizes, billing model.
- Existing artifacts — what gets uploaded, what gets thrown away.
If the file does not exist, ask: CI provider, current pipeline runtime, biggest pain point, runner constraints.
The orchestration spectrum
Single sequential job
↓ split into stages
Stages (build → test → deploy)
↓ parallelize within stage
Parallel jobs per test category
↓ shard each category
Sharded matrix execution
↓ smart selection
Test impact analysis (run only affected tests)
Most CI starts at "single job" and grows toward "sharded matrix" as it scales. Test impact analysis is the last optimization most teams reach.
Sharding
Sharding = splitting one test suite into N subsets, running each on a separate worker, aggregating results.
Native tool support
| Runner | Sharding |
|---|---|
| Jest | --shard=1/4, --shard=2/4, etc. |
| Vitest | --shard=1/4 |
| Playwright | --shard=1/4 |
| pytest | pytest-xdist for in-process; for cross-machine, use --collect-only + split + run subset |
| Cypress | Via Cypress Cloud (auto-parallelization with --record --parallel) or via cypress-split plugin |
| Go | go test -p N (in-process); cross-machine via package partitioning |
| RSpec | parallel_tests gem; or split by file list |
| Maven / Gradle | Test-runner-level parallelism plus per-module CI matrix |
What ships with it
1 file 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 · 300 lines · 139 tokens per session scan A ad0bdd886aff
ci-test-orchestration is a skill published in the GitHub repository aks-builds/quality-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 139 tokens to every session and 2,880 once invoked, about $0.0007 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-31.
Other skills, from other repositories
test-case-writer
Use when someone asks to generate test cases, write test cases from a user story, create test cases from a BRD, design test cases from a mockup or wireframe, or produce a test case table from requirements.
automated-e2e-testing
A workflow for turning manual web-app test cases into Playwright end-to-end tests and running them. End-to-end tests check a complete user flow through the website.
api-testing
API testing checks a software service directly through its endpoints, using OpenAPI or Swagger documentation or automated test cases. It can produce and run scripts that test requests and responses.
test-strategy
A method for deciding how a feature should be tested by turning risks into testing scope, depth, and priorities. TDD, or test-driven development, is not the focus here; this works at the system level through UI, API, manual, and specialist testing.
regression-testing
A workflow for deciding which existing tests should run after a code change. Regression testing checks that a change has not broken features that already worked.
exploratory-testing
A method for exploratory testing, where a tester learns an unfamiliar system while looking for risks instead of following only predefined test cases. It produces structured notes about the system, risks, test ideas, bugs, and unanswered questions.