unknownnodeee @unknownnode404

THIS IS THE F*CKING PROMPT YOUR GROK BOT BILL NEEDED Grok Bot can run your jobs on a clock all day, and almost everyone sets that clock to the fastest one it allows. The idea: the clock only wakes a cheap check, the check reads one hash, and the real run starts only when that hash moved. Same reaction time, 89% less money, because most wakes stop at the check and never turn into a full run. You just tell Grok Bot this: audit my routines, check first here's the split: → a 5-minute clock wakes 8,640 times a month, about $397 for one routine → a read-only check reads one hash, count or date and stops, 2K tokens, $0.0043 → a full run of 20K tokens starts only when something actually changed → one fast routine with a check lands near $45 a month it still stops you at three moments: → anything that sends, posts, pays or deletes waits for your approval → a night run, approvals expire in about 10 minutes, so it ends at a draft → a new routine, test runs are real runs, so it runs on a copy first The clock wakes. The hash decides. You approve. the full tree > every routine names one signal that proves a change > a webhook, Slack, GitHub or email event replaces the clock where it can > the slowest schedule that still works covers the rest > a read-only check runs before every full run > nights end at a Custom Rule or a draft for breakfast > one csv line per run, because the app keeps only the last 20 paste the tree and this prompt into Grok Bot ↓ "Rebuild my routines around this tree: 1. List every routine with its schedule, trigger and monthly cost. 2. Swap the clock for an event trigger wherever a webhook, Slack, GitHub or email event exists. 3. Put a read-only hash check in front of every routine that keeps a clock, and only start a full run on change. 4. Replace every night step that waits for me with a Custom Rule or a draft. 5. Log every run to routines/log/[name].csv and flag anything that is 99% no_change every Monday. Show me the old and new monthly cost side by side. Nothing changes until I say go." ↳ docs.x.ai/grok-bot/get-s… one routine, $397 down to $45. run it once and look at your own number.

Gipp 🦅 @gippp69

2 weeks ago

x.com/i/article/2108…

76 59 545 1.3M 1K

STOP CLICKING YES ON EVERY F*CKING CLAUDE CODE PROMPT Anthropic built the fix right into Claude Code and most people never open it. The idea: Claude proposes every call, your shell checks it for free, and three lists decide who gets to say yes. Way fewer prompts and zero risky surprises, because the boring calls run alone and the dangerous ones never run at all. You just type this in Claude Code: /permissions here's the split: → hooks fire before and after every tool call and run as plain shell, no model inside → a PreToolUse hook that exits 2 kills the call before a single rule is read → deny is checked first, ask second, allow last → allow covers the boring stuff, so you stop clicking yes 40 times a session the hooks earn their keep at three moments: → before a call, block edits to .env, secrets/ and migrations/ → after an edit, run the formatter on the file Claude touched → before Claude says done, run the test suite Hooks check. Rules sort. You sign off. The AI coworker crowd in Slack figured out the same thing. A free script checks first, the agent only wakes on a real change, and every customer email waits for a tap. In my Viktor breakdown that one move took 4 jobs from 211,000 credits a month to 35,800. the full tree > Claude runs the session and proposes every tool call > PreToolUse blocks protected paths with exit 2 > deny rules catch rm -rf, secrets and payments first > ask rules hold git push and installs for your tap > allow rules run reads, greps and tests with no prompt > a Stop hook runs the suite before anything is called done paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Write .claude/settings.json with deny rules for rm -rf, .env and anything with credentials, ask rules for git push and package installs, and allow rules for reads, greps and my test command. 2. Add a PreToolUse hook that exits 2 on writes to .env, secrets/ and migrations/. 3. Add a PostToolUse hook that formats every file you edit. 4. Add a Stop hook that runs the tests and keeps you working if they fail. Show me every change as a diff first. No edits until I say go." ↳ code.claude.com/docs/en/hooks your next session asks you 3 times instead of 40. try it once and you won't go back.

