cdn-cache-purge-tests SKILL.md skillA
cdn-cache-purge-tests 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/cdn-cache-purge-tests@git:20260813.2e5e33bPins git:20260813.2e5e33b 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-cache-testing/skills/cdn-cache-purge-tests/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260813.2e5e33b, committed Aug 13, 2026
- First version recorded
- Jun 15, 2026
- Size
- 9,668 bytes
- Repository stars
- 11
- License
- MIT
Wraps CDN cache-purge testing patterns for Cloudflare (POST /zones/{zone_id}/purge_cache, single-file / everything / cache-tags / hostname / prefix), Fastly (POST purge-by-key / purge-all, surrogate-keys via Surrogate-Key header), and CloudFront (CreateInvalidation API + paths). Covers end-to-end test patterns (write origin → trigger purge → assert edge serves fresh), purge-propagation delay testing (typically 1-30s globally), surrogate-key + cache-tag patterns for group-purge, and…
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
# cdn-cache-purge-tests
## Overview
CDN cache-purge tests verify that the
write-origin-then-invalidate-edge sequence works end-to-end -
the most-likely-broken cache integration in real deployments.
Per
[developers.cloudflare.com/cache/how-to/purge-cache/](https://developers.cloudflare.com/cache/how-to/purge-cache/),
Cloudflare offers five purge methods (Single-file, Everything,
Cache-tags, Hostname, Prefix). Fastly's surrogate-key pattern
and CloudFront's invalidation API offer similar shapes.
## When to use
- Verifying a new purge integration works end-to-end.
- Regression-testing the write-origin-then-purge sequence.
- Auditing existing purge logic before a deploy.
- Investigating "users see stale content after a write."
## Authoring
### Cloudflare - purge by URL
```bash
curl -X POST \
"https://api.cloudflare.com/client/v4/zones/${ZONE_ID}/purge_cache" \
-H "Authorization: Bearer ${CF_API_TOKEN}" \
-H "Content-Type: application/json" \
--data '{"files":["https://example.com/api/users/1"]}'
```
Response:
```json
{ "success": true, "result": { "id": "...." } }
```
### Cloudflare - purge by cache-tag (Enterprise)
```bash
…Read the whole file at its exact version.
How to install
mdr add testland/qa/cdn-cache-purge-tests@sha256:7e52ba4ffc7b479bThe line at the top of this page pins the label git:20260813.2e5e33b, 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_4gu266lq5r56dsp4)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 15, 2026 and Aug 13, 2026, about one every 15 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260813.2e5e33b latest | 2026-08-13 | 2e5e33b | 9,668 B | A | view · diff |
| git:20260724.d4db756 | 2026-07-24 | d4db756 | 8,395 B | A | view · diff |
| git:20260706.d9cec5f | 2026-07-06 | d9cec5f | 8,651 B | A | view · diff |
| git:20260706.4e1409c | 2026-07-06 | 4e1409c | 8,653 B | A | view · diff |
| git:20260615.c62f985 | 2026-06-15 | c62f985 | 8,670 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 (9668 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_4gu266lq5r56dsp4 GET https://markdownregistry.com/api/v1/resolve?ref=testland/qa/cdn-cache-purge-tests GET https://markdownregistry.com/api/v1/blob/7e52ba4ffc7b479bb7ded77416cdedfeab1cbdc51c5baeb4a5ef6cda1a377d40
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.