pce-core

pce-core is a skill for Claude Code from CAPHTECH/pce-memory. It costs 59 tokens per session (2,004 once invoked), scanned A, original, MIT.

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 Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the pce-memory-plugin plugin — 4 skills, 1 agent, 3 hooks, 1 MCP server shipped together

Good fit Use it to observe notes, create and approve promotion candidates, activate relevant context, submit feedback, roll back claims, or use the limited upsert option.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/caphtech/pce-memory/pce-core
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.

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.

Or install pce-memory-plugin, the plugin that ships this one along with the rest of its 4 skills, 1 agent, 3 hooks, 1 MCP server.

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

agentmods badge for pce-core

README.md
[![agentmods](https://agentmods.dev/badge/skills/caphtech/pce-memory/pce-core/github.svg)](https://agentmods.dev/skills/caphtech/pce-memory/pce-core)
Your own site
<a href="https://agentmods.dev/skills/caphtech/pce-memory/pce-core"><img src="https://agentmods.dev/badge/skills/caphtech/pce-memory/pce-core/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.

agentmods 80×15 button for pce-core

Your own site · 80×15
<a href="https://agentmods.dev/skills/caphtech/pce-memory/pce-core"><img src="https://agentmods.dev/badge/skills/caphtech/pce-memory/pce-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00059 $0.02004
Opus 5.5 $0.00024 $0.00802
Sonnet 5.5 $0.00012 $0.00401
Haiku 4.5 $0.00006 $0.00200

Measured 1mo ago against content hash eeab6f09867d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

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. 1mo 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 6mo ago), licensed MIT. It adds 59 tokens to every session and 2,004 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.

Related

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…

mem0ai/mem0 · 217 tokens

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…

asgeirtj/system_prompts_leaks · 74 tokens

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…

danielmiessler/LifeOS · 196 tokens

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…

shiwenwen/hope-agent · 115 tokens

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.

opensquilla/opensquilla · 44 tokens

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.

GanyuanRan/Aegis · 45 tokens