ClaudeClaw is a lightweight personal assistant built into Claude Code that runs tasks in the background on schedules and responds through messaging services. It is for people who want Claude Code to handle recurring work, voice commands, and integrations while a daemon remains active. Its catalogue commands, skills, instructions, and plugin provide the assistant’s setup and operating workflows.
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/moazbuilds/claudeclaw/create-skillnpx skills add moazbuilds/claudeclaw --skill create-skillgit clone --depth 1 https://github.com/moazbuilds/claudeclawWrote 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/moazbuilds/claudeclaw/create-skill)<a href="https://agentmods.dev/skills/moazbuilds/claudeclaw/create-skill"><img src="https://agentmods.dev/badge/skills/moazbuilds/claudeclaw/create-skill.svg" alt="Measured on agentmods" 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 | $0.00092 | $0.00587 |
| Opus 5 | $0.00046 | $0.00293 |
| Sonnet 5 | $0.00018 | $0.00117 |
| Haiku 4.5 | $0.00009 | $0.00059 |
Grade A, and why
create-skill 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 5d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Skill
Create new skills for Claude Code. Use $ARGUMENTS to determine what the user wants.
Skill File Format
A skill is a SKILL.md file inside a skills/<skill-name>/ directory. It uses YAML frontmatter:
---
name: my-skill
description: Short description of when to trigger this skill. Include trigger phrases so Claude knows when to activate it.
---
# Skill Title
Instructions for what Claude should do when this skill is triggered.
Key rules for SKILL.md:
- name: lowercase, kebab-case (e.g.
my-skill) - description: must include trigger phrases and keywords so Claude knows when to use it
- The body contains the full instructions Claude will follow when the skill is invoked
Scope
Skills can be created at two levels:
Project Level (default)
- Location:
<project-root>/skills/<skill-name>/SKILL.md - Only available within this project
- No special permissions needed
- Use this when the skill is project-specific
Global Level
- Location:
~/.claude/skills/<skill-name>/SKILL.md - Available across all projects
- Requires write access to
~/.claude/ - Use this when the skill should work everywhere
Steps
-
Ask the user conversationally what the skill should do, what scope (project or global), and what name they want. Suggest ideas based on context.
-
Based on their answers, generate the
SKILL.mdcontent:- Write a clear, descriptive
namein kebab-case - Write a
descriptionwith plenty of trigger phrases so Claude knows when to activate it - Write detailed body instructions for what Claude should do
- Write a clear, descriptive
-
Create the skill:
- Project level: Write to
skills/<skill-name>/SKILL.mdrelative to project root - Global level: Write to
~/.claude/skills/<skill-name>/SKILL.md
- Project level: Write to
-
Confirm creation and show the user:
- The skill name and path
- How to invoke it:
/<plugin-name>:<skill-name>or just by asking naturally (Claude auto-triggers based on description) - Remind them the skill is available immediately — no restart needed
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.
- 5d ago First seen · 63 lines · 92 tokens per session scan A 538f486390df
create-skill is a skill published in the GitHub repository moazbuilds/claudeclaw (1,315 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 587 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…