Use it when installing, running, testing, documenting, or changing the bridge. It points agents to the files and commands needed for common development work.

It gives an agent the project’s agreed source of truth and helps prevent changes that could break message routing, stored data, or runtime behavior.

How arespawn/WhatsAppToDiscord configures Codex and OpenCode

Q: What is WhatsAppToDiscord AGENTS.md?

A repository guide for coding agents working on WhatsAppToDiscord, a self-hosted bridge that mirrors WhatsApp chats into Discord. It maps the project, startup commands, documentation, and important safety rules.

Reuse

Borrowing it

Nothing to install: this file belongs to arespawn/WhatsAppToDiscord. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/arespawn/WhatsAppToDiscord/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/arespawn/WhatsAppToDiscord

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/arespawn/whatsapptodiscord/agents-md/github.svg)](https://agentmods.dev/instructions/arespawn/whatsapptodiscord/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/arespawn/whatsapptodiscord/agents-md"><img src="https://agentmods.dev/badge/instructions/arespawn/whatsapptodiscord/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/arespawn/whatsapptodiscord/agents-md"><img src="https://agentmods.dev/badge/instructions/arespawn/whatsapptodiscord/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 731 This file is loaded in full into every session.

When invoked 731 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00731	$0.00731
Opus 5.5	$0.00292	$0.00292
Sonnet 5.5	$0.00146	$0.00146
Haiku 4.5	$0.00073	$0.00073

Measured 11d ago against content hash 7acd287c85ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

WhatsAppToDiscord 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 11d 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.

AGENTS.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Notes (AGENTS.md)

This file is the quick map for coding agents working in WA2DC. It intentionally stays short; detailed guidance lives in docs/dev/.

Project snapshot

WhatsAppToDiscord (WA2DC) is a self-hosted bridge that mirrors WhatsApp chats into Discord.

WhatsApp transport: Baileys (@whiskeysockets/baileys)
Discord transport: Discord bot (discord.js)
Persistent state: local ./storage/
Runtime entry: watchdog runner src/runner.js

Fast start

Prereq: Node.js ^24.22.1 || >=26.12.1
Install: npm ci
Run bot: npm start
Run docs: npm run docs
Check docs: npm run docs:check
Lint: npm run lint (Biome)
Test: npm test
Bundle: npm run bundle
Build binary: npm run build:bin
Smoke boot: WA2DC_SMOKE_TEST=1 node src/index.js

Where the source of truth lives

Use these docs for detailed guidance:

docs/dev/README.md: developer docs index and ownership/freshness rules
docs/dev/runtime-and-layout.md: runtime model and repository map
docs/dev/storage-and-side-effects.md: disk formats, runtime files, and permission rules
docs/dev/bridge-constraints.md: anti-loop protections, JID/LID handling, routing constraints
docs/dev/change-playbooks.md: slash command and settings change procedures
docs/dev/testing-and-release.md: test matrix, CI, bundling/pkg constraints
docs/dev/security-and-privacy.md: secret handling and safety boundaries
Public operator configuration: docs/configuration.md

Critical guardrails

Follow the current SQLite-only storage contract in docs/dev/storage-and-side-effects.md.
Do not loosen explicitly enforced storage/download permissions (0700 dirs / 0600 files).
Avoid bridge echo loops; maintain sender-tracking protections.
Respect whitelist and one-way routing checks when touching message flows.
Do not hardcode PN vs LID assumptions for WhatsApp identifiers.
Keep Discord output within platform limits (message length / file size).
Use Biome for linting/format checks.
Treat out.js, out.cjs, and build/ as generated artifacts.
Never commit secrets (.env, auth state, tokens, session blobs).

Read the full file on GitHub · 80 lines

Changes

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.

11d ago Changed 7acd287c85ef
2mo ago First seen · 80 lines · 731 tokens per session scan A 4fe5cd56c9d6

Subscribe to this mod's changes

WhatsAppToDiscord AGENTS.md is an instructions file published in the GitHub repository arespawn/WhatsAppToDiscord (45 stars, last pushed 4d ago), licensed MIT. It adds 731 tokens to every session, about $0.0029 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-30.

automation baileys bot bridge discord discord-bot

WhatsAppToDiscord AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
WhatsAppToDiscord AGENTS.mdarespawn/WhatsAppToDiscord	Instructions file	45	4d ago	MIT	A	731	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

WhatsAppToDiscord: Instructions file for Codex