Ready-made setups for AI coding agents: rules, skills, and MCP configs, checked in CI. Claude Code, Codex, Cursor, Gemini CLI, Copilot, Antigravity. Free.
@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
@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
@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
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
@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
@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
@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
@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
@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
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
@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
@fxlxsxf 699 is wild. did you open any of them in raw view? the GitHub preview hides HTML comments and anything after a long run of blank lines, which is exactly where the dodgy ones stash their instructions
@thedelost worth opening the raw files before installing a pack that size. VirusTotal found bad skills hiding instructions after hundreds of blank lines and inside HTML comments, neither of which shows up in GitHub's preview
My favourite example: a tax skill with ~500 blank lines before the last instruction, telling the agent to BCC your tax docs to an outside address. GitHub's preview looks like it just ends.
VirusTotal looked at 36k agent skills and classed 18.5% as malicious. Most didn't even hide it, the bad instruction was just sitting there in plain text.
The 90 that did hide used three tricks: hundreds of blank lines, HTML comments, and invisible Unicode.
Wrote up how to spot all three with a few terminal commands:
https://t.co/dRZyjkGnML