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-graphnpx skills add CAPHTECH/pce-memory --skill pce-graphgit 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.00045 | $0.00746 |
| Opus 5 | $0.00023 | $0.00373 |
| Sonnet 5 | $0.00009 | $0.00149 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
pce-graph 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PCE Graph - Knowledge Graph Operations
Operate on the pce-memory knowledge graph (entities and relations).
Argument Parsing
Parse $ARGUMENTS:
entity [name] [type]→ Create/search entityrelation [from] [to] [type]→ Create relationquery [pattern]→ Search graph- No arguments → Interactive guide
Entity Operations
Creating Entities
Register important codebase components as entities.
pce_memory_upsert_entity({
id: "entity-unique-id",
type: "component|module|api|database|service|concept",
name: "Display name",
properties: { ... } // Optional additional info
})
Entity Type Guide
See entity-relation-patterns.md.
| Type | Purpose | Examples |
|---|---|---|
| component | Software component | AuthService, UserController |
| module | Module/package | pce-boundary, pce-embeddings |
| api | API endpoint | POST /api/claims |
| database | Data store | DuckDB, Redis |
| service | External service | OpenAI API, GitHub |
| concept | Concept/pattern | State Machine, CRDT |
Querying Entities
pce_memory_query_entity({
type: "component", // Filter by type
name_pattern: "Auth*" // Filter by name pattern
})
Relation Operations
Creating Relations
Register relationships between entities.
pce_memory_upsert_relation({
from_id: "entity-a",
to_id: "entity-b",
relation_type: "depends_on|implements|contains|calls|stores_in",
properties: { ... }
})
Relation Type Guide
| Type | Meaning | Example |
|---|---|---|
| depends_on | Dependency | AuthService depends_on JWTLibrary |
| implements | Implementation | UserController implements IUserAPI |
| contains | Containment | CoreModule contains StateManager |
| calls | Invocation | Handler calls Repository |
| stores_in | Persistence target | ClaimStore stores_in DuckDB |
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.
- 2d ago First seen · 106 lines · 45 tokens per session scan A f3d67d5faddb
pce-graph is a skill published in the GitHub repository CAPHTECH/pce-memory (3 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 746 once invoked, about $0.0002 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.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…