Borrowing it
Nothing to install: this file belongs to Autodesk/claude-browser-test-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Autodesk/claude-browser-test-skills/main/CLAUDE.mdgit clone --depth 1 https://github.com/Autodesk/claude-browser-test-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/instructions/autodesk/claude-browser-test-skills/claude-md)<a href="https://agentmods.dev/instructions/autodesk/claude-browser-test-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/autodesk/claude-browser-test-skills/claude-md/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/instructions/autodesk/claude-browser-test-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/autodesk/claude-browser-test-skills/claude-md.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.00694 | $0.00694 |
| Opus 5 | $0.00347 | $0.00347 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
claude-browser-test-skills CLAUDE.md 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 8d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for working on this repository. For how the skills behave at runtime, read each skills/*/SKILL.md.
What this repo is
A Claude Code plugin named browser-test, distributed through a marketplace (browser-test-skills) defined in the same repo. It provides a four-skill pipeline for authoring, stabilizing, compiling, and running E2E browser tests with Playwright MCP. There is no application code here — the deliverable is the skills themselves plus their manifests.
The pipeline: Author → Refiner → Compiler → Playwright CI, with a Runner for LLM-driven execution of the markdown source. The markdown test case is authoritative; the compiled .spec.ts is a derived artifact.
Layout
.claude-plugin/
marketplace.json # marketplace "browser-test-skills" → plugin "browser-test", source "./"
plugin.json # plugin manifest: name, version, license, metadata
skills/
author/SKILL.md # vague description → structured markdown test case
refiner/SKILL.md # run repeatedly, stabilize flaky steps + conventions
compiler/SKILL.md # stable markdown → Playwright .spec.ts via live browser replay
runner/SKILL.md # execute a stable markdown test faithfully, report pass/fail
.github/CODEOWNERS
docs/superpowers/ # design specs and implementation plans (historical context)
README.md # user-facing docs
Conventions when editing skills
- SKILL.md frontmatter
nameis the bare skill name (name: author), never the plugin-prefixed form. Claude Code adds thebrowser-test:namespace automatically fromplugin.json's plugin name. A prefixed name is a bug. - The
descriptiondrives activation — it is what Claude matches against to decide when to invoke the skill. Keep it specific and trigger-oriented. - Keep examples product-neutral. This is a public, general-purpose repo. Use neutral placeholders (
PROJ-123for Jira keys, generic app/tenant names). Do not reintroduce internal Autodesk product names (Upchain, Fusion, etc.) or real credentials/URLs. - The skills describe conventions-driven test projects, not this repo. When a skill references
tests/e2e/,playwright-tests/,conventions.md, orINVENTORY.md, those live in the consuming project, not here.
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.
- 8d ago First seen · 51 lines · 694 tokens per session scan A 62cffeff106f
claude-browser-test-skills CLAUDE.md is an instructions file published in the GitHub repository Autodesk/claude-browser-test-skills (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 694 tokens to every session, about $0.0035 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.