Insurgently
Get involved · open source and the co‑op

Use the plugins, make them yours, or help build them.

Model Hub, Library Hub and Topic Map are free and open source, and Learning Editor is coming soon. There are four ways in, and you can start with any of them.

Join the co‑op

I want Insurgently to be worker-owned. The plan is a co‑op: a label and a company shared by the people who make the tools.

For now it's just me, so the co‑op is more plan than practice. That makes this the time to shape it. If you'd like to help build it, and one day share in owning it, write to me and say what you'd bring.

Email me about joining →

The wider collective lives at Insurgent Methods.

Make them yours

You don't need to write code to change how the plugins work for you.

Skills

A skill is a note in your skills folder that tells the model how you work. Give it a name, say when it helps, and write the steps. Model Hub picks it up without a restart. One with the same name as a built-in skill replaces it.

Tiers

Make tiers of your own, each a list of models from any provider you've added, and choose which tier each plugin's job runs on.

In Claude Code

Mark a skill mcp-prompt: true and it shows up as a prompt in Claude Code, Claude Desktop or Codex, next to your plugins' tools.

---
name: meeting-notes
description: Turn rough meeting notes into decisions, owners and next steps.
---

- Lead with decisions, then actions with an owner each.
- Keep the note's own wording for names and dates.
A whole skill, saved as SKILL.md in Skills/meeting-notes/.
Add your own skills →

Share a skill

Written a skill other people could use? I'd like to see it. Post it in the plugin's GitHub Discussions with the skill pasted in, or email it to me.

Say what it's for and a note you tried it on. The best skills are short and say plainly when they help, because that description is what the model reads when it picks one.

Code

Every plugin is on GitHub under the MIT license: read it, fork it, or ship your own version.

Fix or add something

Each repo has a ROADMAP.md of what's planned and a CONTRIBUTING.md on building it. Issues labeled help wanted are good places to start.

  1. Open an issue first, so we agree on the shape before you write it.
  2. Build it in a test vault. Lint, type checks and unit tests pass.
  3. If it touches Obsidian, run the end-to-end tests. They run in a sandboxed copy of Obsidian.
  4. Open a pull request that links the issue.

Build on them

Writing a plugin of your own? Model Hub gives it keys, tiers, limits and the ledger, and runs its tools. There are Developer docs for you and Agent docs for your coding agent, with an llms.txt it can read.

The libraries under the plugins are on npm too: @insurgently/obsidian-ui, the shared controls, @insurgently/text for finding and editing text, and @insurgently/retrieval for search.

Other ways to help

  • Tell me what broke. The plugins write a bug report you read in full before choosing where it goes, with keys, paths and names masked.
  • Tell me what you need. A post in GitHub Discussions or an email both reach me.
  • Leave a tip. Everything here is free; a tip pays for the next release.

Join

One list for everything here: an email when a plugin ships, plus the posts I write about these projects on brianspringer.com.

Want to help build this, or join the co‑op? Email me about joining →

Insurgent Methods is where we build at a different scale, to take on the biggest problems.