Add a tool

This is shared infrastructure for the movement, and it gets better every time someone adds the tool they wished they’d found. Best of all, the gate is mechanical, not social — no cliques, no gatekeeping: a tool gets in if it passes the enforcement engine and is described accurately. “Is this dependency clean?” is already answered by CI, so a human’s only job is “does this fit, is it described honestly.” Your contribution helps the next organizer who needs it.

Add a tool

Issue template

The lowest-friction path. Open a New tool issue and fill in the dependency name, ecosystem, primary-source URL, and license claim. The template is structured so a maintainer (or an agent skill) can turn it into a verified entry.

Open a new-tool issue →

CMS (no Git)

For non-developers, the site ships a Git-based CMS (Sveltia) at /admin/. Sign in with GitHub, fill in the fields, and it opens a pull request for you — the same PR a developer would open, so the same CI runs.

Pull request

Generate an entry with the catalog tooling and open a PR:

# add your tool to data/seed-catalog.json, then:
npm run data:fetch          # fetches license @ commit, maintenance, metadata
npm run enforce             # must pass
npm run check               # astro schema validation

What CI checks before a merge

1. astro check — your entry’s frontmatter matches the schema (a verified entry must pin a license commit; a blocked entry must say why).

2. Enforcement Layer 1 — the tool isn’t owned by an excluded organization.

3. Recipe contract (if you added a recipe) — it targets a provider_agnostic entry and actually excludes the LLM providers.

4. Dead-link check — your primary-source and license URLs resolve.

The engine is not advisory

If your contribution introduces a dependency on Meta, OpenAI, or xAI — directly or transitively — the PR fails and cannot merge. That’s a feature. Use a provider-agnostic recipe if the tool legitimately supports a permitted provider.

Build with the skills and archetype

The repository also ships reusable assets for building with an agent:

Agent skills catalog-entry-author, license-watcher, maintenance-checker — as Claude Code skills and Goose recipes. Each runs the enforcement engine before committing.

Spec Kit archetype A scaffold for a Nostr + AT Protocol web client whose constitution forbids excluded dependencies.

See the quickstart for using these with Goose or Claude Code, and Contributing guidelines for the full flow.

Maintenance & governance

How the catalog stays current, the review SLAs, and how it’s designed to outlast its first maintainer are documented in About & maintenance.