Agent builds
Agent setups that ran. Fork one.
Short answer: download or fork real AI agent setups (CLAUDE.md files, Claude Code skills, prompts, MCP and swarm configs). Each build says what it does, which model it runs on, what a run costs and what it measured. Files are scanned so no keys get published.
Claude Code headless vs Claude Code inside throng
sqlswarm: a cheat-proof head-to-head for coding agents
A setup for comparing coding agents fairly: same goal, same model, same clock, and a read-only grader (SQLite's sqllogictest) scored from outside so no agent can raise its score by editing tests.
0 stars0 use it0 forks7 filesby @mattbusel
throng (Rust swarm harness), standalone or as an MCP serverthrong: a swarm of coding agents verified by real builds and tests
Run many coding agents on one repo in parallel. Every build and test goes through one shared, cached engine, and you only get back a change the real test suite passed. Works from Claude Code over MCP.
0 stars0 use it0 forks8 filesby @mattbusel
What makes a good build
- It ran on a real job, and the card says what it did with a number and a source (a receipt).
- Someone else can run it: the README says what to install, what to change and what a run costs.
- No secrets. Use placeholders like <YOUR_API_KEY>. Publishing is blocked if the scanner finds a key.