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.
npx agentmods add instructions/i-no-one/baileys-agent-kit/agents-mdgit clone --depth 1 https://github.com/I-No-oNe/baileys-agent-kitWrote 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/i-no-one/baileys-agent-kit/agents-md)<a href="https://agentmods.dev/instructions/i-no-one/baileys-agent-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/i-no-one/baileys-agent-kit/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 | $0.00364 | $0.00364 |
| Opus 5 | $0.00182 | $0.00182 |
| Sonnet 5 | $0.00073 | $0.00073 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
baileys-agent-kit 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 5d 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
Agent guide
Use the baileys-agent-kit MCP server when available. It exposes capability discovery, diagnostics, QR or one-time-code pairing, bounded recent-account prefetching, and validated WhatsApp execution.
- Call
whatsapp_capabilitiesonce to learn the current action schema. - Call
whatsapp_doctorbefore pairing or executing if account state is unknown. - If unpaired, call
whatsapp_pair_start. By default, show its PNG image content to the user. If the intended account owner asks for phone-number pairing, pass their internationalphoneNumberand privately show the returned one-time code. Callwhatsapp_pair_statusif the QR/code or connection state is unclear. - Call
whatsapp_executeonly for actions the user explicitly authorized. Sending messages and changing groups are external side effects. - Preserve recipient allowlists, rate limits, group-admin opt-in, and circuit-breaker errors. Never retry around these protections.
- Use
list_recent_accountsonly when recent-chat discovery is needed. Set the smallest usefulprefetchSecondsvalue (0–30); other actions deliberately skip history prefetch for speed.
Never print Redis tokens, broker secrets, raw authentication state, raw QR payload text, or pairing codes in public logs. A QR image, one-time code, or private broker URL is temporary authentication material; show it only to the intended account owner.
Shell-only agents can use baileys-agent describe, doctor, pair, and run. QR pairing writes a mode-0600 PNG in the system temporary directory and prints its absolute path so the agent application can preview it. Phone-number pairing uses baileys-agent pair --phone-number +15551234567.
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.
- 5d ago First seen · 15 lines · 364 tokens per session scan A a57e3d55911e
baileys-agent-kit AGENTS.md is an instructions file published in the GitHub repository I-No-oNe/baileys-agent-kit (2 stars, last pushed yesterday), licensed MIT. It adds 364 tokens to every session, about $0.0018 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
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.
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).
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.
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).