Open-source Claude Code plugins. Currently dynamisk-rettsstat; more are added when they are good enough.
Find a file
Kjell Tore Guttormsen c41b3008f2
chore(catalog): bump dynamisk-rettsstat v0.1.1 -> v0.1.2
dynamisk-rettsstat v0.1.2 — release. Catalog ref now pins the v0.1.2 tag so `claude plugin update` resolves the release.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-11 20:42:30 +01:00
.claude-plugin chore(catalog): bump dynamisk-rettsstat v0.1.1 -> v0.1.2 2026-11-11 20:42:30 +01:00
docs docs(migration): replace links to now-private repos with placeholders 2026-11-04 09:29:08 +01:00
scripts feat(catalog): list dynamisk-rettsstat v0.1.0 2026-11-11 19:41:11 +01:00
test test(catalog): flip red-nested-key -> green-nested-key (okr's checker converged) 2026-08-09 20:49:32 +02:00
.gitignore chore: gitignore STATE.md (per-plugin continuity files stay local, not tracked) 2026-05-29 12:20:18 +02:00
.gitleaks.toml refactor(ms-ai-architect): playground uses vendored design-system 2026-05-03 12:35:47 +02:00
.gitleaksignore refactor(linkedin)!: rename plugin linkedin-thought-leadership → linkedin-studio (v3.0.0) 2026-05-29 11:32:02 +02:00
.mailmap Add .mailmap to consolidate author identities 2026-05-05 20:08:12 +02:00
CLAUDE.md feat(check-versions): name ungated stat axes instead of skipping them silently 2026-11-04 09:33:52 +01:00
CONVENTIONS.md docs(conventions): reframe docs-gate + playground refs for polyrepo split 2026-06-18 10:26:15 +02:00
GOVERNANCE.md docs: introduce GOVERNANCE.md and unify fork-and-own blurb 2026-05-03 14:57:00 +02:00
LICENSE docs(catalog): bring the catalog up to the repo-standard gate 2026-08-03 21:53:05 +02:00
llms.txt docs(catalog): add llms.txt (D2b) 2026-08-21 11:23:46 +02:00
README.md chore(catalog): bump dynamisk-rettsstat v0.1.1 -> v0.1.2 2026-11-11 20:42:30 +01:00
SECURITY.md docs(catalog): add SECURITY.md 2026-08-16 21:14:34 +02:00

ktg-plugin-marketplace

Open-source Claude Code plugins. Currently dynamisk-rettsstat; more are added when they are good enough.

Built for my own Claude Code workflow and shared openly for anyone who finds them useful. Solo-maintained, AI-assisted, fork-and-own. Issues are welcome as signals; pull requests are not accepted. See GOVERNANCE.md for what upstream provides and how this is meant to be used.

All code here is generated by Claude Code through a dialog-based process: I direct, review, test, and validate; Claude writes. Treat the plugins as AI-authored, human-curated.

Install

claude plugin marketplace add https://git.fromaitochitta.com/open/ktg-plugin-marketplace.git

Then open Claude Code and type /plugin to browse and install — the command above only registers the marketplace, it installs nothing.

Each plugin keeps its own full README and CHANGELOG; this page is just the catalog.

Staying up to date

Auto-update is off by default for this marketplace. claude plugin marketplace add records no autoUpdate key, and Claude Code only defaults it on for Anthropic's own catalogs — so a release published here does not reach an already-registered machine on its own.

Pull updates by hand:

claude plugin marketplace update ktg-plugin-marketplace   # refresh the catalog
claude plugin update <plugin>                             # update one installed plugin (restart to apply)

Or turn auto-update on once, by declaring the marketplace in your user settings (~/.claude/settings.json). This is the entry marketplace add already writes, plus autoUpdate:

{
  "extraKnownMarketplaces": {
    "ktg-plugin-marketplace": {
      "source": {
        "source": "git",
        "url": "https://git.fromaitochitta.com/open/ktg-plugin-marketplace.git"
      },
      "autoUpdate": true
    }
  }
}

Claude Code then refreshes this marketplace and its installed plugins on startup.

Measured on Claude Code 2.1.260 in an isolated CLAUDE_CONFIG_DIR profile: a fresh marketplace add writes the entry above without autoUpdate; setting the key to true propagates to plugins/known_marketplaces.json on the next start, and false propagates too.

Non-goals

  • Not a host for plugin source or issues. This repository holds the marketplace manifest and this catalog page. Code, issues and releases live in each plugin's own repository, linked from its entry below.
  • Not a third-party registry. Only plugins maintained here are listed. There is no submission process.
  • No pull requests. Issues are welcome as signals; PRs are not accepted. See GOVERNANCE.md for the reasoning and the fork-and-own model.
  • No support commitment. Bug fixes are best-effort, breaking changes happen and are documented in each plugin's CHANGELOG. Version-pin if you need stability.

Plugins

dynamisk-rettsstat v0.1.2 🇳🇴 Norwegian

Runs the model from the Norwegian concept note Den dynamiske rettsstaten on your own numbers, by talking to Claude. The model describes the criminal justice chain: where it binds, what kind of measure that calls for, and what happens over time. Skills, examples and documentation are in Norwegian.

  • diagnose — from figures per link (cases in, capacity, backlog) to the link that binds, the type of measure and the capacity needed
  • forlop — stability check and the month-by-month course of the measure
  • simuler — from a "what if" question to a scenario file, a run, a table of key figures and a figure
  • forbedre — a working copy of the model that you own, a map from the note's equations to the code, extensions with a limiting case, and a check that says which of the note's results a change moves
  • Reproduces the note — the core is unchanged copies of the note's code, locked by sha256; the check re-creates the note's 22 data files byte for byte with the pinned versions of numpy and scipy

The parameters are stylised and the model is not calibrated on Norwegian data: runs show the model's dynamics, not forecasts. Needs Python 3, plus numpy and scipy for everything except the diagnosis.

4 skills · 263 tests · Full documentation →


Tests

This repository's own gates — version consistency between each plugin entry and the tag it pins, catalog-to-plugin stat mirroring, OKF parity, and the navigation goldens — are covered by tests:

node --test scripts/*.test.mjs

The test files under docs/marketplace-polyrepo-migration/ belong to the one-off migration that split the former monorepo into per-plugin repositories. They are kept as a record of that migration and are not part of the suite above.


License

MIT