Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Numaira-Technology/weclaw-cuanpx agentmods add skills/numaira-technology/weclaw-cua/weclawWrote 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/numaira-technology/weclaw-cua/weclaw)<a href="https://agentmods.dev/skills/numaira-technology/weclaw-cua/weclaw"><img src="https://agentmods.dev/badge/skills/numaira-technology/weclaw-cua/weclaw.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.1 | $0.00031 | $0.01040 |
| Opus 5 | $0.00015 | $0.00520 |
| Sonnet 5 | $0.00006 | $0.00208 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
weclaw 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 7d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WeClaw (OpenClaw host skill)
WeChat must be the desktop app on the same machine as OpenClaw Gateway. This skill automates the UI; it does not work from a phone alone.
One-time setup on the host
-
Clone WeClaw next to your workspace or any fixed path. Set a durable env var (shell profile or OpenClaw
skills.entries.weclaw.env):WECLAW_ROOT= absolute path to the WeClaw git checkout (directory that containsrun.sh).
-
Python venv (from WeClaw README):
cd "$WECLAW_ROOT" python3 -m venv .venv ./.venv/bin/pip install -r requirements.txt -
Copy
config/config.json.exampletoconfig/config.json. Fillgroups_to_monitorand either putopenrouter_api_keyin the file or exportOPENROUTER_API_KEY(env overrides JSON when present per WeClaw config). -
macOS: grant Accessibility to the app running Python (Terminal, iTerm, or the OpenClaw host). Windows: match elevation with WeChat if needed.
-
Install this skill into the active OpenClaw workspace
skills/weclaw/(the script usesopenclaw skills list --jsonto findworkspaceDirwhenopenclawis onPATH, or setOPENCLAW_WORKSPACEto override):"$WECLAW_ROOT/scripts/install_openclaw_skill.sh"Or copy
{baseDir}(this skill’s directory) into your workspaceskills/weclaw/yourself. OpenClaw discoversskills/weclaw/SKILL.md.
Optional openclaw.json (JSON5) snippet so the agent always sees WECLAW_ROOT:
skills.entries.weclaw.env.WECLAW_ROOT = "/absolute/path/to/weclaw"
Run the capture + report pipeline
From the host shell (or schedule via OpenClaw cron / systemd / launchd calling the same command):
export WECLAW_ROOT="/absolute/path/to/weclaw"
export WECLAW_CONFIG_PATH="$WECLAW_ROOT/config/config.json"
cd "$WECLAW_ROOT"
./run.sh
With a non-default config path:
./run.sh /path/to/other-config.json
Stdout is the generated report text (or No matching messages found.). Structured chat exports are JSON files under output_dir from config (default output/).
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.
- 7d ago First seen · 95 lines · 31 tokens per session scan A ad6bf532e601
weclaw is a skill published in the GitHub repository Numaira-Technology/weclaw-cua (32 stars, last pushed 27d ago), licensed Apache-2.0. It adds 31 tokens to every session and 1,040 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.