Free .md downloads, page 6
Starter playbooks, templates and prompt packs you can download in full, no signup. The free tier of the product line.
Run a multi-agent team on a ledger that only marks work done when the receiver confirms
YC Labs ran 50 agents in a Minecraft survival world and 10 against 10 Claude and GPT teams in Bed Wars. The colony's food ledger learned the hard way that a tool's 'delivered' report is not proof: a tossed ration was picked up by the wrong agent, so the rule became named chests and 'served only after the recipient confirms'.
Write down your own call before your agent argues for one
Anthropic gave 50 professional analysts Claude Code with a hidden, coin-flip lean on four analysis choices. They went with the agent's lean 86% of the time, 77% later reused its arguments, and only 15% credited it. A cheap guard: record your choice and reason before you ask the agent, then compare.
Have Claude write an Aseprite extension that paints isometric worlds from brushes
A game artist tired of hand-drawing hundreds of grass tiles spent a couple of weeks directing Claude to write the Lua for an Aseprite extension: SimCity-style brushes for hills, paths, ponds and trees that redraw only the area touched, with trees grown in 3D first and drawn back to pixels with the same camera.
Make a small browser horror game in a weekend with one style line per area for consistent 3D models
A non-coder made a six-minute first-person browser horror game in 52 hours: 150 models from Tripo for about $27 including retries, sound from ElevenLabs and code from Claude. The trick that kept a hundred separate generations looking like one house was one written style line per floor appended to every prompt.
Turn an official public source into a versioned git history, one agent session per source
A builder used separate Claude Code sessions, one per country, to download every version of each law from official publishers and write it out as git history with one commit per change on its in-force date. Each session checked robots.txt and the terms first, and two independent builds had to match hash for hash.
Sandbox your MCP servers too, because the agent's sandbox may not cover them
A write-up on r/mcp points out that Claude Code's and Codex's own docs say local MCP servers run as ordinary processes outside the agent's sandbox. It walks through a recent paper on narrow tools being steered into reading files outside their job, and gives concrete container and environment settings.
Design MCP tools and errors so the model's next call is the right one
Two MCP server builders shared numbers and rules from real use. A Photoshop server with 83 tools kept model-caused bad calls to about 1 in 290 by making every tool distinct, folding variants into parameters, returning errors that list allowed values, and giving the model a short capability map. A design editor server added batch writes with one undo step and idempotency keys that report stale after an undo.
Extension Lockfile: an allow-list check for your editor extensions (free sample)
From Extension Lockfile: the quick checks for the 2026-10-29 Claude Code extension incident, pointing to the vendor's notice, five habits for editor extensions, and a read-only script that flags extensions not on your allow list, at an unapproved version, or installed in the last few days.
Bug Report Your Agent Can Fix (free sample)
From the $14 pack: the capture checklist, the report template, five rules and the reproduce-first prompt.