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.
npx agentmods add skills/acn-ericlaw/agent-memory/sync-adaptersnpx skills add acn-ericlaw/agent-memory --skill sync-adaptersgit clone --depth 1 https://github.com/acn-ericlaw/agent-memoryWhat 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 | $0.00064 | $0.00579 |
| Opus 5 | $0.00032 | $0.00290 |
| Sonnet 5 | $0.00013 | $0.00116 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
sync-adapters 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 2d 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.
What it actually says
⚠️ Tool-managed skill provided by agent-memory (
provenance: agent-memory-builtin). Don't edit it in place — fork under a new name, or upstream a fix to the agent-memory project (seeSKILLS.md).
This skill is the sync skill adapters operation. It is a runnable script — do not hunt for an
npm command, MCP tool, or hand-write the adapter files. Run one of these from the repo root (output is
byte-identical across all three; bash needs no runtime install — prefer it, especially in a non-Node
project):
bash agent-skills/sync-adapters/scripts/sync-adapters.sh
# no bash? (e.g. native Windows) — use whichever runtime you have:
node agent-skills/sync-adapters/scripts/sync-adapters.mjs
python3 agent-skills/sync-adapters/scripts/sync-adapters.py
For each agent-skills/<name>/SKILL.md it (re)writes all six vendor adapters —
.claude/skills/<name>/SKILL.md, .gemini/commands/<name>.toml, .cursor/rules/<name>.mdc,
.kiro/skills/<name>/SKILL.md, .github/skills/<name>/SKILL.md, .agents/skills/<name>/SKILL.md — and
prunes orphaned adapters it previously generated (identified by their pointer signature; never touches
hand-authored vendor files). The .agents/skills/ adapter is the Agent Skills standard dir read by Google
Antigravity (agy, the Gemini CLI successor) — Antigravity ignores .gemini/commands, so this is what
makes /<name> work there.
It is idempotent and writes only the gitignored adapter dirs — never agent-skills/, never a
committed file. Pass --dry-run to preview. The neutral agent-skills/<name>/SKILL.md is always the
source of truth; the adapters are thin regenerated pointers (do not commit them).
After syncing, reload your runtime if it loads adapters at startup (e.g. GitHub Copilot CLI:
/restart or a skills rescan) for a new /<name> to become available this session.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 36 lines · 64 tokens per session scan A 3e58718795d2
sync-adapters is a skill published in the GitHub repository acn-ericlaw/agent-memory (5 stars, last pushed 8d ago), licensed Apache-2.0. It adds 64 tokens to every session and 579 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-31.
Other skills, from other repositories
reelier-slice
Use when implementing any change to the Reelier authority ledger or Path C compiled-authority code - encodes the evidence-led slice loop, the baseline gate, the RED/GREEN review protocol, and the failure modes that have actually cost slices here.
reelier-replay
Freeze a repeatable, tool-call-driven task into a replayable Reelier skill, and replay an existing skill instead of redoing deterministic work. Use after finishing a task that was mostly API/MCP tool calls (data pulls, report generation, deploy checks, CRUD sequences) — never for arbitrary coding/file-edit sessions…
reelier-write-safety
Bound and record an agent's writes before granting them. Use when the user is adding or configuring an MCP server, planning to run an agent unattended or on a schedule or in CI, or deciding whether to give an agent write access to a real system. Covers the recorder, the policy seatbelt, approvals, and what a receipt…
reelier
Replay recurring deterministic jobs at 0 tokens instead of re-reasoning them every run. For cron/heartbeat tool-call workflows (status checks, data pulls, report generation, CRUD sequences) — record the job once with reelier, then run "npx -y reelier run " on every heartbeat and gate drift with "reelier diff". Never…
coding
编写并运行 Python 代码，验证脚本逻辑和输出。.
kayba-stage-6-hitl
Human-In-The-Loop gate that presents the action plan with full context, collects an informed approval/modification/rejection decision, and records the outcome. Trigger when the user says "run stage 6", "HITL review", "approve action plan", or when invoked by the kayba-pipeline orchestrator. Requires eval/actionplan.md…