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 agentmods add skills/mathaix/openclawmachines/ocm-debuggingnpx skills add mathaix/OpenClawMachines --skill ocm-debugginggit clone --depth 1 https://github.com/mathaix/OpenClawMachinesWhat 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 | $0.00044 | $0.00583 |
| Opus 5 | $0.00022 | $0.00292 |
| Sonnet 5 | $0.00009 | $0.00117 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
ocm-debugging 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 2d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OCM Debugging
Use this skill when behavior differs between local, operator, hosted-like, Worker, agent, guest VM, or KVM integration paths and the next move should be a debug signal rather than a guess.
Default Loop
- State the suspected boundary:
- profile/config
- auth/cookie/session exchange
- Cloudflare Worker/KV routing
- host enrollment or heartbeat
- placement/capacity
- backend-to-agent API
- metadata server
- guest init/rootfs
- Firecracker network/storage
- runtime artifact/version selection
- Add or enable the narrowest signal that proves that boundary.
- Reproduce with the same profile, env, domain shape, host state, and runtime version. Do not switch profiles or providers unless that variable is under test.
- Compare configured state with actual activated state.
- Patch the root cause.
- Rerun the exact failing probe, then broaden only if a shared contract needs it.
Useful Starting Points
- Config/profile load:
backend/internal/config. - Session cookies and auth:
backend/internal/api/auth_handlers.go. - Worker route selection and resolve fallback:
worker/worker.js. - Route provisioning and signing keys:
backend/internal/routing. - Machine start/upgrade lifecycle:
backend/internal/machines/runtime.go. - Host enrollment:
backend/internal/api/enrollment.go. - Agent control API:
backend/internal/agentapi. - Firecracker orchestration:
backend/internal/orchestrator. - Guest metadata:
backend/internal/metadata. - Guest init:
scripts/init-openclaw.sh. - Local full-stack runbook:
docs/local-firecracker-e2e.md.
Proof Choices
- Single backend invariant: focused Go package test.
- Worker route/auth bug:
make test-worker. - Frontend/auth UI bug: focused frontend test plus
make typecheck. - Local control-plane setup:
make local-statusor the relevantscripts/local-dev.shcommand. - Firecracker/agent/rootfs/network bug: KVM integration or local
scripts/local-e2e-firecracker.sh status, with exact blocker reported when unavailable. - Cloudflare/operator routing bug: local Worker test plus config/doc review; live Cloudflare proof only when credentials and operator approval are present.
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.
- 2d ago First seen · 71 lines · 44 tokens per session scan A d9f4bd34ee20
ocm-debugging is a skill published in the GitHub repository mathaix/OpenClawMachines (57 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 583 once invoked, about $0.0002 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
testing-preview
Test the preview proxy feature end-to-end. Use when verifying preview URL changes, auth changes on the web proxy route, or networking-related fixes.
agent-reach
MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g. 全网调研 X / 帮我调研一下 X / 查一下 X / 搜搜 X / 看看大家怎么评价 X / X 上有什么讨论 / research this topic。 Also MUST USE when user mentions any platform or shares any URL/链接: 小红书/xiaohongshu/xhs, Twitter/推特/X, B站/bilibili, Reddit, Facebook, Instagram…
ast-grep
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
pinchtab-stealth-score
Run the PinchTab stealth-score sweep against 15 bot-detection / fingerprint sites (sannysoft, rebrowser, deviceandbrowserinfo, iphey, whoer, browserscan, pixelscan, fingerprint-scan, incolumitas, fvision, amiunique, browserleaks, creepjs, coveryourtracks, fingerprint-demo). Starts a Docker PinchTab container per…
bernstein-approve
Review and approve/reject pending tasks or plans in Bernstein. Use when the user asks about approvals, wants to review agent work, or needs to approve/reject a plan before execution begins.