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/caphtech/pce-memory/pce-syncnpx skills add CAPHTECH/pce-memory --skill pce-syncgit clone --depth 1 https://github.com/CAPHTECH/pce-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.00055 | $0.00821 |
| Opus 5 | $0.00028 | $0.00411 |
| Sonnet 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 yesterday.
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.
- yesterday 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 5mo ago), licensed MIT. It adds 55 tokens to every session and 821 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…