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/samihalawa/whatsapp-go-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/rules/samihalawa/whatsapp-go-mcp/project-structure)<a href="https://agentmods.dev/rules/samihalawa/whatsapp-go-mcp/project-structure"><img src="https://agentmods.dev/badge/rules/samihalawa/whatsapp-go-mcp/project-structure/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/rules/samihalawa/whatsapp-go-mcp/project-structure"><img src="https://agentmods.dev/badge/rules/samihalawa/whatsapp-go-mcp/project-structure.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.00005 | $0.01306 |
| Opus 5.5 | $0.00002 | $0.00522 |
| Sonnet 5.5 | $0.00001 | $0.00261 |
| Haiku 4.5 | $0.00001 | $0.00131 |
Grade A, and why
project-structure 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 2mo 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go WhatsApp Web Multidevice API
This is a Go implementation of a WhatsApp Web Multidevice API that allows you to interact with WhatsApp through HTTP APIs.
Project Structure
Root Directory
- readme.md - Project documentation and usage instructions
- docker-compose.yml - Docker configuration for running the application
- LICENCE.txt - License information
Source Code (src/)
The main source code is organized in the src directory with the following structure:
Command Line Interface
- src/cmd/root.go - Root command using Cobra for CLI commands, handles configuration loading
- src/cmd/rest.go - REST server command implementation
- src/cmd/mcp.go - Model Context Protocol server command implementation
Configuration
- src/config/ - Application configuration settings and constants
Domain Models
The application is organized using domain-driven design principles:
- src/domains/app/ - Core application domain models
- src/domains/chat/ - Chat-related domain models and interfaces
- src/domains/group/ - Group-related domain models
- src/domains/message/ - Message-related domain models
- src/domains/newsletter/ - Newsletter-related domain models
- src/domains/send/ - Message sending domain models
- src/domains/user/ - User-related domain models
Infrastructure
- src/infrastructure/chatstorage/ - Chat storage repository and WhatsApp integration
- src/infrastructure/whatsapp/ - WhatsApp client implementation and related infrastructure
User Interface
- src/ui/rest/ - REST API implementation
- src/ui/rest/helpers/ - Helper functions for REST handlers
- src/ui/rest/middleware/ - Middleware components for request processing
- src/ui/websocket/ - WebSocket implementation for real-time communication
- src/ui/mcp/ - Model Context Protocol server to communication with AI Agent
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.
- 2mo ago First seen · 127 lines · 5 tokens per session scan A 3bf300cf6398
project-structure is a cursor rule published in the GitHub repository samihalawa/whatsapp-go-mcp (6 stars, last pushed 11mo ago), licensed MIT. It adds 5 tokens to every session and 1,306 once invoked, about $0.0000 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 cursor rules, from other repositories
go-backend-scalability-cursorrules-prompt-file
Cursor rules for Go development with backend scalability.
backend
You are an expert in Go, Gin, Gorm, Gen, Cosy (https://cosy.uozi.org/) with a deep understanding of best practices and performance optimization techniques in these technologies.
go-servemux-rest-api-cursorrules-prompt-file
Cursor rules for Go development with ServeMux REST API integration.
go-grpc-service-rule
A set of Chinese-language rules for implementing gRPC services in Go. gRPC is a way for software services to communicate using defined messages and procedures.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
usecase
Claude Rules - Use Case Pattern.