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 commands/ibrahimhajjaj/wu-cli/communitiesgit clone --depth 1 https://github.com/ibrahimhajjaj/wu-cliWhat 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.00008 | $0.00172 |
| Opus 5 | $0.00004 | $0.00086 |
| Sonnet 5 | $0.00002 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
communities 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 3d 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
List WhatsApp Communities (parent groups that contain subgroups) using the wu MCP server.
Call wu_communities_list with with_subgroups: true when the user wants the full hierarchy, or default (false) when they just want to see which communities they're in. Each community row includes its constraint state.
Render as a tree: community parent on its own line, subgroups indented underneath with their tag (announce for the announcement channel, subgroup for the rest).
If the cache is empty, suggest the user run wu groups list --live once or start wu daemon so groups get populated as events arrive.
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.
- 3d ago First seen · 13 lines · 8 tokens per session scan A 796384cf55fe
communities is a command published in the GitHub repository ibrahimhajjaj/wu-cli (14 stars, last pushed 21d ago), licensed MIT. It adds 8 tokens to every session and 172 once invoked, about $0.0000 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 commands, from other repositories
review-and-fix
Reviews a PR or staged changes and automatically initiates a Pickle Fix loop for findings.
pr-review
Review a specific pull request.
frontend
Injects context of all relevant cli files.
code-guide
Answer questions about the Gemini CLI codebase with explanations and code snippets.
introspect
Analyze the influence of system instructions on a specific action.
cleanup-back-to-main
Go back to main and clean up the branch.