Borrowing it
Nothing to install: this file belongs to majiayu000/remem. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/majiayu000/remem/main/.agents/skills/remem-plugin-version-sync/SKILL.mdgit clone --depth 1 https://github.com/majiayu000/rememWrote 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.
[](https://agentmods.dev/skills/majiayu000/remem/remem-plugin-version-sync)<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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 30 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00059 | $0.00716 |
| Opus 5.5 | $0.00024 | $0.00286 |
| Sonnet 5.5 | $0.00012 | $0.00143 |
| Haiku 4.5 | $0.00006 | $0.00072 |
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 1mo 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.
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.tomlCargo.lockplugins/remem/.codex-plugin/plugin.jsonplugins/remem/runtimes/remem-releases.jsonnpm/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.mdplugins/remem/skills/remem/SKILL.mdplugins/remem/scripts/remem-runtime.jsplugins/remem/scripts/remem-runtime.test.jsnpm/remem/scripts/install.jsnpm/remem/scripts/install.test.js
Workflow
- Run
git status --shortand identify whether the PR changes binary-impacting files:src/,migrations/, orCargo.lock. - If binary-impacting files changed, bump
Cargo.tomlpackage.version. - Regenerate or update
Cargo.lockso theremem-aipackage version matches. - Update
plugins/remem/.codex-plugin/plugin.jsonto the same version. - Update
plugins/remem/runtimes/remem-releases.jsonso it contains exactly the same version key and abase_urlending in/releases/download/v<version>. - Update
npm/remem/package.jsonto the same version. For npm-only metadata or wrapper behavior changes, update this file without bumping the binary only whencheck_plugin_version_sync.pystill passes. - Keep runtime resolution explicit:
REMEM_BINARYand plugin-managed runtime paths are valid; do not silently adoptrememfromPATH.
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
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.
- 1mo ago First seen · 77 lines · 59 tokens per session scan A c654e738edce
remem-plugin-version-sync is a skill published in the GitHub repository majiayu000/remem (34 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 716 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-close-issues
Close resolved Codewhale issues only after verifying the landed commit/behavior, with a positive crediting comment; never from title alone.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
gh-credit-harvest
Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.