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/synaptic-labs-ai/pact-plugin/pact-memorynpx skills add Synaptic-Labs-AI/PACT-Plugin --skill pact-memorygit clone --depth 1 https://github.com/Synaptic-Labs-AI/PACT-PluginWrote 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/synaptic-labs-ai/pact-plugin/pact-memory)<a href="https://agentmods.dev/skills/synaptic-labs-ai/pact-plugin/pact-memory"><img src="https://agentmods.dev/badge/skills/synaptic-labs-ai/pact-plugin/pact-memory.svg" alt="Measured on agentmods" 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.00061 | $0.05996 |
| Opus 5 | $0.00030 | $0.02998 |
| Sonnet 5 | $0.00012 | $0.01199 |
| Haiku 4.5 | $0.00006 | $0.00600 |
Grade A, and why
pact-memory 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 6d 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 — 505 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PACT Memory Skill
Persistent memory system for PACT framework agents. Store and retrieve context, goals, lessons learned, decisions, and entities across sessions with semantic search.
Overview
The PACT Memory skill provides:
- Rich Memory Objects: Store context, goals, tasks, lessons, decisions, and entities
- Semantic Search: Find relevant memories using natural language queries
- Graph-Enhanced Retrieval: Memories linked to files are boosted when working on related files
- Session Tracking: Automatic file tracking and session context
- Cross-Session Learning: Memories persist across sessions for cumulative knowledge
Store access: the two routes
STORE ACCESS. A memory operation (save, search, get, list, update or
delete a record) goes through the pact-memory CLI. YOU DO NOT SELECT A
STORE. Do not name a store by --db-path, by an environment variable, or by
one more route somebody adds later. Let the CLI resolve it. A store you
select is not the store the memory of the team lives in, so a save there is
lost rather than shared. STORE INSPECTION is different: a row count, a
column audit, or a schema check on the file. To inspect, do not run a CLI
verb, do not import a module below skills/pact-memory/scripts/, and do not
open the store read-write. In ONE command, against ONE resolved path, check
that memory.db-wal and memory.db-shm are both absent by their full
names, then open with mode=ro and immutable=1. Without immutable=1 the
open fails. If a sidecar is present, stop and report. The read does not load
the vector extension, so it cannot answer a question about vec_memories.
Stop and report rather than take a barred route.
The sections below give the detail behind each sentence above.
What ships with it
15 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.
- references/memory-patterns.md 20 KB
- scripts/__init__.py 6.0 KB runs code
- scripts/cli.py 50 KB runs code
- scripts/config.py 12 KB runs code
- scripts/database.py 59 KB runs code
- scripts/embedding_catchup.py 13 KB runs code
- scripts/embeddings.py 7.4 KB runs code
- scripts/graph.py 19 KB runs code
- scripts/memory_api.py 47 KB runs code
- scripts/memory_init.py 21 KB runs code
- scripts/models.py 20 KB runs code
- scripts/pact_session.py 7.8 KB runs code
- scripts/search.py 16 KB runs code
- scripts/setup_memory.py 5.2 KB runs code
- scripts/working_memory.py 140 KB runs code
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.
- 6d ago First seen · 505 lines · 61 tokens per session scan A 1f593bdd841b
pact-memory is a skill published in the GitHub repository Synaptic-Labs-AI/PACT-Plugin (71 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 5,996 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-30.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
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…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
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.
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…