Gipp 🦅 @gippp69

2 days ago

x.com/i/article/2112…

31 5 87 239K 69

x.com/i/article/2112…

your Grok Bot is f*cking robbing you every 5 minutes and you're thanking it 8,640 wakes a month. same page. same answer. "nothing new". $397 the bot was fine. the clock was the problem so I rebuilt it the boring way. events wake it, one hash decides, a full run only when something actually moved here are 10 GitHub repos I stole the pieces from: 1. ntfy send a push to your phone with one curl. perfect for "something changed" and silence for everything else github.com/binwiederhier/… 2. uptime-kuma self-hosted monitor with push and keyword checks. watches the thing so your bot doesn't have to github.com/louislam/uptim… 3. diun tells you when a docker image actually updates. a clean example of reacting to a version, not a timer github.com/crazy-max/diun 4. inngest event-driven functions with retries and sleeps built in. the mental model every routine should copy github.com/inngest/inngest 5. windmill turn scripts into webhooks, flows and schedules in one place. great for wiring a trigger in front of Grok Bot github.com/windmill-labs/… 6. trigger.dev background jobs that run on events, with long waits that don't cost you while they wait github.com/triggerdotdev/… 7. svix-webhooks send and receive webhooks properly, with retries and signatures. stop polling the APIs that can ping you github.com/svix/svix-webh… 8. smee.io forwards webhooks to your local machine. test a GitHub trigger in 2 minutes instead of setting a cron github.com/probot/smee.io 9. gocron a tiny scheduler for Go. when you really need a clock, at least pick the slowest one on purpose github.com/go-co-op/gocron 10. kestra event-driven orchestration with real run history. the opposite of an app that forgets after 20 runs github.com/kestra-io/kest… the 3 questions I ask before any routine gets a clock now > what proves it changed? > who can tell me first, a webhook or a timer? > what happens at 3 a.m. when nobody taps approve? if the answer is "nothing changed", the bill should be nothing too same bot, same model. $397 became $45 ↓

Gipp 🦅 @gippp69

2 weeks ago

x.com/i/article/2108…

76 59 545 1.3M 1K

stop telling Grok Bot to "check every 5 minutes" that one line wakes your routine 8,640 times a month. about $397, mostly for nothing the fix is boring. read one signal, react only to change, and let real events wake the bot I pulled 10 GitHub repos that do exactly that part well: 1. changedetection.io watches any page and only fires when the content actually changes. perfect model for a "did anything move" check github.com/dgtlmoon/chang… 2. urlwatch diffs web pages from the terminal and reports only what changed. tiny, scriptable, easy for Grok Bot to copy the idea github.com/thp/urlwatch 3. webhook a small server that runs your commands when an HTTP request hits it. the cleanest way to replace a clock with an event github.com/adnanh/webhook 4. n8n workflow automation with webhook, cron and app triggers. good for wiring Slack, GitHub and email into one place github.com/n8n-io/n8n 5. healthchecks cron monitoring that alerts you when a job stops checking in. you find out a routine died before the bill does github.com/healthchecks/h… 6. APScheduler python scheduling with cron, interval and one-shot triggers plus persistent job stores github.com/agronholm/apsc… 7. robfig/cron the go cron library half the internet runs on. read it once and you stop writing */5 by reflex github.com/robfig/cron 8. apprise one library for alerts to Slack, Telegram, Discord, email and 100+ more. send a note on change, nothing on no_change github.com/caronc/apprise 9. huginn self-hosted agents that watch sources and act on events. the original "bot that wakes on change" github.com/huginn/huginn 10. temporal durable timers, retries and long-running workflows that survive crashes. what a night run should feel like github.com/temporalio/tem… instead of > check every 5 minutes > keep an eye on it > wait for my approval give Grok Bot > a webhook trigger > an hourly schedule > 1 hash check, 2K tokens > a draft at night, never wait > 1 csv line per run less clock, more signal that's when the bill stops being a guess ↓

