pact-contract-testing SKILL.md skillA
pact-contract-testing from testland/qa is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add testland/qa/pact-contract-testing@git:20260728.1bce424Pins git:20260728.1bce424 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- testland/qa
- Path
plugins/qa-contract-testing/skills/pact-contract-testing/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260728.1bce424, committed Jul 28, 2026
- First version recorded
- Jun 2, 2026
- Size
- 8,078 bytes
- Repository stars
- 11
- License
- MIT
Authors and verifies Pact consumer-driven contract tests across the full Pact lifecycle - consumer tests producing pact files, publishing to the Pact Broker, provider verification, and `can-i-deploy` deployment gates. Use when introducing a new HTTP/JSON API contract between two services, diagnosing breaking changes, or wiring contract verification into CI.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# pact-contract-testing ## Overview Pact is a code-first tool for **consumer-driven contract tests** over HTTP and message integrations ([pact-overview][overview]). The contract is a side-effect of the consumer's tests - each test documents one request/response pair, and only the parts the consumer actually uses get tested. [overview]: https://docs.pact.io/ The lifecycle has five steps ([pact-how-it-works][how]): 1. **Consumer test** runs against a Pact mock server using the Pact DSL. 2. The framework writes a **pact file** (JSON) capturing every `given() → uponReceiving() → withRequest() → willRespondWith()` interaction. 3. The pact file is **published to the Pact Broker**. 4. The **provider verifies** the pact: each recorded request is replayed against the running provider and responses are checked against the contract. 5. **`can-i-deploy`** queries the Broker matrix to confirm the candidate version has a green verification against every consumer/provider already deployed in the target environment ([can-i-deploy][cid]). [how]: https://docs.pact.io/getting_started/how_pact_works [cid]: https://docs.pact.io/pact_broker/can_i_deploy …
Read the whole file at its exact version.
How to install
mdr add testland/qa/pact-contract-testing@sha256:9991ad2ee9475289The line at the top of this page pins the label git:20260728.1bce424, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_pskblqq2o6kq6g3v)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 2, 2026 and Jul 28, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260728.1bce424 latest | 2026-07-28 | 1bce424 | 8,078 B | A | view · diff |
| git:20260724.d4db756 | 2026-07-24 | d4db756 | 9,661 B | A | view · diff |
| git:20260706.4e1409c | 2026-07-06 | 4e1409c | 9,698 B | A | view · diff |
| git:20260603.21eda0e | 2026-06-03 | 21eda0e | 9,715 B | A | view · diff |
| git:20260602.ce520f0 | 2026-06-02 | ce520f0 | 9,729 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8078 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
testland/qa · 11 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pskblqq2o6kq6g3v GET https://markdownregistry.com/api/v1/resolve?ref=testland/qa/pact-contract-testing GET https://markdownregistry.com/api/v1/blob/9991ad2ee947528968a965870c0f7293aeaf97b5a62511cda11938e2189da9ab
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.