A plain directory for agent setups

Kitloom is a directory of reusable setups for AI coding agents. Developers already write good instructions, rules, skills, and workflows for their tools; they are scattered across repositories and hard to compare. Kitloom lists them in one place, shows what each one contains, and links to the ZIP.

It is free. Browsing and downloading need no account, and the site runs no analytics or advertising. You only sign in to publish your own setups. It is not a chatbot, it does not run agents, and it does not install anything for you.

A setup is a ZIP of configuration that changes how a coding agent behaves in a project:

• agent instructions and project rules
• skills, commands, and agent definitions
• hooks, workflow templates, and tool configuration
• the documentation and install notes that go with them

A setup can target one agent or several. Applications, model weights, datasets, and bare prompt collections are out of scope.

Each listing names the agents it supports. Kitloom currently recognises Claude Code, Codex, Cursor, Antigravity, Gemini CLI, GitHub Copilot, Windsurf, opencode, Aider.

Declared means the creator says the setup works with that agent. Tested means it was actually verified, and the listing shows that separately. Kitloom does not test packages itself, and a setup is never assumed to work with an agent it does not name. Agents change between versions, so check the date on a listing.

A setup is not passive text. Instructions can tell an agent to run commands, hooks run shell commands automatically, and MCP configuration starts programs. Treat a kit like code from a stranger.

• Read every file before copying it into a project. The listing shows the full file list.
• Extract into an empty folder first, never straight into a repository.
• There is no checksum to compare. The download is the ZIP of the exact commit Heddle checked, and its file name carries that commit's ID, so you can look it up in the repository's history on GitHub.
• Being hosted on GitHub, or listed here, does not make a package trusted.

Before every download, Heddle, Kitloom's pre-download check, reads the repository at its latest commit in your browser and reports warning signs: commands that run on their own, hidden or invisible instructions for agents, credential theft, disguised programs. It never runs anything, and it cannot prove a setup is safe; malware can be written to avoid it. Community listings appear as soon as their creator publishes them; they are not reviewed first. Maintainers can hide a listing after the fact. READMEs are displayed as plain Markdown with HTML removed and remote images blocked.

Every setup belongs to its creator. Listings show the licence the creator stated, or “No licence stated” when there is none. Without a licence you do not automatically have the right to reuse or redistribute someone's work, even when the repository is public.

Creator names, source repository links, and licence files are preserved as submitted. If you build on someone else's setup, keep their notice and follow their terms.

Keep your setup in a public GitHub repository, sign in, and fill in a short form: the repository link, a description, and the agents it is written for. Kitloom reads the README and file list from GitHub and links to the ZIP that GitHub builds from the repository. Nothing is uploaded to Kitloom.

Publish a setup

A community listing always downloads the current state of its repository, so pushing to GitHub updates what people get. To refresh the README and file list shown on Kitloom, or to change the description, edit the listing from your account. You can delete a listing at any time.

Because that ZIP follows the repository, it has no fixed checksum; the repository's commit history is the record of what changed. Kitloom does not show download counts, because it has no trustworthy way to count them.