cursorrules

A set of rules for an AI assistant working on a codebase connected to WhatsApp. The rules say to ask for clarification through WhatsApp instead of waiting for terminal input.

In plain words
What is it for?
Use it to define how the assistant asks questions and handles replies during development.
Why use it?
It keeps work moving when the assistant needs a decision, requirement, approval, or credential.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/dudu1111685/hermes_mcps/cursorrules
Clone the repo
git clone --depth 1 https://github.com/dudu1111685/hermes_mcps

Made for: Cursor.

Per session 297 This file is loaded in full into every session.
When invoked 297 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00297 $0.00297
Opus 5 $0.00148 $0.00148
Sonnet 5 $0.00059 $0.00059
Haiku 4.5 $0.00030 $0.00030

Measured 2d ago against content hash 165a436aa5a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursorrules 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 2d 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.

.cursorrules · 57 lines

What it actually says

AI Assistant Rules for WAHA MCP

Core Instruction

When working with this codebase and you need user input, clarification, or approval:

DO NOT stop and wait for console input.

INSTEAD: Use the ask_user_via_whatsapp MCP tool to ask questions and continue working.


Default Workflow

  1. Hit a question or need clarification
  2. Call ask_user_via_whatsapp({ question: "Your question here", chatId: "[email protected]" })
  3. Wait for reply (tool is blocking)
  4. Parse the answer
  5. Continue working

Example

// ❌ Don't do this:
// "I need to know if you want error logging. Please tell me."

// ✅ Do this:
const answer = await ask_user_via_whatsapp({
  question: "Should I add detailed error logging? (yes/no)",
  chatId: "[email protected]",
  timeoutMinutes: 20
});

if (answer.toLowerCase().includes("yes")) {
  // Implement logging
}
// Continue working

When to Use

  • Architectural decisions
  • Missing requirements
  • Ambiguous specs
  • API credentials
  • Any blocking question

Goal: Keep working autonomously. Use WhatsApp to unblock yourself.


See CLAUDE_CODE_INSTRUCTIONS.md for detailed examples and best practices.

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.

  1. 2d ago First seen · 57 lines · 297 tokens per session scan A 165a436aa5a2

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository dudu1111685/hermes_mcps (5 stars, last pushed 2d ago), licensed MIT. It adds 297 tokens to every session, about $0.0015 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.