pin

This skill never installs anything. It runs one Node process from the plugin directory, which writes a run-scoped variable to the user's own Mubit instance. No packages, no services, no changes to the shell.

What a pin is

A pin is a sentence that is true for this run and this task, injected in full above the recalled memory on every prompt until it is cleared.

for the rest of this, don't touch the vendored server

The model is who notices a sentence like that. Before pinning existed, the only place to put it was memory — so it was written as a lesson, and a lesson is durable and cross-session. It would then be recalled into every future session of a project where it had long since stopped being true. Removing that failure is the entire reason this command exists.

Pin or remember — the line is not blurry

	/mubit-memory:pin	/mubit-memory:remember
Scope	this run, this task	durable, every future session
Ends when	the user clears it, or the run does	never, unless it is forgotten or superseded
Costs	tokens on every prompt of this run	nothing until recall decides it is relevant
Example	"no new dependencies while we finish this PR"	"this project pins dependencies by exact version"

Read the two example rows before choosing. If the sentence would still be worth saying in six months, in a different session, it is a lesson — use /mubit-memory:remember. If it would be wrong to say next week, it is a pin.

Pin something

node "${CLAUDE_PLUGIN_ROOT}/bin/pin.mjs" add "don't touch the vendored server" --data-dir "${MUBIT_CC_DATA_DIR:-${CLAUDE_PLUGIN_DATA}}" --run <run_id> --json

It renders on the very next prompt — the command writes through to the local cache the recall hook reads, so there is nothing to wait for.

Use the user's own words. A pin is an instruction, and paraphrasing an instruction changes it.

Always pass --run

<run_id> is the run named in the Mubit memory is active block at the top of this conversation — the line reading Run: cc-<slug>-<hash>. Copy it verbatim.