pinlisted

**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. ## Step 0 — resolve the binary No environment variable carries this plugin's path under Codex. Codex lists each skill with the absolute path of its `SKILL.md`; **this file** is at `<plugin-root>/skills/pin/SKILL.md`, so the binary is two directories above it: ``` <plugin-root>/bin/pin.mjs ``` Resolve that to an absolute path from this file's own location and use it in every command below. Do not write `${CLAUDE_PLUGIN_ROOT}`: Codex sets no plugin-root variable of any spelling, so the shell expands it to nothing and `node /bin/pin.mjs` fails with ENOENT. ## 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 You are 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 | | pin | remember | | --- | --- | --- | | Scope | this run, this task | durable, every future session