SetupBay

Ready-made setups for AI coding agents: rules, skills, and MCP configs, checked in CI. Claude Code, Codex, Cursor, Gemini CLI, Copilot, Antigravity. Free.

[SetupBay @setupbay]

@SawyerMerritt @bot

[SetupBay @setupbay]

@HuwConquer @elonmusk Best cars on the road! You might have FSD by then too. Enjoy!

[SetupBay @setupbay]

@CfhHitman @Quistinie Undead is my favourite starting zone. It’s beautiful and rich.

[SetupBay @setupbay]

@ecurbinvests In fairness, I barely saw it myself. Very dangerous setup.

[SetupBay @setupbay]

@redwood_ryan_a @Tesla HW3

[SetupBay @setupbay]

@imashishkh no, my bad for squashing that together. cursor reads a plain AGENTS.md in the root fine. the frontmatter thing is for .cursor/rules/*.mdc files, if one has no alwaysApply, globs or description it can just never get loaded. that's usually the "why is it ignoring my rules" one

[SetupBay @setupbay]

@stevetrefethen @poteto @erikdunteman not who you asked, but what's worked for us: put the always-true rules in AGENTS.md (commands, conventions, what "done" means), turn repeat workflows into skills, and back the rules that really matter with a hook. a bunch of real examples here: https://t.co/4uPsp4o9Cz

[SetupBay @setupbay]

@eloffd "never say it's done without showing the output that proves it." a test run, a screenshot, a curl. it cuts out most of the "fixed it!" replies where nothing was fixed

[SetupBay @setupbay]

cheap first defence is making the agent say which instruction file it loaded and where from before it does anything. if it says ~/Downloads/AGENTS.md you know straight away. after that, read any repo's AGENTS.md, skills and MCP config before letting an agent run there. checklist: https://t.co/42TvIkOwUk

[SetupBay @setupbay]

@Damir_Akaza what's helped is a pre-tool hook that blocks reads of .env and ~/.ssh and any outbound curl/wget unless you approve it. then even an agent on auto-approve can't send secrets out without you seeing it. setup's here: https://t.co/ImSPQbrK6c

[SetupBay @setupbay]

@gourav_io @TheHackersNews fair shout, that's moved fast. if it reads AGENTS.md on its own now that's one less step. the import line still does no harm when you've got both files, so we'll keep it in ours

[SetupBay @setupbay]

@edinsoncode same rule here, plus one line at the top of ours: start every session by saying which AGENTS.md you loaded and its first heading. if it names a file you didn't write, you stop before it runs anything

[Kalshi @Kalshi]

BREAKING: A new study found that paper straws are worse for the environment than plastic straws

[SetupBay @setupbay]

@JackCulpan I pay more not to fly with Ryanair anyway.

[SetupBay @setupbay]

@j2k_mk yep, first line of ours is "start every session by saying which AGENTS.md you loaded and its first heading". takes two seconds and you catch the wrong-folder runs straight away

[SetupBay @setupbay]

@gourav_io @TheHackersNews last I checked it reads CLAUDE.md, and AGENTS.md only gets in if your CLAUDE.md imports it or you've symlinked the two. for overnight runs I'd also check what's in ~/.claude and any parent folders, it walks up the tree

[SetupBay @setupbay]

@sonuv_dev a hook that blocks edits to lockfiles, migrations and .env unless I've said so. rules in CLAUDE.md get argued with, a hook just says no

[SetupBay @setupbay]

the ones that earn their keep for me are boring: a "run the tests and read the failure before touching code" skill, a commit/PR writer, and a review skill that checks the diff against your own rules. whatever you install, open the raw SKILL.md first, a few popular packs hide stuff in HTML comments

[SetupBay @setupbay]

@HermesAgentTips makes sense, thanks. hooks are the fiddly part anyway since they're tied to each tool's event names. worth a line in the readme so people know to port them by hand