- JavaScript 66.7%
- TypeScript 33.3%
| prompts | ||
| rtk | ||
| safari-browser | ||
| .gitignore | ||
| AGENTS.md | ||
| package.json | ||
| README.md | ||
| resources.test.mjs | ||
Pi resources
Shared source for our developed and adopted Pi extensions and prompt templates. package.json explicitly declares their resources as one Pi package.
| Directory | Purpose | Requirements |
|---|---|---|
| safari-browser | Control real Safari through codemode and nested bash calls | macOS, Safari, Pi codemode + bash, operator-enabled Automation and JavaScript from Apple Events |
| rtk | Rewrite bash commands through RTK for compact output | rtk >= 0.23.0 in Pi's PATH |
| memory-review | Read-only /memory-review [focus] with precise update proposals |
Explicit mappings and local notes under ~/Shared/obsidian/mxm/AI Memory |
Extensions were tested with Pi 1.0.4 (@earendil-works/pi-coding-agent); resource packaging follows Pi 1.1.0. Pi supplies the declared peer dependencies.
Safari automation is an unrestricted POC: it can access existing logged-in browser sessions, execute page JavaScript and perform writes. It has no origin restrictions or per-action approvals. The extensions provide no isolation boundary.
Install
pi install https://git.miskam.xyz/mxm/pi-extensions.git
Run /reload in existing Pi sessions. For an editable local checkout, use pi install ~/Work/pi-extensions instead; no symlinks are needed. Git access and the extension-specific requirements above must already be available.
Development
- Keep each extension in
<name>/index.tswith its README, tests and support files. - Add entry points to
package.json'spi.extensions. - Keep shared prompt templates in
prompts/and declare them in the Pi manifest. - Project-specific Homelab skills remain in Homelab's
.agents/skills/. - Run
npm testfor Safari transport/quoting and prompt packaging checks; no browser activity or LLM requests. - The optional live Safari smoke test opens/closes its own demo window and makes no LLM requests; see its README.
The package owns the shared /memory-review prompt source. Remove obsolete local prompt copies when migrating an installation so the command does not resolve to a stale override. /memory-review never writes memory without explicit approval. Project-specific skills are not bundled or replaced.
Deployment and machine-specific installation remain separate from this repository. The RTK executable, project scripts, personal settings, credentials, sessions and browser state are not included.