Instagram DM Auto-Reply 🐧

v2.js (Internal API) based. 0 browser snapshots, CDP cookie extraction → Instagram REST API direct calls.

Prerequisites

• - OpenClaw browser running (port 18800)
• Instagram tab open and logged in
• INLINECODE0 npm package (npm i -g ws or local)

Script List

Core Workflows

1. Check DMs

CODEBLOCK0

2. Read Messages

CODEBLOCK1

3. Reply

CODEBLOCK2

On API failure, returns JSON with method: "use_browser" + threadUrl → fallback to browser tool.

4. Notification Check (cron integration)

CODEBLOCK3

• - If new DMs: outputs INLINECODE8
• If none: outputs INLINECODE9
• Uses state file dm-state.json to prevent duplicates

5. Auto-Reply Flow

CODEBLOCK4

1. 1. Read dm-alert.json (created by dm-watcher)
2. Run security check on each DM
3. Return results: needs_reply / security_alert / INLINECODE14
4. AI generates replies for needs_reply DMs → send via INLINECODE16

6. Real-time Detection Daemon

CODEBLOCK5

Polls v2.js check every 15s. On new DM detection, writes dm-alert.json + Discord DM notification.

Security Check (Injection Rejection)

INLINECODE19's SECURITY_PATTERNS detects:

• - Prompt Injection: "ignore previous", "system prompt", "you are now", "act as", "pretend"
• Jailbreak Attempts: "override", "jailbreak", "DAN mode", "bypass"
• Sensitive Info Requests: "secret key", "private key", "seed phrase", "wallet address"
• Code Execution Attempts: "execute command", "run script", "eval(", "rm -rf", "sudo"
• Social Engineering: "simulation mode", zero-width characters

On threat detection → don't reply, return security_alert. Separate notification sent.

Cron Setup Example

CODEBLOCK6

Token Efficiency

• - inbox/check: exec 1 call (~500 tokens)
• reply: exec 1 call (~200 tokens)
• browser snapshots: 0

🐧 Built by 무펭이 — Mupengism ecosystem skill