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.
git clone --depth 1 https://github.com/wawimundo/viber-mcpWrote 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/commands/wawimundo/viber-mcp/viber-reply)<a href="https://agentmods.dev/commands/wawimundo/viber-mcp/viber-reply"><img src="https://agentmods.dev/badge/commands/wawimundo/viber-mcp/viber-reply/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/commands/wawimundo/viber-mcp/viber-reply"><img src="https://agentmods.dev/badge/commands/wawimundo/viber-mcp/viber-reply.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.00019 | $0.00301 |
| Opus 5.5 | $0.00008 | $0.00120 |
| Sonnet 5.5 | $0.00004 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
viber-reply 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 1mo 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
Draft a reply to the Viber conversation that is currently open on screen.
Steps:
- Call the
read_open_chatMCP tool to OCR the visible conversation. - Identify the most recent incoming message(s) and the thread's context, language, and tone (the user is in the Philippines — match Taglish/English/Filipino as the chat uses it).
- Compose a natural, appropriately concise reply as the user (first person, their voice).
- If the user gave guidance in the arguments below, follow it for content/tone/length.
- Otherwise infer a sensible reply from context.
- Show me the drafted reply text and a one-line summary of what you're replying to.
- Call the
put_draftMCP tool with that reply to paste it into the open chat's compose box. Do NOT send it — the user reviews and presses send themselves. - Tell the user the draft is in Viber's compose box, ready to review and send.
Important:
- Never call
send_messagefor this command — drafting only, the user sends. - OCR only sees on-screen text; if the conversation is unclear or empty, say so and ask the user to scroll the relevant messages into view rather than guessing.
User guidance for this reply (optional): $ARGUMENTS
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.
- 1mo ago First seen · 25 lines · 19 tokens per session scan A 4c74b21d923e
viber-reply is a command published in the GitHub repository wawimundo/viber-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 301 once invoked, about $0.0001 per session on Opus 5.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-31.
Other commands, from other repositories
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
verify-pr
Verify a PR's frontend changes through browser automation.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.
can-i-use
Check browser support for web platform features against the project's browser targets.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.