Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/CAPHTECH/pce-memorynpx agentmods add skills/caphtech/pce-memory/pce-syncWrote 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/caphtech/pce-memory/pce-sync)<a href="https://agentmods.dev/skills/caphtech/pce-memory/pce-sync"><img src="https://agentmods.dev/badge/skills/caphtech/pce-memory/pce-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/caphtech/pce-memory/pce-sync"><img src="https://agentmods.dev/badge/skills/caphtech/pce-memory/pce-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00055 | $0.00821 |
| Opus 5.5 | $0.00022 | $0.00328 |
| Sonnet 5.5 | $0.00011 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
pce-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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PCE Sync - V2 Team Knowledge Synchronization
Synchronize durable pce-memory knowledge across team members. v2 sync preserves memory_type and follows layer-aware export/import rules.
Argument Parsing
Parse $ARGUMENTS:
push→ Export local knowledgepull→ Import team knowledgestatus→ Check sync state- No arguments → Run status and guide
Operations
Push (Export)
Export syncable durable knowledge to .pce-shared/.
pce_memory_sync_push()
- Export target:
$PCE_SYNC_TARGET_DIR(default:.pce-shared/) - If
PCE_SYNC_AUTO_STAGE=true, autogit add - Scope filter: Restrict with
PCE_SYNC_SCOPE_FILTER memory_typeis exported with each durable claim- Session/micro content is excluded
- Rolled-back or tombstoned durable claims are excluded
promotion_queueis local review state and is never exported
Pull (Import)
Import team knowledge from .pce-shared/.
pce_memory_sync_pull()
// Or dry-run to preview
pce_memory_sync_pull({ dry_run: true })
- CRDT (G-Set) based merge: additions only, no deletions
- Boundary promotion:
public < internal < pii < secret(upgrade only) memory_typeis preserved on import and backfilled onto existing claims only when the receiver is missing it- Session/micro artifacts remain local-only and are not reconstructed from sync
promotion_queuestays local-only because it represents review/rollback governance state- Conflicts: boundary upgrades auto-resolve, entity/relation diffs are still skipped for manual review
Status
pce_memory_sync_status()
Returns:
- Local and remote claim counts
- Unsynced claim count
- Last sync timestamp
- Conflict presence
Git Hooks Integration
Setup
# Install hooks
./scripts/git-hooks/install-hooks.sh
# Set environment
export PCE_SYNC_ENABLED=true
Flow
git commit → pre-commit hook → sync push (auto export)
git pull → post-merge hook → sync pull (auto import)
Layer-Aware Rules
- micro / session: never sync by default
- meso / project: default sync surface
- macro / principle: sync only after reviewed durable promotion
- promotion_queue: local-only review queue, excluded from Git sync
What ships with it
1 file 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.
- 1mo ago First seen · 107 lines · 55 tokens per session scan A dd8d1d224c68
pce-sync is a skill published in the GitHub repository CAPHTECH/pce-memory (3 stars, last pushed 6mo ago), licensed MIT. It adds 55 tokens to every session and 821 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-31.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.