Gipp 🦅 @gippp69

2 weeks ago

x.com/i/article/2108…

76 59 545 1.3M 1K

GROK BOT JUST KILLED 15 USELESS RUNS BEFORE THEY BURNED MORE TOKENS someone built a routine desk that finally treats AI wakeups like something you should pay attention to. 27 checks. 15 stopped early. 0 expired approvals. the whole setup runs on 6 rules. here's the split: → CHECK FIRST compares the latest hash and exits if nothing changed → SLOWEST CLOCK moves unnecessary 5-minute checks to hourly → TRIGGER > CLOCK uses webhooks, Slack and GitHub events → NIGHT RULE saves sensitive work as drafts → OWN LOG records every decision in CSV → TEST ON A COPY keeps experiments away from live workflows the interesting part is what happens when a routine wakes up. → Price Check finds the same hash and stops → RSS Hash sees no new posts and skips execution → Invoice Chase at 03:00 becomes a morning draft → Inbox Count moves from 8,640 monthly checks to an hourly schedule no expensive investigation when the answer is already known. paste this into Grok Bot ↓ "Rebuild my routines around these 6 rules: Check for meaningful changes before starting expensive work. Replace excessive polling with slower schedules or supported event triggers. Keep overnight actions requiring approval in draft mode. Log every run, including skipped checks, failures and estimated costs. Test modifications on safe copies before touching live workflows. Review execution history and identify wasted calls. Show the proposed changes before enabling anything." the dashboard is a demonstration, not a measured production benchmark. 27 wakeups look impressive on a screen. i'm far more interested in the 15 that knew when to stop. ↳ x.ai/bot/guides/gro…

Gipp 🦅 @gippp69

2 weeks ago

x.com/i/article/2108…

76 59 545 1.3M 1K

THIS IS A F*CKING 38-JOB COMPANY INSIDE ONE GROK BOT someone finally organized AI automation like an actual business instead of a bunch of agents running around with no purpose. 38 routines. 8 trigger groups. one bot. and every job has its own reason to wake up. the setup is surprisingly clean: → WEBHOOK runs 7 jobs for deployments, payments, orders, refunds and incoming leads → HOURLY + CHECK handles 6 monitors covering prices, repository changes, inbox counts and competitor pages → DAILY 08:00 delivers 5 scheduled tasks for morning briefs, metrics, calendar preparation and invoices → SLACK runs 5 workflows for standups, thread summaries, support and mentions → GITHUB takes care of 5 engineering jobs, including PR reviews, issue labels, CI checks and dependency changes → EMAIL manages 4 jobs for invoices, lead drafts, receipts and newsletters → NIGHT RULE keeps 3 overnight workflows separate from actions that need human approval → MONDAY 09:00 runs 3 maintenance tasks: audit.py, Log Rotator and Cost Report the last one is my favorite. every monday, Cost Report tells you what each routine cost over the previous week. you can finally see which automations are useful and which ones are just burning money. here's how i'd organize the whole system: → events for things that need immediate attention → hourly checks for sources that change frequently → daily schedules for predictable reporting → night rules for work that shouldn't wake you up → weekly audits to catch waste and failures no need to turn every little task into another expensive AI session. the important part is assigning the right trigger before you enable anything. paste this into Grok Bot ↓ "Design a routine workspace with 8 trigger groups. 1. Organize my workflows across webhooks, hourly checks, daily schedules, Slack, GitHub, email, overnight rules and weekly maintenance. 2. Give every routine one specific responsibility and an expected output. 3. Use event triggers when supported instead of unnecessary scheduled polling. 4. Skip expensive processing when the underlying information hasn't changed. 5. Keep sensitive actions in draft mode until I approve them. 6. Create a Monday 09:00 Cost Report showing execution counts, failures, estimated spending and routines worth pausing. Show me the entire configuration before enabling anything." the dashboard uses 38 of Grok Bot's 50 available routine slots. but filling every slot isn't the goal. i'd rather have 12 jobs that finish real work than 50 agents competing to write the same useless status update. ↳ docs.x.ai/grok-bot/skill…

