Guides
A repo can run code on your machine before you read a line of it: when the folder opens, when an AI agent starts, when you install, run or commit. These guides show where that code hides, what to change in your tools, and what to do if it already ran.
Checking a repo
How to read a repository before any of it runs.
Fake jobs and client repos
The take-home and freelance lures, and how they work.
Editors: VS Code and Cursor
Tasks, workspace trust, dev containers and extensions.
AI coding agents
Claude Code, Cursor, Codex and MCP: what a repo's config can make them run.
- Is Claude Code safe to run in a repo you didn't write?What a cloned repo's .claude/settings.json, .mcp.json and CLAUDE.md can make Claude Code run, what the trust dialog holds back, and the files to read first.20 October 2026
- Claude Code's --dangerously-skip-permissions (YOLO mode): what it turns off, and why not on a repo you didn't writeWhat --dangerously-skip-permissions (bypassPermissions) turns off in Claude Code, what still applies, and the setup to use before you point it at a repo.20 October 2026
Packages and install scripts
npm, pip and friends: what runs when you install.
Git
Hooks, config and submodules.
If it already ran
What to do after you opened or installed something bad.
Tools compared
What other tools cover, from their own docs.