Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Haroon966/pinky-cursornpx agentmods add rules/haroon966/pinky-cursor/10-whatsapp-ownerWrote 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/rules/haroon966/pinky-cursor/10-whatsapp-owner)<a href="https://agentmods.dev/rules/haroon966/pinky-cursor/10-whatsapp-owner"><img src="https://agentmods.dev/badge/rules/haroon966/pinky-cursor/10-whatsapp-owner/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.
<a href="https://agentmods.dev/rules/haroon966/pinky-cursor/10-whatsapp-owner"><img src="https://agentmods.dev/badge/rules/haroon966/pinky-cursor/10-whatsapp-owner.svg" alt="Reviewed on agentmods" width="80" 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.00301 | $0.00301 |
| Opus 5 | $0.00151 | $0.00151 |
| Sonnet 5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
10-whatsapp-owner 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 9d 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
WhatsApp owner (ALWAYS ON when .pinky/whatsapp/owner.json exists)
Product path (phone without Cursor UI)
User keeps this running in their terminal:
export PATH="$HOME/.local/bin:$PATH"
bash .pinky/whatsapp/watch.sh
Flow: owner WhatsApp → Cursor CLI agent → reply on WhatsApp. PC stays on. IDE chat optional.
Doctor: bash .pinky/whatsapp/doctor.sh
Agent hard rules
- Never run
login.sh/watch.sh/ QR yourself — only give the command (QR must appear in user terminal). - Never enable Cursor MCP
whatsappwhilewatch.shuses the same.pinky/whatsappauth (causes 440 disconnect). - Ask/set owner number in
owner.jsonif missing. - Owner must text the linked (QR) WhatsApp account.
If user asks why no reply
- Is
watch.shrunning? doctor.shclean?- MCP whatsapp disabled?
- Correct chat (linked account)?
- Wait for
AGENT_DONE/AGENT_REPLIEDin watch terminal (can take ~1–2 min).
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.
- 9d ago First seen · 35 lines · 301 tokens per session scan A 9a3b3451a5a4
10-whatsapp-owner is a cursor rule published in the GitHub repository Haroon966/pinky-cursor (4 stars, last pushed 1mo ago), licensed MIT. It adds 301 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.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.