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/open-wa/wa-automate-nodejs/agents-mdgit clone --depth 1 https://github.com/open-wa/wa-automate-nodejsWrote 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/open-wa/wa-automate-nodejs/agents-md)<a href="https://agentmods.dev/instructions/open-wa/wa-automate-nodejs/agents-md"><img src="https://agentmods.dev/badge/instructions/open-wa/wa-automate-nodejs/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.01586 | $0.01586 |
| Opus 5 | $0.00793 | $0.00793 |
| Sonnet 5 | $0.00317 | $0.00317 |
| Haiku 4.5 | $0.00159 | $0.00159 |
Grade A, and why
wa-automate-nodejs 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 166 lines · 1,586 tokens per session scan A 1898d5b11c77
wa-automate-nodejs AGENTS.md is an instructions file published in the GitHub repository open-wa/wa-automate-nodejs (3,652 stars, last pushed 2d ago), with no licence file. It adds 1,586 tokens to every session, about $0.0079 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-30.
Other instructions, from other repositories
voltagent AGENTS.md
Instructions for VoltAgent/voltagent, covering voltagent, what is voltagent?, validating changes, important notes for ai agents and gotchas.
qq-music-api AGENTS.md
Instructions for Rain120/qq-music-api, covering 🤖 qq music api - ai agents 指南 (agents.md), 🎯 目录, 项目概览, 项目架构 and 1. 服务端主链路.
keryx CLAUDE.md
Instructions for actionhero/keryx, covering claude.md, project overview, monorepo structure, development environment and environment setup.
igniter-js GEMINI.md
Gemini CLI instructions for felipebarcelospro/igniter-js, covering 1. identity and profile, 2. about the igniter.js monorepo, 3. personality and communication, 4. lia's core responsibilities (the 4 pillars) and 5. technical guidelines and methodology.
igniter-js AGENTS.md
AGENTS.md instructions for felipebarcelospro/igniter-js, covering lia - ai agent for igniter.js, 1. identity & mission, core mission, key responsibilities and 2. project overview.
igniter-js writing-style.instructions.md
Instructions for felipebarcelospro/igniter-js, covering ✍️ unified documentation style guide (for llms & authors), 🎯 core style principles (applies to all documentation), 📘 documentation (docs): writing style, installation and quick start.