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 skills add geezerrrr/motive --skill wacligit clone --depth 1 https://github.com/geezerrrr/motiveWrote 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/geezerrrr/motive/wacli)<a href="https://agentmods.dev/skills/geezerrrr/motive/wacli"><img src="https://agentmods.dev/badge/skills/geezerrrr/motive/wacli/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/geezerrrr/motive/wacli"><img src="https://agentmods.dev/badge/skills/geezerrrr/motive/wacli.svg" alt="Reviewed on agentmods" width="80" 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.00656 |
| Opus 5 | $0.00015 | $0.00328 |
| Sonnet 5 | $0.00006 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
wacli 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 9d 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.
This is a copy
83% identical to wacli — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
wacli
Use wacli only when the user explicitly asks you to message someone else on WhatsApp or when they ask to sync/search WhatsApp history.
Do NOT use wacli for normal user chats; OpenClaw routes WhatsApp conversations automatically.
If the user is chatting with you on WhatsApp, you should not reach for this tool unless they ask you to contact a third party.
Safety
- Require explicit recipient + message text.
- Confirm recipient + message before sending.
- If anything is ambiguous, ask a clarifying question.
Auth + sync
wacli auth(QR login + initial sync)wacli sync --follow(continuous sync)wacli doctor
Find chats + messages
wacli chats list --limit 20 --query "name or number"wacli messages search "query" --limit 20 --chat <jid>wacli messages search "invoice" --after 2025-01-01 --before 2025-12-31
History backfill
wacli history backfill --chat <jid> --requests 2 --count 50
Send
- Text:
wacli send text --to "+14155551212" --message "Hello! Are you free at 3pm?" - Group:
wacli send text --to "[email protected]" --message "Running 5 min late." - File:
wacli send file --to "+14155551212" --file /path/agenda.pdf --caption "Agenda"
Notes
- Store dir:
~/.wacli(override with--store). - Use
--jsonfor machine-readable output when parsing. - Backfill requires your phone online; results are best-effort.
- WhatsApp CLI is not needed for routine user chats; it’s for messaging other people.
- JIDs: direct chats look like
<number>@s.whatsapp.net; groups look like<id>@g.us(usewacli chats listto find).
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.
- 9d ago First seen · 73 lines · 31 tokens per session scan A e96ce8a145db
wacli is a skill published in the GitHub repository geezerrrr/motive (117 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 656 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to wacli, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
issue-maintenance
Periodic and on-demand maintenance pass over a repo's open GitHub issue backlog. Re-labels miscategorized or unlabeled issues (bug/enhancement/question/invalid/duplicate) and bug lifecycle labels (needs-repro/needs-info) following the same decision logic as Anthropic's own dogfooded triage-issue command; re-scores…
evidence-check
An honesty gate that makes an AI back up its claims with real evidence instead of presenting guesses as fact. Use as an always-on background behavior, and invoke explicitly when the user says show your work, prove it, how do you know that, evidence check, what's your source, back that up, or when the AI is…
ci-fix-with-memory
Automatically invoke when CI checks fail on a PR. Triggers on: any mention of CI failure, red checks, failed GitHub Actions, or "CI is broken/failing". Reads session handoffs and a known-issues log to avoid repeating failed fix attempts. Do NOT wait for user to ask — invoke as soon as a CI failure is confirmed. Not…
plain-language-audit
Sweeps a codebase's text — comments, docstrings, markdown docs, and user-facing UI copy — for jargon that could be plainer, AI writing tells/tropes, and verbose text that could be tightened. Auto-fixes unambiguous swaps, surfaces judgment calls for review. Trigger on: "jargon audit", "plain language audit", "find…
test-workflow
Automatically run after editing source files to select and run the appropriate test suite. Triggers on: any src/ file edit before a commit, or when the user says "run tests", "check tests", or "make sure tests pass". Selects unit, E2E, visual regression, or CSS lint based on what changed. Protects running dev servers.…
comment-reaper
Finds and removes unnecessary code comments - the ones that restate the code, cite an issue number, narrate refactor history, or wrap a one-line function in six lines of JSDoc. Sorts every find into auto-fix, propose, or never-touch, so the WHY comments survive the sweep. Trigger on: "comment reaper", "reap comments"…