Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add AgentComputerAI/torch --skill camoufoxgit clone --depth 1 https://github.com/AgentComputerAI/torchWrote 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/agentcomputerai/torch/camoufox)<a href="https://agentmods.dev/skills/agentcomputerai/torch/camoufox"><img src="https://agentmods.dev/badge/skills/agentcomputerai/torch/camoufox/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/agentcomputerai/torch/camoufox"><img src="https://agentmods.dev/badge/skills/agentcomputerai/torch/camoufox.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.00091 | $0.02041 |
| Opus 5.5 | $0.00036 | $0.00816 |
| Sonnet 5.5 | $0.00018 | $0.00408 |
| Haiku 4.5 | $0.00009 | $0.00204 |
Grade A, and why
camoufox 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 1mo 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Camoufox
Camoufox is a Firefox fork where fingerprint spoofing happens at the C++ engine level — navigator.*, WebGL, Canvas, AudioContext, screen geometry are all rewritten before any JavaScript can inspect them. That makes it structurally more robust than puppeteer-stealth, which patches the same signals via JavaScript shims that anti-bot systems can detect.
For torch, Camoufox is the answer to "my machine can't run the real-Chrome-clone strategy" — VMs, headless servers, CI pipelines, remote boxes with no host Chrome. It's a strict fallback, not a replacement: when 127.0.0.1:9222 is available (the user's real profile), that's still the better choice because it has real cookies, history, and browsing reputation that Camoufox's synthetic fingerprints cannot replicate.
When to activate
Use this skill when:
- Running on a VM or headless server — no host Chrome to clone, no GUI to drive a headed browser, and
puppeteer.launch()with stealth gets detected on hard sites - Running in CI — same reasons
- You need concurrent personas — torch's cloned profile is a single identity; Camoufox's BrowserForge fingerprint generator produces internally-consistent fresh personas on demand (5% Linux, 2560x1440 at 9.5%, Intel HD GPU at 27.5%, etc. matching real-world distributions)
- The current toolchain is genuinely failing — a site that real-Chrome-clone + stealth + solver + proxy still can't crack (rare, but happens — Interstitial, Kasada, Shape)
Do not use this skill when:
- The user has a real Chrome profile torch can clone (
127.0.0.1:9222is set) — real profile beats synthetic fingerprint for account-level reputation scoring - The site tests specifically for Chrome/Chromium (some sites use V8-specific quirks that SpiderMonkey cannot spoof)
- You only need to scrape soft targets where vanilla stealth plugin already works
Installation
Camoufox is Python-first. torch drives it from Node via the Playwright server mode.
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.
- 1mo ago First seen · 161 lines · 91 tokens per session scan A 4c49e0e5aa76
camoufox is a skill published in the GitHub repository AgentComputerAI/torch (5 stars, last pushed 6mo ago), licensed MIT. It adds 91 tokens to every session and 2,041 once invoked, about $0.0004 per session on Opus 5.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 skills, from other repositories
chrome-extension
Use when building or shipping a Manifest V3 browser extension and hitting its quirks — service worker dying and losing state, permission warnings, a Chrome Web Store rejection, content-script/worker/popup messaging, or an MV2-to-V3 migration. NOT a generic web app (that is nextjs), NOT a desktop shell (that is…
data-scraper
Use when data lives on a website with no usable API — listings, prices, public records — and the scrape must stay legal and not get blocked: legal gate, extraction path, durable selectors, pacing, resilience. NOT parsing bytes you already hold into fields (that is structured-extraction), NOT a documented API or key…
nodejs
Use when building or operating a plain Node.js / Express 5 backend service: project layout, async correctness, central error middleware, fail-fast config, graceful shutdown on SIGTERM. NOT DI modules/providers/guards (that is nestjs), NOT the type system or tsconfig (that is typescript), NOT REST contract design (that…
checking-a-page
Check that a web page you wrote or changed actually works, by opening it in a browser and driving every control on it. Use after creating or editing an HTML page, or the JavaScript or CSS that a page loads.
browser-qa
Testing web apps through a real browser: reconnaissance before acting, selector discovery, state capture, console errors and screenshot evidence. Use on a web surface end to end, or to reproduce a front-end bug.
browser-automation
A browser-automation workflow that detects the terminal environment and chooses a browser control tool. It supports opening pages, taking snapshots, clicking, filling fields, and other checks.