Agent skill

Dogfood

by redf0x1 in redf0x1/camofox-browser

QA testing workflow for CamoFox Browser — systematic testing with console capture, error detection, and Playwright tracing.

MITAuto-check passedTesting & QA

Install Dogfood

skills CLI
$ npx skills add redf0x1/camofox-browser --skill dogfood -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install redf0x1/camofox-browser dogfood --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/redf0x1/camofox-browser.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/dogfood .claude/skills/dogfood && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
dogfood
GitHub stars
412
Token cost
~1.2k tokens
SKILL.md length
209 words
Files
3 (incl. references)
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

QA testing workflow for CamoFox Browser — systematic testing with console capture, error detection, and Playwright tracing.

  • Works in 5 steps: Initialize Session → Navigate & Orient → Systematic Exploration → …
  • The user needs to test a web application
  • SKILL.md covers When to Use, Prerequisites, Workflow and Issue Reporting, plus 2 more sections
  • Reaches target-app.com and trace.playwright.dev

What it does

Dogfood is an agent skill from redf0x1/camofox-browser. QA testing workflow for CamoFox Browser — systematic testing with console capture, error detection, and Playwright tracing. Use when the user needs to test a web application, perform QA validation, do exploratory testing, or verify web app behavior. Triggers include "test this website", "QA", "dogfood", "exploratory testing", "find bugs", or any request to systematically test a web application.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/issue-taxonomy.md` and `templates/dogfood-report-template.md`).

It sits in Testing & QA, covering QA and bug reports, Browser testing and Debugging. It works with Playwright. The repository describes itself as: Anti-detection browser server for AI agents — REST API wrapping Camoufox engine with OpenClaw plugin support. The licence is MIT.

When your agent uses it

  • The user needs to test a web application
  • Perform QA validation
  • Do exploratory testing
  • Verify web app behavior

Example prompts

  • “test this website”
  • “dogfood”
  • “exploratory testing”
  • “/dogfood”

Requirements

  • Pre-approved tools (allowed-tools): Bash(camofox:*)

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Initialize Session
  2. Navigate & Orient
  3. Systematic Exploration
  4. Document Issues
  5. Wrap Up

What it can do on your machine

Read from SKILL.md and the folder at commit 4f23dcf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(camofox:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • target-app.com
    • trace.playwright.dev

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dogfood loads about 1.2k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 101 tokens; SKILL.md has 209 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~101
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from redf0x1/camofox-browser at commit 4f23dcf, republished under its MIT licence (© redf0x1). 209 words, ~1,185 tokens.

Download SKILL.mdSave it as .claude/skills/dogfood/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
dogfood
description
QA testing workflow for CamoFox Browser — systematic testing with console capture, error detection, and Playwright tracing. Use when the user needs to test a web application, perform QA validation, do exploratory testing, or verify web app behavior. Triggers include "test this website", "QA", "dogfood", "exploratory testing", "find bugs", or any request to systematically test a web application.
allowed-tools
Bash(camofox:*)

Dogfood QA Testing — camofox-browser

Systematic exploratory testing of web applications using camofox-browser's anti-detection browser automation.

When to Use

  • Testing web applications for bugs, UX issues, and accessibility problems
  • QA validation before release
  • Exploratory testing of new features
  • Cross-browser verification with Firefox/Camoufox engine

Prerequisites

  • camofox-browser server running on port 9377
  • Target application URL accessible

Workflow

Phase 1: Initialize Session
bash
# Create a dedicated test session
camofox open "about:blank" --user dogfood-qa

# Start trace recording for evidence capture
camofox trace start --user dogfood-qa --screenshots --snapshots
Phase 2: Navigate & Orient
bash
# Navigate to target application
camofox navigate "https://target-app.com" --user dogfood-qa

# Take initial snapshot to understand page structure
camofox snapshot --user dogfood-qa

# Capture annotated screenshot for visual baseline
camofox annotate --user dogfood-qa
Phase 3: Systematic Exploration
3.1 Happy Path Testing

Follow the primary user flows:

bash
# Interact with elements using refs from snapshot
camofox click e5 --user dogfood-qa
camofox type e3 "test input" --user dogfood-qa
camofox press Enter --user dogfood-qa

# Wait for navigation/loading
camofox wait networkidle --user dogfood-qa

# Capture state after each action
camofox snapshot --user dogfood-qa
3.2 Edge Case Testing
bash
# Test empty inputs
camofox type e3 "" --user dogfood-qa
camofox press Enter --user dogfood-qa

# Test long strings
camofox type e3 "aaaa...very long string..." --user dogfood-qa
camofox press Enter --user dogfood-qa

# Test special characters
camofox type e3 "<script>alert('xss')</script>" --user dogfood-qa
camofox press Enter --user dogfood-qa
3.3 Error Discovery
bash
# Check for console errors after interactions
camofox errors --user dogfood-qa

# Check console output for warnings
camofox console --user dogfood-qa --type warning

# Monitor all console messages
camofox console --user dogfood-qa --limit 50
3.4 State & Navigation Testing
bash
# Test back/forward navigation
camofox go-back --user dogfood-qa
camofox go-forward --user dogfood-qa

# Save session state for later comparison
camofox session save dogfood-qa-state --user dogfood-qa

# Test page reload
camofox navigate "https://target-app.com" --user dogfood-qa
Phase 4: Document Issues

When a bug is found:

bash
# 1. Capture visual evidence
camofox annotate --user dogfood-qa

# 2. Capture page errors
camofox errors --user dogfood-qa

# 3. Capture console logs
camofox console --user dogfood-qa

# 4. Mark trace chunk for this specific issue
camofox trace chunk-start --user dogfood-qa
# ... reproduce the bug ...
camofox trace chunk-stop --user dogfood-qa

# 5. Take snapshot for element state
camofox snapshot --user dogfood-qa
Phase 5: Wrap Up
bash
# Stop trace recording
camofox trace stop --user dogfood-qa
# → Trace ZIP saved to ~/.camofox/traces/
# → View at https://trace.playwright.dev

# Final console/error summary
camofox errors --user dogfood-qa
camofox console --user dogfood-qa --type error

# Close session
camofox close --user dogfood-qa

Issue Reporting

Use the issue taxonomy to classify findings. Use the report template to document each issue.

Key Differences from Standard Browser Testing

FeatureStandardcamofox-browser
DetectionEasily flagged as botAnti-detection (C++ spoofing)
BrowserChrome/ChromiumFirefox/Camoufox
EvidenceScreenshots onlyTraces (screenshots + DOM + network)
ConsoleManual DevToolsconsole / errors commands
Element refsCSS selectorsAccessibility tree refs (eN)

Tips

  • Use trace chunk-start/stop to isolate specific bug reproductions within a longer session
  • Check errors frequently — many bugs show console errors before visual symptoms
  • Use annotate for visual evidence — it numbers all interactive elements
  • Trace ZIPs contain full reproduction data — share via trace.playwright.dev
  • The --user flag isolates test sessions from each other

© redf0x1, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/dogfood of redf0x1/camofox-browser.

  • SKILL.md
  • references/issue-taxonomy.md
  • templates/dogfood-report-template.md

Open the folder on GitHubat commit 4f23dcf

Compare with similar skills

Dogfood next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dogfood compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dogfood this skillredf0x1/camofox-browser412—~1.2kAutomated safety check: PassMIT
Replica TestJakeschincariol/replica-skill1.4k—~819Automated safety check: PassMIT
Testingkortix-ai/suna20k—~3.6kAutomated safety check: NotesCustom licence
Playwright Debugvoicetreelab/voicetree924—~1.2kAutomated safety check: PassCustom licence
Playwright Coretestdino-hq/playwright-skill3901 repos~1.4kAutomated safety check: PassMIT
Hands On Testktnyt/cclsp675—~1.7kAutomated safety check: PassMIT

Similar skills

  • Replica Test

    Jakeschincariol/replica-skill

    Clicks through every flow of an app clone and tests it for bugs: a test plan generated from the recon flows with happy paths and edge cases, Playwright end-to-end tests where possible, a browser…

    1.4k GitHub stars~819 tokensUpdated 7 days ago
    Testing & QAAuto-check passed
  • Testing

    kortix-ai/suna

    A skill your agent uses for every Kortix test task, behavior change, bug fix, refactor, API route change, CLI change, SDK change, browser journey, test failure, coverage question, local benchmark…

    20k GitHub stars~3.6k tokensUpdated today
    Testing & QAAuto-check: notes
  • Playwright Debug

    voicetreelab/voicetree

    This skill should be used when the user asks to "debug the electron app", "connect playwright to VoiceTree", "take screenshots of the running app", "interact with the live UI", "inspect the running…

    924 GitHub stars~1.2k tokensUpdated 3 days ago
    Testing & QAAuto-check passed
  • Playwright Core

    testdino-hq/playwright-skill

    Battle-tested Playwright patterns for writing and debugging reliable E2E, API, component, visual, accessibility, and security tests.

    390 GitHub starsUsed in 1 repo~1.4k tokens
    Testing & QAAuto-check passed
  • Hands On Test

    ktnyt/cclsp

    Performs manual hands-on testing of a web application using playwright-cli.

    675 GitHub stars~1.7k tokensUpdated 7 mo ago
    Testing & QAAuto-check passed
  • UI Visual Debugging

    NangoHQ/nango

    A skill your agent uses when modifying or visually debugging Nango frontend UI, including packages/webapp, packages/connect-ui, browser interactions, screenshots, and visual regressions.

    13k GitHub stars~1.3k tokensUpdated yesterday
    Testing & QAAuto-check passed

More from redf0x1/camofox-browser

  • Camofox Browser

    redf0x1/camofox-browser

    Anti-detection browser automation for AI agents. An agent skill from redf0x1/camofox-browser.

    412 GitHub stars~4.6k tokensUpdated 19 days ago
    Auto-check passed
  • Camofox CLI

    redf0x1/camofox-browser

    CamoFox CLI — 50 commands for anti-detection browser automation from the terminal.

    412 GitHub stars~1.3k tokensUpdated 19 days ago
    Auto-check passed
  • Gemini Image

    redf0x1/camofox-browser

    Automate image generation on Google Gemini (gemini.google.com) using CamoFox CLI.

    412 GitHub stars~1.6k tokensUpdated 19 days ago
    Auto-check passed
  • Reddit

    redf0x1/camofox-browser

    Reddit automation with CamoFox CLI — login, browse, post, comment, reply with anti-detection.

    412 GitHub stars~1.5k tokensUpdated 19 days ago
    Auto-check passed

Works with

Categories

Questions about Dogfood

What does Dogfood do?

QA testing workflow for CamoFox Browser — systematic testing with console capture, error detection, and Playwright tracing. Dogfood is an agent skill from redf0x1/camofox-browser. QA testing workflow for CamoFox Browser — systematic testing with console capture, error detection, and Playwright tracing.

When should I use Dogfood?

Dogfood fits situations like: the user needs to test a web application; perform QA validation; do exploratory testing; verify web app behavior.

How do I install Dogfood in Claude Code?

Run `npx skills add redf0x1/camofox-browser --skill dogfood -a claude-code`. Or copy the skill folder (skills/dogfood in redf0x1/camofox-browser) into .claude/skills/dogfood in your project. Claude Code loads it when a task matches its description.

How do I install Dogfood in Codex?

Run `npx skills add redf0x1/camofox-browser --skill dogfood -a codex`. Or copy the skill folder (skills/dogfood in redf0x1/camofox-browser) into .agents/skills/dogfood in your project. Codex loads it when a task matches its description.

Can I use Dogfood in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add redf0x1/camofox-browser --skill dogfood -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dogfood, .gemini/skills/dogfood, .github/skills/dogfood and .opencode/skills/dogfood in your project.

What does Dogfood need to run?

SKILL.md names no scripts, command-line tools or credentials: Dogfood is instructions for the agent only. Its frontmatter pre-approves these tools: Bash(camofox:*).

Does Dogfood access the network?

SKILL.md names 2 domains. In commands or code: target-app.com and trace.playwright.dev; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Dogfood safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dogfood use?

Dogfood is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dogfood use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 495 tokens, read only when the agent opens those files.

What are the alternatives to Dogfood?

Skills that share tags, products or a category with Dogfood: Replica Test (Jakeschincariol/replica-skill, 1.4k stars), Testing (kortix-ai/suna, 20k stars), Playwright Debug (voicetreelab/voicetree, 924 stars) and Playwright Core (testdino-hq/playwright-skill, 390 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dogfood?

redf0x1 (a GitHub user) maintains it in redf0x1/camofox-browser, which has 412 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 22, 2026.

Source: redf0x1/camofox-browser on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.