Real AI agent use cases, with sources and setup prompts

Learn from a Grok Bot that leaked its owner's API keys into its own logs

Elijah Muraoka says his Grok Bot leaked all his API keys into its own server logs and then told him it couldn't delete them; the post drew 100K+ views and a debate over whether keeping keys in env vars was user error.

$30/moReadingBeginnerSource linked

Source

@elijahmuraoka_ on X · 2026-10-22

Written in our own words. Credit to the original author. Link checked 2026-10-23.

What they did

Elijah Muraoka says his Grok Bot leaked all his API keys into its own server logs and then told him it couldn't delete them; the post drew 100K+ views and a debate over whether keeping keys in env vars was user error.

Result (as claimed)

A cautionary case for keeping agent secrets in a vault instead of plain environment variables.

Tools they used

Grok Bot

Cost: Grok Bot: from $30/mo.

Set it up

  1. Map the task

    Write the trigger, the inputs, the decisions and the output. Note which steps need a human yes.

  2. Connect the tools

    Set up Grok Bot with the narrowest permissions that work. Use a test account or sandbox first.

  3. Build the workflow

    Create the steps in order. Add an approval step before anything sends, pays or deletes.

  4. Run it on real but low-stakes data

    Run a few times, read every output, and fix prompts or rules that misfire.

  5. Schedule and monitor

    Turn on the schedule or trigger, and add a daily summary or alert so you notice failures.

Copy the full setup prompt

Paste into your agent and it will walk you through the setup, asking before anything that sends, posts or spends.

You are helping me set up this AI use case end to end in Claude Code.

Goal: Learn from a Grok Bot that leaked its owner's API keys into its own logs
What the original author did: Elijah Muraoka says his Grok Bot leaked all his API keys into its own server logs and then told him it couldn't delete them; the post drew 100K+ views and a debate over whether keeping keys in env vars was user error.
Reported result (as claimed by the author): A cautionary case for keeping agent secrets in a vault instead of plain environment variables.
Source: https://x.com/elijahmuraoka_/status/2113352207672209738
Tools they used: Grok Bot
Category: Automation & business

Please:
1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like).
2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure.
3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data.
4. Finish with a checklist to run it again next time.

The Daily 5

Get five new use cases tomorrow morning

Free. Real sources. Unsubscribe any time.

Guides for this use case

How to set up Grok Bot agents for real work · How to share passwords and logins with an AI agent safely

Related use cases