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/clawteam/clawteam-devnpx skills add HKUDS/ClawTeam --skill clawteam-devgit clone --depth 1 https://github.com/HKUDS/ClawTeamWhat 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.00094 | $0.01016 |
| Opus 5 | $0.00047 | $0.00508 |
| Sonnet 5 | $0.00019 | $0.00203 |
| Haiku 4.5 | $0.00009 | $0.00102 |
Grade A, and why
clawteam-dev 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- clawteam-dev — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClawTeam Local Development
This skill is for developing and validating ClawTeam inside the ClawTeam repository. Use it when the task is about changing ClawTeam itself, testing local behavior, or verifying multi-agent workflows against the current checkout.
Development Bootstrap
Standardize the local development environment with the bootstrap script:
bash scripts/bootstrap_clawteam_dev.sh
This script lives in scripts/bootstrap_clawteam_dev.sh inside this skill folder.
This script does all of the following:
- Creates a fixed uv environment at
~/.clawteam-venv - Installs the current repository into that environment with dev dependencies
- Writes
~/.local/bin/clawteamto point at the fixed environment - Adds a
clawteam()shell function block to~/.bashrc
After it finishes:
source ~/.bashrc
clawteam --version
Use this bootstrap whenever you want the same clawteam command across different
Python environments on the machine.
Project Skill Wiring
To wire another local project so its ./.agents and ./.claude directories use
this repository's local ClawTeam skills directly:
bash scripts/link_local_clawteam_skills.sh /path/to/project
This script lives in scripts/link_local_clawteam_skills.sh inside this skill folder.
This creates these symlinks inside the target project:
./.agents/skills/clawteam./.claude/skills/clawteam
Run the same script again any time you want to refresh or recreate those links.
Typical Uses
- Run targeted local validation after code changes
- Reproduce a spawn / board / task / inbox / harness bug
- Smoke-test the real CLI in tmux or subprocess mode
- Review ClawTeam workflows end-to-end from the current repository checkout
Fast Validation
Prefer the smallest validation that proves the change.
ruff check clawteam/ tests/
pytest tests/<target_file>.py -q
Use broader runs only when the change crosses modules:
pytest tests/test_cli_commands.py -q
pytest tests/test_spawn_backends.py -q
pytest tests/test_harness.py tests/test_event_bus.py -q
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 134 lines · 94 tokens per session scan A 84504f03ffc1
clawteam-dev is a skill published in the GitHub repository HKUDS/ClawTeam (5,520 stars, last pushed 3mo ago), licensed MIT. It adds 94 tokens to every session and 1,016 once invoked, about $0.0005 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…