ESP-Claw is an AI agent framework that runs on Espressif IoT chips and lets people define device behavior through conversation. It handles local sensing, decision-making, and execution for connected devices, with support for event-driven actions, structured memory, and MCP communication.
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/espressif/esp-claw/scheduled_tasknpx skills add espressif/esp-claw --skill scheduled_taskgit clone --depth 1 https://github.com/espressif/esp-clawWrote 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/espressif/esp-claw/scheduled_task)<a href="https://agentmods.dev/skills/espressif/esp-claw/scheduled_task"><img src="https://agentmods.dev/badge/skills/espressif/esp-claw/scheduled_task.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.00043 | $0.01604 |
| Opus 5 | $0.00022 | $0.00802 |
| Sonnet 5 | $0.00009 | $0.00321 |
| Haiku 4.5 | $0.00004 | $0.00160 |
Grade A, and why
scheduled_task 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scheduled Task
Use this skill when the user asks to add a scheduled task, timer, periodic reminder, timed agent wake-up, fixed IM reminder, or scheduled Lua script run.
Run exactly one bundled Lua script with lua_run_script:
{"path":"{CUR_SKILL_DIR}/scripts/add_scheduled_task.lua","args":{},"timeout_ms":60000}
If script execution returns an error, report that error directly to the user. Do not retry with changed arguments or run another script in the same turn unless the user explicitly asks.
Script Args Schema
{
"type": "object",
"properties": {
"task_id": {
"type": "string",
"description": "Stable schedule id. Use lowercase letters, digits, underscore, or hyphen."
},
"kind": {
"type": "string",
"enum": ["cron", "interval"]
},
"cron_expr": {
"type": "string",
"description": "Required when kind is cron. Use a 5-field cron expression: minute hour mday month wday."
},
"interval_ms": {
"type": "integer",
"description": "Required when kind is interval. Must be greater than 0."
},
"mode": {
"type": "string",
"enum": ["wake_agent", "send_message", "run_script"]
},
"text": {
"type": "string",
"description": "Required for wake_agent and send_message. For run_script it is optional schedule text."
},
"script_path": {
"type": "string",
"description": "Required for run_script. Must be an absolute .lua path and must not contain .."
},
"script_args": {
"type": "object",
"default": {}
},
"chat_channel": {
"type": "string",
"description": "Required for wake_agent and send_message, for example feishu, weixin, qq, or telegram."
},
"chat_id": {
"type": "string",
"description": "Required for wake_agent and send_message."
},
"enabled": {
"type": "boolean",
"default": true
},
"trigger_count": {
"type": "integer",
"default": 0,
"description": "Maximum number of times to trigger. Use 0 for unlimited. Preferred over max_runs."
},
"max_runs": {
"type": "integer",
"default": 0,
"description": "Compatibility alias for trigger_count. Use trigger_count for new calls."
}
},
"required": ["task_id", "kind", "mode"]
}
What ships with it
1 file 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.
- 5d ago First seen · 148 lines · 43 tokens per session scan A adb86cbca446
scheduled_task is a skill published in the GitHub repository espressif/esp-claw (2,080 stars, last pushed 2d ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,604 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
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…