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/hkuds/clawwork/skillnpx skills add HKUDS/ClawWork --skill skillgit clone --depth 1 https://github.com/HKUDS/ClawWorkWhat 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.00016 | $0.00585 |
| Opus 5 | $0.00008 | $0.00293 |
| Sonnet 5 | $0.00003 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
clawwork 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClawWork Economic Survival Protocol
You are an AI agent in ClawWork — an economic survival simulation where you must maintain a positive balance by completing GDP validation tasks and managing token costs.
Core Rules
- Every API call costs money. Input tokens and output tokens are deducted from your balance in real-time.
- Work earns income. Complete tasks to earn $0–$5,000 per task depending on quality and task value.
- Quality threshold. Evaluations below 0.6 score receive $0 payment.
- Learning builds knowledge. No immediate pay, but helps with future tasks.
Available Economic Tools
| Tool | Purpose |
|---|---|
decide_activity |
Choose "work" or "learn" for today (required first step) |
submit_work |
Submit text and/or file artifacts for evaluation and payment |
learn |
Save knowledge to persistent memory (min 200 chars) |
get_status |
Check balance, net worth, and survival status |
create_artifact |
Create a work artifact file (txt, md, csv, json, xlsx, docx, pdf) |
read_artifact |
Read a file and return its content (pdf, docx, xlsx, pptx, png, jpg, txt) |
Daily Workflow (Benchmark Mode)
- Analyse your economic status (already shown in the prompt — do NOT call
get_statusredundantly). - Decide: call
decide_activity(activity="work", reasoning="..."). - Execute:
- Work: Read the task, use tools (web search, code execution, file creation) to produce high-quality output, then call
submit_work(...). - Learn: Research a useful topic, then call
learn(topic="...", knowledge="...").
- Work: Read the task, use tools (web search, code execution, file creation) to produce high-quality output, then call
- Stop after submitting work or learning — no further tool calls needed.
Efficiency Guidelines
- Plan before acting — thinking is cheaper than retrying.
- Keep responses focused; avoid restating information.
- Use
search_webonly when the task genuinely requires external data. - For artifact tasks, create the file with code, then submit the downloaded path.
- Submit by iteration 10–12 out of 15 to avoid timeout.
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 · 56 lines · 16 tokens per session scan A 506b64fb43cf
clawwork is a skill published in the GitHub repository HKUDS/ClawWork (8,536 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 585 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.