manifest-v3-test-surface-reference SKILL.md skillB
manifest-v3-test-surface-reference 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/manifest-v3-test-surface-reference@v1.2.9Pins v1.2.9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- testland/qa
- Path
plugins/qa-browser-extension/skills/manifest-v3-test-surface-reference/SKILL.md- Versions recorded
- 5
- Latest version
- v1.2.9, committed Oct 11, 2026
- First version recorded
- Jul 24, 2026
- Size
- 10,863 bytes
- Repository stars
- 11
- License
- MIT
Pure-reference catalog of the Manifest V3 test surface for Firefox + Chromium browser extensions. Maps each manifest field that changed from MV2 (manifest_version, background.service_worker vs background.scripts, action vs browser_action / page_action, host_permissions split, web_accessible_resources object-form, content_security_policy object-form), the runtime restrictions service workers impose (no DOM, no XMLHttpRequest, no localStorage, ephemeral lifecycle, synchronous listener…
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
# manifest-v3-test-surface-reference ## Overview Manifest V3 (MV3) is the current packaging contract for Chromium-family browser extensions; Firefox supports it as a peer with a documented divergence list. The manifest is the *only* declarative input both browsers see - every test surface (background lifecycle, permission prompt, content-script injection, web-accessible-resource fetch) hangs off a manifest field. Knowing which field maps to which runtime behaviour is what lets a test author decide whether a behaviour is testable in unit, integration, or full-browser scope. This skill is the **pure reference** consumed by `playwright-extension-fixtures` (and its reload-matrix / storage-tests references). The summary tables below are the quick lookup; exact MV2/MV3 field shapes, the full Firefox/Chrome key matrix, and the offscreen-document + keep-alive detail live in [references/manifest-matrix.md](references/manifest-matrix.md); Mozilla's `web-ext` CLI (Firefox lint / run / build / sign) lives in [references/web-ext-firefox.md](references/web-ext-firefox.md). All sources are consolidated in the References section. For Playwright-driven MV3 popup / content-script fixtures and …
Read the whole file at its exact version.
How to install
mdr add testland/qa/manifest-v3-test-surface-reference@sha256:8703b2c5bdcf3500The line at the top of this page pins the label v1.2.9, 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_kpty7gvbkfsbqt35)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 24, 2026 and Oct 11, 2026, about one every 20 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.2.9 latest | 2026-10-11 | a1bd3f7 | 10,863 B | B | view · diff |
| git:20260813.e6bcb77 | 2026-08-13 | e6bcb77 | 10,844 B | B | view · diff |
| git:20260813.84b37f4 | 2026-08-13 | 84b37f4 | 10,833 B | B | view · diff |
| git:20260728.1bce424 | 2026-07-28 | 1bce424 | 10,513 B | B | view · diff |
| git:20260724.d4db756 | 2026-07-24 | d4db756 | 15,287 B | B | view |
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10863 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
testland/qa · 11 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kpty7gvbkfsbqt35 GET https://markdownregistry.com/api/v1/resolve?ref=testland/qa/manifest-v3-test-surface-reference GET https://markdownregistry.com/api/v1/blob/8703b2c5bdcf350049f0443d0cd4f4225ea8ccd707874e376bc3cad8f006fc9f
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.