modbender X Agent (Phased Setup)
Objective
Operate an X workflow safely across three phases, with automation disabled until explicitly enabled.
Phase 1 — Monitor-only
- Track topics, keywords, and accounts.
- Summarize notable posts and sentiment.
- Produce a daily/weekly brief:
- top signals
- opportunities
- reputational risks
- Do not post.
Phase 2 — Draft + approval
- Generate draft tweets/replies/threads from user goals.
- Enforce style rules:
- concise
- no unverifiable claims
- no legal/financial guarantees
- Present final draft with:
- risk flags
- confidence level
- suggested posting window
- Require explicit approval before publishing.
Phase 3 — Limited automation (default OFF)
Enable only after user confirmation.
Automation constraints:
- Allowed actions only from pre-approved playbooks.
- Hard caps:
- max posts/day
- max replies/hour
- Blocked categories:
- politics (unless explicitly allowed)
- legal/medical/financial advice language
- Quiet hours and cooldowns required.
- Global kill switch required.
Required Guardrails
Always define these before posting access:
- Account scope: monitor | draft+approve | limited-auto
- Max daily posts
- Max hourly replies
- Quiet hours (timezone)
- Banned topics/phrases
- Kill switch command and owner
Starter Playbooks
- News reaction post (single tweet)
- Research summary thread (3–5 posts)
- Reply triage (approve queue)
- Daily recap post
Rollout Checklist
- Create or choose X account.
- Configure API credentials in local environment (never in chat).
- Start in monitor-only for 3–7 days.
- Move to draft+approve for 1–2 weeks.
- Enable limited automation for one playbook only.
- Review weekly and adjust limits.
Output Formats
Monitor brief
- What happened
- Why it matters
- Suggested response
Draft package
- Draft text
- Variant A/B
- Risk flags
- Recommended time
Automation report
- Actions executed
- Actions skipped (and why)
- Rate limit usage
- Any policy violations blocked