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/degenapetrader/evclaw/executenpx skills add Degenapetrader/EVClaw --skill executegit clone --depth 1 https://github.com/Degenapetrader/EVClawWhat 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.00041 | $0.00440 |
| Opus 5 | $0.00020 | $0.00220 |
| Sonnet 5 | $0.00008 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
execute 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.
What it actually says
/execute (manual plan execution)
This command supports two manual modes:
- Plan mode (existing): execute a previously generated
/tradeplan. - Ad-hoc mode: parse direction/symbol/mode and generate+execute a plan deterministically.
Usage
- Fast fill:
/execute ETH-01 chase
- RESTING limit (pending SR limit; default cancel timing comes from the stored plan, typically 60m):
/execute ETH-01 limit
- Override limit TTL:
/execute ETH-01 limit 4h
Ad-hoc examples:
/execute long ETH chase/execute ETH long limit 350/execute short ETH chase 250/execute long ETH chase 300 confirm
Workflow
- Run the execute bridge script (deterministic):
EVCLAW_ROOT="${EVCLAW_ROOT:-$HOME/.openclaw/skills/EVClaw}" \
python3 "$EVCLAW_ROOT/openclaw_skills/execute/scripts/execute_bridge.py" <ARGS_FROM_/execute>
- Handle JSON response deterministically:
- If
ok=true: return execution result. - If
needs=size_usd: ask one question: "What size in USD?" - If
needs=confirm: show preview + ask for explicit confirm command.- Use returned
confirm_commandexactly.
- Use returned
- Confirmation behavior for ad-hoc mode:
- Do not execute ad-hoc input without explicit confirmation.
- After user confirms, run bridge again with
confirmtoken.
Safety
- Refuse if plan is expired or missing.
- Never run on behalf of non-owner senders.
- Keep audit trail: ad-hoc mode must generate a plan first, then execute that plan.
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.
- 2d ago First seen · 52 lines · 41 tokens per session scan A 6e9f5d529a0b
execute is a skill published in the GitHub repository Degenapetrader/EVClaw (40 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 440 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.
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.