pce-core

A workflow guide for pce-memory, a system that stores and recalls project knowledge over time. It covers capturing raw notes, turning them into lasting knowledge, recalling relevant context, recording feedback, and undoing incorrect claims.

In plain words
What is it for?
Use it to observe notes, create and approve promotion candidates, activate relevant context, submit feedback, roll back claims, or use the limited upsert option.
Why use it?
It provides an ordered process for deciding what should remain temporary and what should become durable project knowledge.

Skill for Claude CodeCodex

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/caphtech/pce-memory/pce-core
Any agent
npx skills add CAPHTECH/pce-memory --skill pce-core
Clone the repo
git clone --depth 1 https://github.com/CAPHTECH/pce-memory

Made for: Claude Code, Codex.

Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,004 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.02004
Opus 5 $0.00030 $0.01002
Sonnet 5 $0.00012 $0.00401
Haiku 4.5 $0.00006 $0.00200

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

Security

Grade A, and why

pce-core 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.

pce-memory-plugin/skills/pce-core/SKILL.md · 232 lines

How it starts

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

PCE Core - V2 Knowledge Workflow

Manages the v2 pce-memory workflow:

observe -> distill -> promote -> activate(intent) -> feedback -> rollback

pce_memory_upsert still exists, but only as a narrow escape hatch for already-distilled durable knowledge.

Argument Parsing

Parse $ARGUMENTS:

  • activate [query] → Intent-aware recall mode
  • observe [text] → Raw micro-memory capture
  • distill [source ids or guidance] → Promotion candidate creation
  • promote [candidate-id] → Durable promotion
  • rollback [claim-id] [reason] → Durable repair/supersession
  • upsert [kind] [text] → Escape hatch for already-distilled durable knowledge
  • feedback [claim-id] [signal] → Feedback mode
  • No arguments → Full workflow guide

State Gate

  1. Check current state with pce_memory_state
  2. If Uninitialized, run pce_memory_policy_apply
  3. Continue only after the policy state is ready for the tool you need

1. Observe (Raw Micro Memory Only)

Use pce_memory_observe for raw inputs:

  • session work-in-progress
  • chat/tool/file/http/system outputs
  • debugging notes and local evidence
  • secret or PII-bearing material that must not become durable inline

Rules

  • Observe is raw-only. It does not create durable claims inline.
  • Do not use legacy inline extraction modes such as single_claim_v0.
  • extract: { mode: "noop" } is only a compatibility knob and still preserves raw-only behavior.
  • Use boundary_class: secret only in observe, never in upsert.
  • Use observe instead of upsert for anything session-scoped.

Typical Input

{
  "source_type": "chat|tool|file|http|system",
  "content": "...",
  "boundary_class": "public|internal|pii|secret",
  "tags": ["..."],
  "ttl_days": 7
}

2. Distill (Create Promotion Candidate)

Use pce_memory_distill to convert observations, claims, or an active context into a reviewable candidate.

Inputs

  • source_observation_ids: Raw observations to abstract
  • source_claim_ids: Existing durable claims to refine or supersede
  • active_context_id: Promote from a planned working set
  • proposed_kind: fact | preference | task | policy_hint
  • proposed_scope: project | principle
  • proposed_memory_type: working_state | knowledge | procedure | norm
  • note: Distillation hint for reviewers

Read the full file on GitHub · 232 lines

Files

What ships with it

2 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.

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. 2d ago First seen · 232 lines · 59 tokens per session scan A eeab6f09867d

Subscribe to this mod's changes

pce-core is a skill published in the GitHub repository CAPHTECH/pce-memory (3 stars, last pushed 5mo ago), licensed MIT. It adds 59 tokens to every session and 2,004 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens