NoteMods, 132 Obsidian plugins built and released alone
NoteMods is my catalog of small Obsidian plugins, each built to do one job well. I built the factory that makes them, the release path that ships them and the site that sells them, and I run all of it alone.







The problem
Obsidian users ask for many small features that the app does not have. In October 2026, 14 of the 30 most voted feature requests on the Obsidian forum were about Bases, the new database view. Most of those jobs are too small for a company and too fiddly for a weekend.
One plugin is easy to make. A hundred plugins that each pass the directory review, keep their versions in sync and get fixes every week is a different problem. That needs a factory, not a single repo.
What I built
One private monorepo holds every product, 137 of them today. A command named fx makes a new plugin from a fixed template, runs its checks, exports a clean public repo and prepares the release. Shared code for the core logic and for the Pro license sits in two packages that every plugin uses.
Each plugin passes 6 gates before it can ship. They check the files and versions, the README and its screenshots, lint, tests and build, and every network host the code reaches. A separate review then reads the code. In the first waves those reviews found between 4 and 13 real defects in every build that had already passed its own tests.
AI coding agents do the build work in parallel lanes. I pick the ideas, read the reviews and approve each live release. Nothing goes public without that step.
Release without clicks
A change lands with a version note. CI opens a version pull request, then pushes a tag to the public plugin repo. That repo builds main.js from the committed source, attests it and publishes the release, never as a draft.
A nightly job checks that the version the directory shows matches the latest tag. A weekly job flags any plugin with no release in 7 days. 17 negative controls break the release gate on purpose to prove it still fails when it should.
The site
notemods.com is a static site that a Python build makes from live data. Each morning at 06:15 a scheduled run fetches the directory facts and GitHub releases, commits the data, builds into a side folder and swaps it in only when every page passed. It then runs 14 gates, uploads to Cloudflare Pages and checks the live site.
The site has 289 URLs, with a page for each of the 132 plugins, 106 guides and 41 theme pages. It has no backend, a strict content security policy and no analytics until the visitor allows them. When a gate fails or the disk runs low, the run stops and the old site stays live.
Result
132 plugins are listed in the Obsidian directory, all with Excellent health. The first went live on 10 October 2026. Together they have 13,231 downloads across 645 released versions.
Most plugins are small, and the median has 54 downloads. The top one, Footnotes in Callouts and Tables, has 849. Core features stay free and MIT licensed. One GitHub sponsorship turns on Pro in each plugin that has it.
Evidence
notemods.comThe live catalog, with a page for each pluginObsidian community profile132 plugins listed under my accountBases Freeze PanesOne public plugin repo, with its release workflowFootnotes in Callouts and TablesFootnotes inside callouts and tables, 849 downloadsSearch OperatorsDate, link and tag search, 679 downloadsObsidian download statsThe public file the download counts come from
Own product. Download and version counts come from the Obsidian community stats file on 5 November 2026. The factory and site repositories are private. All 132 plugin repositories are public.