procedural-memory
v0.6.0Lets Claude find and reuse previously verified scripts and automations instead of rebuilding them from scratch each time — for developers who want proven code reused safely.
By Rhize Media2 GitHub starsUpdated 2 hours ago
Directory evidence
- Runtimes
- Codex and Claude Code
- Parsed components
- 3 skill or MCP entries
- Source updated
- Sep 27, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install procedural-memory for Codex and Claude Code
codex plugin marketplace add Rhize-Media/rhize-plugins
codex plugin marketplace upgrade rhize-plugins
codex plugin add procedural-memory@rhize-pluginsPaste and run these commands in a terminal with Codex. They add and refresh the rhize-plugins catalog, then install this plugin.
Compatibility: the page URL and API slug “procedural-memory” remain stable.
- Codex:
procedural-memory@agent-plugin-marketplace→procedural-memory@rhize-plugins
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/Rhize-Media/rhize-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is procedural-memory/.
Plugin files
├── .codex-plugin/plugin.json├── .claude-plugin/plugin.json├── skills/functionize/SKILL.md├── skills/procedural-memory/SKILL.md└── skills/rhize-content-engine/SKILL.md
Included Skills3
Mine repeated CLI usage into redacted Functionize candidates, compile inert proposal bundles, or record a digest-bound human review through the rhize-skill CLI. Use when asked to "Functionize" a CLI, inspect repeated shell-history patterns, generate a safe wrapper proposal, or review a Functionize candidate. This skill never registers, approves, promotes, verifies, or runs a generated artifact; use procedural-memory only when a later gate is separately authorized.
Execute a proven artifact from the procedural-memory registry instead of recomposing a task. Use when the registry may already contain working code: recall ranks matches with trust, health, and success signals, while run stays registry-only, digest-checked, and trust/health-gated. Also use to promote a newly captured script or re-run an artifact's sandboxed verification. This skill executes code with a provenance contract; it does not retrieve past conversations or build vault knowledge graphs. Trigger on "is there already a tool for this", "run the registry version", "promote this script", "recall a proven artifact", "re-verify an artifact", or "has this been automated before".
Select and follow the established RHIZE Content Engine for writing, combining, regenerating, or revising resource articles and website/blog drafts. Use for "our content engine protocol", "Rhize Media resource article", or "record the content benchmark" before composing. Binds the requested local-draft or CMS-draft scope to the procedural registry; full public publishing is unsupported. This RHIZE workflow is distinct from ECC's content-engine.
Plugin manifests2
{
"name": "procedural-memory",
"version": "0.6.0",
"description": "Lets Claude find and reuse previously verified scripts and automations instead of rebuilding them from scratch each time — for developers who want proven code reused safely.",
"author": {
"name": "Rhize Media"
},
"homepage": "https://rhize.media",
"keywords": [
"procedural-memory",
"functionize",
"proposal-generation",
"registry",
"recall",
"skill-reuse",
"provenance",
"trust-gating",
"rhize"
],
"skills": "./skills/",
"interface": {
"displayName": "Procedural Memory",
"shortDescription": "Reuse proven code or compile inert proposals safely",
"longDescription": "Use one host-neutral skill to discover and execute already-proven Rhize registry artifacts behind content-digest, provenance, trust, health, and approval gates. Use the separate Functionize skill only to mine redacted CLI shapes, compile inert proposals, and record reviews; generation never grants registry or execution authority.",
"developerName": "Rhize Media",
"category": "Developer Tools",
"capabilities": [
"Interactive",
"Read",
"Write"
],
"defaultPrompt": [
"Recall a proven registry artifact for this task.",
"Run this reviewed registry artifact with its trust gates intact.",
"Promote this reusable script after checking its provenance contract.",
"Compile this repeated CLI pattern into an inert Functionize proposal without promoting or running it."
],
"websiteURL": "https://rhize.media",
"brandColor": "#7C3AED"
}
}{
"name": "procedural-memory",
"version": "0.6.0",
"description": "Lets Claude find and reuse previously verified scripts and automations instead of rebuilding them from scratch each time — for developers who want proven code reused safely.",
"author": {
"name": "Rhize Media"
},
"homepage": "https://rhize.media",
"keywords": [
"procedural-memory",
"functionize",
"proposal-generation",
"registry",
"recall",
"skill-reuse",
"provenance",
"trust-gating",
"pgvector",
"rhize"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[procedural-memory on Agent Plugins Marketplace](https://pluginsmp.com/plugins/procedural-memory)