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 capmonstergit 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/capmonster)<a href="https://agentmods.dev/skills/agentcomputerai/torch/capmonster"><img src="https://agentmods.dev/badge/skills/agentcomputerai/torch/capmonster/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/capmonster"><img src="https://agentmods.dev/badge/skills/agentcomputerai/torch/capmonster.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.00104 | $0.02230 |
| Opus 5.5 | $0.00042 | $0.00892 |
| Sonnet 5.5 | $0.00021 | $0.00446 |
| Haiku 4.5 | $0.00010 | $0.00223 |
Grade A, and why
capmonster 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CapMonster Cloud
CapMonster Cloud is an AI-based CAPTCHA solver. Unlike 2Captcha (human workers), CapMonster uses trained models, which makes it faster (10-30s) and cheaper ($0.60/1K for reCAPTCHA v2) but slightly less reliable on novel challenge variants.
Use this skill when:
- You need to solve the same CAPTCHA types as 2Captcha, but want lower cost
- You're scraping at volume (>10K solves) where $0.40/1K savings matter
- You need
cf_clearancecookies for Cloudflare Challenge pages (CapMonster has a dedicated task type for this) - 2Captcha returns
ERROR_CAPTCHA_UNSOLVABLE— try CapMonster as fallback
For the 2Captcha equivalent, see 2captcha. The task shape is similar but the client API is different.
Installation
Two npm packages exist. Prefer the official ZennoLab client:
# Official — maintained by capmonster.cloud
npm install @zennolab_com/capmonstercloud-client
# Community alternative — node-capmonster — only use if you need TypeScript types or features not in the official client
npm install node-capmonster
Examples below use the official client.
Setup
import {
CapMonsterCloudClientFactory,
ClientOptions,
} from "@zennolab_com/capmonstercloud-client";
const client = CapMonsterCloudClientFactory.Create(
new ClientOptions({ clientKey: process.env.CAPMONSTER_API_KEY })
);
Read the key from process.env.CAPMONSTER_API_KEY — torch loads .env automatically.
Check balance
const balance = await client.getBalance();
console.log(`CapMonster balance: $${balance}`);
Pay-per-success billing: you're only charged for tasks that returned a valid token.
Cloudflare Turnstile
Simple Turnstile (no proxy)
import { TurnstileRequest } from "@zennolab_com/capmonstercloud-client";
const req = new TurnstileRequest({
websiteURL: "https://example.com/login",
websiteKey: "0x4AAAAAAABUYP0XeMJF0xoy",
});
const res = await client.Solve(req);
const token = res.solution.token;
// Inject into the hidden field
await page.evaluate((t) => {
document.querySelector('input[name="cf-turnstile-response"]').value = t;
}, token);
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 · 284 lines · 104 tokens per session scan A 0e4e8d7d8765
capmonster is a skill published in the GitHub repository AgentComputerAI/torch (5 stars, last pushed 6mo ago), licensed MIT. It adds 104 tokens to every session and 2,230 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.