agentmods.dev

remem-plugin-version-sync

remem-plugin-version-sync is a skill for Claude Code, Codex from majiayu000/remem. It costs 59 tokens per session (716 once invoked), scanned A, original, MIT.

A project-specific guide for keeping several release versions in sync. It covers a Rust binary, its Cargo package, a Codex plugin, release metadata, and an npm package.

In plain words
What is it for?
Updating package versions, changing plugin or npm runtime behavior, checking release metadata, and responding to version-sync failures in continuous integration.
Why use it?
It prevents different parts of the same release from advertising or installing incompatible versions.

Skill for Claude CodeCodex

not rated 30 +1 today A scan 59 tokens original MIT
View the source file majiayu000/remem
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/majiayu000/remem/remem-plugin-version-sync
Any agent
npx skills add majiayu000/remem --skill remem-plugin-version-sync
Clone the repo
git clone --depth 1 https://github.com/majiayu000/remem

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for remem-plugin-version-sync

README.md
[![agentmods](https://agentmods.dev/badge/skills/majiayu000/remem/remem-plugin-version-sync.svg)](https://agentmods.dev/skills/majiayu000/remem/remem-plugin-version-sync)
Your own site
<a href="https://agentmods.dev/skills/majiayu000/remem/remem-plugin-version-sync"><img src="https://agentmods.dev/badge/skills/majiayu000/remem/remem-plugin-version-sync.svg" alt="Measured on agentmods" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 716 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00059 $0.00716
Opus 5 $0.00030 $0.00358
Sonnet 5 $0.00012 $0.00143
Haiku 4.5 $0.00006 $0.00072

Measured 5d ago against content hash c654e738edce, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

remem-plugin-version-sync scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/remem-plugin-version-sync/SKILL.md · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.

remem-plugin-version-sync

Use this skill for changes that affect the shipped remem binary, Codex plugin runtime, or npm wrapper. The goal is to keep all release surfaces consistent and avoid a plugin that resolves a stale or incompatible runtime.

Files

Keep these synchronized when the binary version changes:

  • Cargo.toml
  • Cargo.lock
  • plugins/remem/.codex-plugin/plugin.json
  • plugins/remem/runtimes/remem-releases.json
  • npm/remem/package.json

scripts/ci/check_plugin_version_sync.py requires the Rust package, plugin manifest, release manifest, and npm wrapper package versions to match. A binary version bump must update the npm package version even when npm wrapper behavior is unchanged.

Read these before editing plugin runtime behavior:

  • plugins/remem/README.md
  • plugins/remem/skills/remem/SKILL.md
  • plugins/remem/scripts/remem-runtime.js
  • plugins/remem/scripts/remem-runtime.test.js
  • npm/remem/scripts/install.js
  • npm/remem/scripts/install.test.js

Workflow

  1. Run git status --short and identify whether the PR changes binary-impacting files: src/, migrations/, or Cargo.lock.
  2. If binary-impacting files changed, bump Cargo.toml package.version.
  3. Regenerate or update Cargo.lock so the remem-ai package version matches.
  4. Update plugins/remem/.codex-plugin/plugin.json to the same version.
  5. Update plugins/remem/runtimes/remem-releases.json so it contains exactly the same version key and a base_url ending in /releases/download/v<version>.
  6. Update npm/remem/package.json to the same version. For npm-only metadata or wrapper behavior changes, update this file without bumping the binary only when check_plugin_version_sync.py still passes.
  7. Keep runtime resolution explicit: REMEM_BINARY and plugin-managed runtime paths are valid; do not silently adopt remem from PATH.

Verification

Run these focused checks after version or plugin-runtime changes:

python3 scripts/ci/check_plugin_version_sync.py
node --test plugins/remem/scripts/remem-runtime.test.js plugins/remem/apps/remem/server.test.js npm/remem/scripts/install.test.js
python3 scripts/ci/check_version_bump.py origin/main HEAD

Read the full file on GitHub · 77 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 77 lines · 59 tokens per session scan A c654e738edce

Subscribe to this mod's changes

remem-plugin-version-sync is a skill published in the GitHub repository majiayu000/remem (30 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 716 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

DevOps and cloudGit and workflowRustclaude-codeclideveloper-toolsknowledge-managementmcp
Related

Other skills, from other repositories

shodh-memory

Persistent memory system for AI agents. Use this skill to remember context across conversations, recall relevant information, and build long-term knowledge. Activate when you need to store decisions, learnings, errors, or context that should persist beyond the current session.

varun29ankuS/shodh-memory · 53 tokens

migrate-v0-to-v1

Migrate a Scraps wiki from v0 to v1. Use this whenever the user asks to upgrade Scraps, migrate v0 wiki syntax/config, convert implicit tags to explicit #[[tag]], move from scraps-writer to scraps, or audit a wiki for v1 readiness. This skill is designed for one-pass LLM-led migrations that discover the latest v0 and…

boykush/scraps · 105 tokens

ingest

Create a new scrap from a source (prompt, URL, or arbitrary markdown), update cross-links in related scraps, and run a sanity check. Use this when the user wants to add a scrap, summarize an article, save synthesized content to the wiki, or file back a Q&A result.

boykush/scraps · 62 tokens

query

Answer questions about the wiki by searching, reading, and synthesizing relevant scraps with [[Title]] citations. Use this when the user wants to query the wiki, ask what they have written about a topic, compare scraps, find related notes, or pull a synthesized overview from existing scraps.

boykush/scraps · 61 tokens

review-rust

Perform critical Rust code reviews covering correctness, edition 2024 compliance, error handling, API design, async pitfalls, and dependency hygiene. ALWAYS use this skill when the user wants to review, audit, or critically evaluate Rust code — whether that's a PR diff, a specific crate or module, a cross-cutting…

ractive/hyalo · 177 tokens

lint-js

Lint JS/TS code only. Use before opening a PR when only JavaScript or TypeScript files were changed (no Rust).

denoland/deno · 29 tokens