Gipp 🦅 @gippp69

2 weeks ago

x.com/i/article/2108…

76 59 545 1.3M 1K

grok bot can run an entire AI team while you sleep. the scary part is how much money that team can waste doing absolutely nothing a routine checking every 5 minutes wakes up 8,640 times a month. in this example, running the full AI task every time costs $397/month. checking for changes first brings the modeled bill down to $45. that's nearly 89% less. here's the 8-bot setup i'd actually want: bot 1 → Trigger Scout watches for real changes instead of firing off expensive requests on a timer bot 2 → CI Watcher checks builds and pull requests, only investigating when a status changes bot 3 → Price Tracker compares competitor pages and reports new prices, not the same numbers twice bot 4 → Inbox Desk sorts incoming emails and prepares replies without sending anything risky bot 5 → Deploy Guard catches failed deployments and collects logs before anyone gets involved bot 6 → Night Shift handles safe tasks overnight and leaves sensitive decisions waiting for approval bot 7 → Run Logger records every execution, skipped check, failure and reason behind it bot 8 → Monday Auditor goes through the history and finds routines that are quietly eating the budget you don't need all 8 constantly thinking. most of the time, they should be waiting for a reason to start. the workflow is ridiculously simple: event → change check → relevant agent → safe execution → log → weekly audit the $397 and $45 figures are illustrative API estimates, not Grok Bot subscription prices. imagine opening your laptop on monday and finding completed work instead of a graveyard of expired approvals. that's the kind of AI employee i'd keep on payroll. the ones asking "anything new?" every 5 minutes can pack their desks.

Gipp 🦅 @gippp69

2 weeks ago

x.com/i/article/2108…

76 59 545 1.3M 1K

call me insane but grok bot just made me realize how stupid most AI automation actually is 8,640 runs a month just to check if something changed. grok bot + smart triggers could cut that down without missing the work that matters. event → change check → grok bot → approval → audit no change? no run. 3 a.m. approval? leave a draft. something breaks? wake the right routine. give grok bot this exact workflow. let the bots work. not the clock.

Gipp 🦅 @gippp69

2 weeks ago

x.com/i/article/2108…

76 59 545 1.3M 1K

SpaceXAI engineer on the Grok Bot team, Lauren Tan: "if you don't have trust and you try to spawn 100 sub-agents or cloud agents, you're going to quickly find that you're just going to get a ton of slop pull requests and a bunch of regressions" most people scale agents first and fix the mess later. she does it backwards: Verification Skills → Agent Checks Its Own Work → Trust → 100 Parallel Agents → Whole Team Ships in this 37-minute talk, she shows how agents run the app themselves, take traces, find the hotspots and "hill climb to a better performance in our application automatically." no babysitting every diff. no wall of slop PRs. more useful than any agent course you'll pay for this year. bookmark it and watch it now. then read my full breakdown below on what Grok Bot routines really cost ↓

Gipp 🦅 @gippp69

2 weeks ago

x.com/i/article/2108…

76 59 545 1.3M 1K

SpaceXAI engineer at Grok Bot Galaxy: "every 3 a.m., my bot will start a research cloud agent across the whole surface of our monorepo. And when I wake up, I just have a set of PRs available." The setup is basically a 24/7 agent team that only pings a human when it matters. In this 21-minute workshop, you see how the bots handle research, CI fixes and on-call while nobody is watching. This is more useful than 10+ surface-level Grok Bot / agent engineering guides. Watch the workshop, then read the article below ↓

Gipp 🦅 @gippp69

2 weeks ago

x.com/i/article/2108…

76 59 545 1.3M 1K