cc-mods

Claude Code mods (function-hook plugins), forked from other authors or written here, kept in one repo. Each mod lives under mods/<name>/. A forked one is a squashed git subtree of its upstream: the upstream's license stays with it, and each squash commit names the upstream commit it came from. One written here has no upstream and carries its own license.

The repo is also a plugin marketplace, so a forked mod can be installed from here once it carries local changes.

Mods

Mod	Upstream	Local changes	License
md-prompt	nogu66/md-prompt	0.2.0: none. The dunder-path fix carried here as 0.1.1-cc.1 was taken upstream in 0.1.2 (nogu66/md-prompt#4), so the mod is upstream as is	MIT
plan-progress	zycck/claude-mods	1.0.0-cc.7, on upstream 1.0.0 and its fix #26 (b77335e); the earlier local changes that upstream now ships (the duplicate-title carry, light-theme strips, the strip clock taken from now, the demo reel gone, a folding chevron) are upstream's code again, and the usage rules are back in prompt.compose, which the desktop engine has by 2.1.308 (2.1.284 refused it) and which keeps them in front of the model while the desktop defers the tool. Kept on top: an agent's strip names the agent definition it runs as before its model and effort (worker · sonnet 5.5 · high; none for general-purpose) and, before its time, the context its last request carried (ctx 42k), with its share of the window only where the model id names that window ([1m]: ctx 251k · 25%); a bar's strips fold into one summary row by default (3 more agents · 2 running · 1 done, a waiting or failed agent keeping its own), the foldAgents option, on in the manifest and off for a host that passes no options, so upstream's folding and its tests stand as they are; agents the main thread starts in a turn before it opens a bar for that work move onto that bar as it opens (a new id, or a finished bar's id taken for the next task); the bars draw in the desktop app's own colours (the desktopColors option, on in the manifest: running in its clay #D97757, waiting in its blue, error and done in its danger and success; a pill a shade deeper where white reads at 4.5:1, each strip's tool word lifted until it reads at 4.6:1 on the desktop's tint and on the terminal's 4-bit one); a permission dialog put to you and left unanswered sounds decision, on the engine's permission_prompt notification; finished bars stay doneBarSeconds 60 s by default once /plan-progress-autoclose is on; the engine's own mark under the band (an element of type engine, which draws nothing while bars show) adds no gap under them, so the band sits centred in the desktop's card; the footer shows, before tok/s, how long the main conversation's prompt cache stays warm (the cacheTimer option, auto in the manifest, as cache-timer 0.3.2 counted it: Cache 42m, the seconds in the last minute, Cache cold; auto starts at 1h and follows a model switch's cache_ttl and a 5-to-60-minute idle request's cache read or re-write), the words changing once a minute and read by the band too, so a footer change never hands back an old band; a -cc.N build counts as a folder install, so it never asks GitHub for releases or runs claude plugin update from its settings window, and updates through this repo; the test engine shims Uint8Array#toBase64 for Node before 25, its stream returns its result as the engine's does, compile.cjs uses the TypeScript 7 CLI, and the one case that reads TypeScript's JavaScript API falls back to upstream's pattern under TypeScript 7	MIT

Install a mod from this repo

Function hooks are early access, so turn them on first in ~/.claude/settings.json:

{ "env": { "CLAUDE_CODE_ENABLE_FUNCTION_HOOKS": "1" } }

claude plugin marketplace add mtmtian/cc-mods
claude plugin install md-prompt@cc-mods

To install from a local checkout instead, so your own edits are what gets installed, pass its path: claude plugin marketplace add <path to this checkout>.

Install a mod from one marketplace only. With both md-prompt@nogu66 and md-prompt@cc-mods enabled, the prompt box is painted twice.

Change a mod

A local change bumps the mod's version in its .claude-plugin/plugin.json with a -cc.N suffix (0.1.1-cc.1, 0.1.1-cc.2, ...), since installed copies only update when the version changes. Then:

claude plugin marketplace update cc-mods
claude plugin update md-prompt@cc-mods

While working on a mod, --plugin-dir loads the checkout directly and reloads on save (for md-prompt: claude --plugin-dir mods/md-prompt/plugins/md-prompt); each mod's own README has its test commands.

Run the checks

Use the Node.js version in .node-version, then run from the repo root:

npm ci
npm run ci

The root CI workflow runs on every pull request, pushes to main, and manual dispatch. Test and plugin checks run on standard Ubuntu and macOS runners; workflow and shell checks run in a separate Ubuntu job:

Check	What it covers
npm test	md-prompt's Bun tests, plan-progress's asserted stub-engine regressions, and the upstream-status script's local Git fixtures
npm run check:plugins	Marketplace/source/name/license consistency, strict Claude manifest validation, native hook tests for md-prompt, and TypeScript checks for both plugins
Workflow and shell checks	actionlint for the active root workflow and ShellCheck for the repository's shell scripts

The plugin checks copy the plugins into a temporary directory, use a fresh Claude config, and generate SDK declarations for the locked CLI version there. /cost is a local command: no login or model API key is needed. The API endpoint is set to a closed local port, so an accidental model request fails. The temporary copies are removed even when a check fails. These checks do not replace testing real prompt editing, desktop rendering or audio in Claude Desktop.

Development tools are version-pinned in package.json and package-lock.json; Actions use full commit SHAs. Dependabot proposes weekly npm-tool and Action updates; update actionlint's version and checksum together in the workflow. Claude and Bun require their native-binary install scripts, approved by exact version in allowScripts. When updating either package, review its install script, update the approval with npm install-scripts approve <package>, and rerun the checks. CI has read-only repository permissions, cancels superseded PR runs, and uses neither uploaded artifacts nor dependency caches.

Check and pull upstream changes

upstreams.tsv lists each mod's upstream URL and branch. scripts/upstream-status.sh reads it and, per mod, prints the upstream commit last synced, the upstream commits since, the paths changed here, and the paths changed on both sides (overlap_path=, where a pull may conflict). It only fetches; it never pulls or edits a mod. scripts/test-upstream-status.sh checks it against a throwaway upstream.

bash scripts/upstream-status.sh

To take the upstream changes, with the URL and branch from upstreams.tsv (on a branch, merged with a merge commit so the squash commit's git-subtree-split trailer stays on main):

git subtree pull --prefix=mods/<name> <url> <branch> --squash

Resolve conflicts by keeping each local change on top of upstream's version, never by taking one side whole. Then check that every local change still holds: the mod's tests (each local change has a regress case where it can), and a strict type check against the engine's types, which catches call sites the two sides changed differently.

Add another mod

git subtree add --prefix=mods/<name> https://github.com/<owner>/<repo>.git <branch> --squash

Then add the mod to upstreams.tsv, a row to the table above, and an entry to .claude-plugin/marketplace.json whose source points at the directory holding that mod's .claude-plugin/plugin.json.

A mod written here goes in mods/<name>/plugins/<name>/ with its own LICENSE beside it; it gets a row in the table and a marketplace entry, but no upstreams.tsv line.

Notes

• GitHub only runs workflows from the repo root's .github/workflows, so the CI files inside mods/*/.github/ never run here.
• Each forked mod here is a personal build on upstream: upstream is the base and the local changes are kept on top of it, listed in the table. A local change leaves only when upstream ships the same behaviour (upstream's code then replaces ours, as md-prompt's dunder fix did in 0.1.2) or when we drop it ourselves; an upstream declining it is no reason to drop it. A fix useful to everyone may also be offered upstream as an issue or a pull request.