$git clone https://github.com/sshh12/claude-pluginsShrivu's random Claude Code plugins.
| 1 | # claude-plugins |
| 2 | |
| 3 | [](https://blog.sshh.io/) |
| 4 | [](https://github.com/sshh12) |
| 5 | [](https://x.com/ShrivuShankar) |
| 6 | [](https://linkedin.com/in/shrivushankar) |
| 7 | [](https://sshh.io/coffee-chat) |
| 8 | |
| 9 | Shrivu's random Claude Code plugins. |
| 10 | |
| 11 | ## Plugins |
| 12 | |
| 13 | ### [brw](https://github.com/sshh12/claude-plugins/tree/main/plugins/brw) |
| 14 | |
| 15 | Full browser automation for Claude Code via Chrome DevTools Protocol. Navigate, click, type, screenshot, record GIFs, intercept network requests, and more — all from your terminal. |
| 16 | |
| 17 | **Why brw?** Claude for Chrome is a black box that requires a subscription. Playwright MCP and Chrome DevTools MCP servers don't handle highly parallel agent workflows well — they weren't designed for multiple agents sharing one browser concurrently. brw is a lightweight proxy built for agent-first usage: stateless CLI, per-tab mutexes, and JSON output that agents can parse directly. |
| 18 | |
| 19 | ``` |
| 20 | /plugin marketplace add sshh12/claude-plugins |
| 21 | /plugin install brw@shrivu-plugins |
| 22 | ``` |
| 23 | |
| 24 | Then use `/brw` to start browsing. The proxy auto-starts on first command and stays running. Key capabilities: |
| 25 | - **Navigate & interact**: click, type, scroll, drag, keyboard shortcuts |
| 26 | - **Read pages**: screenshots, DOM extraction, console logs, network traffic |
| 27 | - **Record**: GIF recordings of multi-step workflows |
| 28 | - **Multi-tab**: open, switch, and manage browser tabs |
| 29 | - **Script-driven extraction**: capture the app's own XHRs and replay them as a `.js` script that uses the user's existing session — paginate inboxes, export history, scrape behind login without clicking through the UI |
| 30 | - **Security**: configurable URL blocking, protocol restrictions, cookie scoping |
| 31 | |
| 32 | ### [freetaxusa](https://github.com/sshh12/claude-plugins/tree/main/plugins/freetaxusa) |
| 33 | |
| 34 | Tax filing automation for FreeTaxUSA.com. Guides you through filing US federal and state taxes by extracting your tax documents, researching current tax rules, and automating browser-based form filling via `brw`. |
| 35 | |
| 36 | ``` |
| 37 | /plugin marketplace add sshh12/claude-plugins |
| 38 | /plugin install freetaxusa@shrivu-plugins |
| 39 | ``` |
| 40 | |
| 41 | Then use `/freetaxusa` to start. The skill walks through 5 phases: |
| 42 | - **Setup**: Explains risks, legal disclaimers, loads browser automation, gets consent |
| 43 | - **Discovery**: Extracts text and images from your PDFs (W-2s, 1099s, etc.), builds a consolidated summary, front-loads all questions |
| 44 | - **Research**: Fetches current-year tax brackets and rules, runs a life-change questionnaire, flags items that may need a CPA |
| 45 | - **Filing**: Fills FreeTaxUSA forms section by section with a 4-source verification table (expected, entered, page read, screenshot) |
| 46 | - **Review**: Generates a personalized HTML tax breakdown report, walks through a review checklist, creates a data purge reminder |
| 47 | |
| 48 | **Not a tax professional. Not tax advice.** The user reviews and submits their return themselves — the skill never auto-submits. |
| 49 | |
| 50 | ### [whatsup](https://github.com/sshh12/claude-plugins/tree/main/plugins/whatsup) |
| 51 | |
| 52 | WhatsApp **MCP server** for Claude Code via the Baileys WebSocket client. Inbound WhatsApp messages get pushed to Claude as `notifications/claude/channel` events; Claude responds with the `reply` tool. Bidirectional, no polling, no CLI. |
| 53 | |
| 54 | ``` |
| 55 | /plugin marketplace add sshh12/claude-plugins |
| 56 | /plugin install whatsup@shrivu-plugins |
| 57 | ``` |
| 58 | |
| 59 | Restart Claude Code, then ask it to call the `status` tool — first run surfaces a QR file for **WhatsApp → Settings → Linked Devices → Link a Device**. Key capabilities: |
| 60 | - **Bidirectional**: messages from allowlisted contacts arrive as channel notifications; Claude replies via the `reply` MCP tool |
| 61 | - **Tool surface**: `reply`, `react`, `edit_message`, `download_attachment`, `status`, `unreplied`, `list_chats`, `read_chat`, `search`, `contacts` |
| 62 | - **Security**: allowlist-only sends (empty = blocked), per-contact + global rate limits, `<untrusted_user_message>` wrapping on inbound text, audit logging |
| 63 | - **Architecture**: single MCP stdio process — no daemon, no HTTP, lifetime tied to the Claude Code session |
| 64 | |
| 65 | ### [diy-mcp-connector](https://github.com/sshh12/claude-plugins/tree/main/plugins/diy-mcp-connector) |
| 66 | |
| 67 | Turn any web app into a set of tools that Claude can call directly — no browser automation, no screenshots, no copy-pasting between tabs. Instead of Claude navigating a UI like a human (screenshot, click, wait, screenshot again), your connector talks to the app's API and returns clean, structured data. One tool call replaces 4-6 browser steps with ~80% fewer tokens and ~10x faster responses. |
| 68 | |
| 69 | ``` |
| 70 | /plugin marketplace add sshh12/claude-plugins |
| 71 | /plugin ins |