Borrowing it
Nothing to install: this file belongs to panghy/whatsapp-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/panghy/whatsapp-mcp-server/main/AGENTS.mdgit clone --depth 1 https://github.com/panghy/whatsapp-mcp-serverWrote 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/instructions/panghy/whatsapp-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/panghy/whatsapp-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/panghy/whatsapp-mcp-server/agents-md.svg" alt="Measured on agentmods" 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.01490 | $0.01490 |
| Opus 5 | $0.00745 | $0.00745 |
| Sonnet 5 | $0.00298 | $0.00298 |
| Haiku 4.5 | $0.00149 | $0.00149 |
Grade A, and why
whatsapp-mcp-server AGENTS.md 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 7d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Release Documentation for AI Agents
Release Architecture
- semantic-release for versioning (config:
.releaserc.json) - electron-builder for building/packaging (config:
package.json→"build"section) - GitHub Actions workflow at
.github/workflows/release.yml - Builds for:
- macOS: dmg + zip
- Linux: AppImage
- Windows: nsis + portable
- Auto-updater: Uses
electron-updater, checkslatest-mac.yml/latest-linux.yml/latest.ymlon the GitHub release
How Releases Are Triggered
Two trigger methods:
- Manual (preferred): Go to GitHub Actions → "Release" workflow → "Run workflow". Optionally provide a tag (e.g.
v1.2.3) to rebuild a specific version, or leave empty to let semantic-release auto-determine version. - Rebuild existing tag: Use the workflow_dispatch with a specific tag input (e.g.
v1.2.3) to rebuild and re-upload artifacts for an existing release.
IMPORTANT: Do NOT add push-to-main triggers — this caused race conditions in the past where two parallel runs (push + tag) uploaded conflicting assets with mismatched SHA512 checksums, breaking the auto-updater.
Workflow Jobs
- semantic-release — Only runs on branch pushes (
workflow_dispatch). Analyzes commits and creates a new GitHub release + tag if warranted. UsesRELEASE_TOKENsecret (PAT) to bypass branch protection. - build — Runs on all 3 OS matrix (
macos-latest,ubuntu-latest,windows-latest). Checks out the tagged commit, syncspackage.jsonversion, builds with electron-builder, and uploads artifacts to the GitHub release with--publish always. - publish-release — Ensures the release is not a draft after all builds complete.
Commit Conventions
semantic-release uses Angular preset with these release rules (from .releaserc.json):
feat:→ minorfix:→ patchperf:→ patchrefactor:→ patchchore:→ patch
Key Configuration
package.json→"build.publish":releaseTypemust be"release"(not"draft") — electron-builder skips upload if the release isn't in the expected state..releaserc.json:npmPublishisfalse(this is an Electron app, not an npm package).- Secrets needed:
RELEASE_TOKEN(PAT with repo scope)APPLE_CERTIFICATEAPPLE_CERTIFICATE_PASSWORDAPPLE_IDAPPLE_PASSWORD
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.
- 7d ago First seen · 113 lines · 1,490 tokens per session scan A 3de27cba435e
whatsapp-mcp-server AGENTS.md is an instructions file published in the GitHub repository panghy/whatsapp-mcp-server (5 stars, last pushed 9d ago), licensed MIT. It adds 1,490 tokens to every session, about $0.0075 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-31.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.