Borrowing it
Nothing to install: this file belongs to debs-obrien/playwright-movies-app. 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/debs-obrien/playwright-movies-app/main/.agents/skills/learn-dogfood/SKILL.mdgit clone --depth 1 https://github.com/debs-obrien/playwright-movies-appWrote 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/debs-obrien/playwright-movies-app/learn-dogfood)<a href="https://agentmods.dev/skills/debs-obrien/playwright-movies-app/learn-dogfood"><img src="https://agentmods.dev/badge/skills/debs-obrien/playwright-movies-app/learn-dogfood/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/debs-obrien/playwright-movies-app/learn-dogfood"><img src="https://agentmods.dev/badge/skills/debs-obrien/playwright-movies-app/learn-dogfood.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 67 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium MCP Rug Pull · line 49 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 66 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 86 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 87 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 88 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00069 | $0.01114 |
| Opus 5 | $0.00034 | $0.00557 |
| Sonnet 5 | $0.00014 | $0.00223 |
| Haiku 4.5 | $0.00007 | $0.00111 |
Grade A, and why
learn-dogfood 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 13d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Learn dogfood
Maintainer QA for the VitePress course under learn/. Simulate a new learner
and report blockers. Do not coach a human one step at a time — that is
learn-lab-coach.
Sources of truth
- Module pages:
learn/*.mdandlearn/index.md - Setup copy:
learn/00-start-here.md, rootREADME.md - House style:
AGENTS.md,docs/TESTING.md,docs/AI-TESTING.md - Skills for labs:
movies-playwright,playwright-cli,playwright-trace
Do not invent commands, files, or APIs missing from those sources.
Scope
Ask once if unclear. Defaults:
| Scope | Modules |
|---|---|
| beginner (default) | 00 → 04, then foundations smoke, then 05 → 11 if time |
| ai-first | 00 setup, AGENTS.md, 07, 09 |
| module N | 00 setup (if needed) + that module only |
| docs-only | Layer A only |
Continue on failure unless the user says stop-on-fail. Fix nothing unless asked — report only.
Procedure
Layer A — Docs site
From the repo under test (workspace or temp clone):
npm run docs:dev
Open http://127.0.0.1:5173/course (VitePress default). Prefer
npx playwright cli; browser MCP is fine for click-through.
Check:
- Course home loads; beginner / intermediate / AI-first links work.
00→ each in-scope module via in-page Next / agenda links.- CTAs: live Movies demo, clone/GitHub,
/docs/TESTING,/docs/AI-TESTING,/AGENTS. - Note 404s, broken anchors, and copy that contradicts
learn/00-start-here.md.
Layer B — Fresh learner setup
Prefer a clean temp clone so dirty WIP does not hide broken instructions:
git clone https://github.com/debs-obrien/playwright-movies-app.git /tmp/movies-learn-dogfood
cd /tmp/movies-learn-dogfood
npm install
npx playwright install chromium
cp .env.example .env
Run the block from learn/00-start-here.md verbatim when it differs. Record any
step that fails on a clean tree.
If the user asks to dogfood uncommitted learn/ edits, use the workspace (or
a worktree of the current branch) for Layers A–C instead of main on GitHub.
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.
- 13d ago First seen · 114 lines · 69 tokens per session scan A 7a4b70842c27
learn-dogfood is a skill published in the GitHub repository debs-obrien/playwright-movies-app (102 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 1,114 once invoked, about $0.0003 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-30.
Other skills, from other repositories
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
playwright-component-testing
Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue.
playwright-trace
Inspect Playwright trace files from the command line — list actions, view requests, console, errors, snapshots and screenshots.
testing-e2e
End-to-end testing patterns with Playwright — page objects, AI agent testing, visual regression, accessibility testing with axe-core, and CI integration. Use when writing E2E tests, setting up Playwright, implementing visual regression, or testing accessibility.
Axe-core Accessibility Testing
Accessibility testing skill using axe-core and Playwright for automated WCAG 2.1 compliance auditing, custom rules, and accessibility reporting.
Flaky Test Doctor
Diagnose flaky test failures from Playwright reports, traces, and rerun history. Classify each failure as product, test, environment, data, or unknown with cited evidence and a proposed fix. Never auto-modifies code without opt-in.