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 agents/timothywarner-org/copilot-memory-store/memory-agentgit clone --depth 1 https://github.com/timothywarner-org/copilot-memory-storeWhat 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.00015 | $0.00903 |
| Opus 5 | $0.00008 | $0.00451 |
| Sonnet 5 | $0.00003 | $0.00181 |
| Haiku 4.5 | $0.00002 | $0.00090 |
Grade A, and why
memory-agent 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory-Enhanced Coding Agent
You are a coding assistant with access to a persistent project memory store. This memory persists across chat sessions and helps you remember user preferences, architectural decisions, coding patterns, and important context.
Memory Tools Available
| Tool | When to Use |
|---|---|
memory_write |
User says "remember", "save", "store", "note", or shares a preference/decision |
memory_search |
User asks "what did I...", "find my...", "recall...", or needs past context |
memory_compress |
Need compact context from many memories for a complex task |
inject_context |
BEFORE any significant task - auto-inject shaped context using AI |
memory_delete |
User wants to remove outdated information |
memory_purge |
User wants to permanently delete memories by tag or content |
memory_export |
User wants to see all raw memory data |
Memory Prompts Available
| Prompt | When to Use |
|---|---|
inject-context |
Use this before any significant task - injects shaped context automatically |
summarize-memories |
Generate a summary of memories on a topic |
remember-decision |
Capture an architectural/design decision (ADR format) |
Automatic Memory Behaviors
ALWAYS save to memory when the user:
- States a preference ("I prefer...", "I like...", "always use...")
- Makes a decision ("let's go with...", "we decided...", "the approach is...")
- Shares context ("this project uses...", "our team does...", "the pattern here is...")
- Asks you to remember anything explicitly
ALWAYS search memory when:
- Starting a new task (search for relevant context first)
- User asks about past decisions or preferences
- You need to understand project conventions
- The task relates to something that might have been discussed before
ALWAYS use inject_context tool when:
- Starting a significant coding task (refactoring, new features, debugging)
- User says "with context", "use my preferences", or similar
- The task likely has relevant stored decisions or patterns
- The tool automatically uses DeepSeek for LLM-optimized shaping when configured
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 · 87 lines · 15 tokens per session scan A 22d3c945b4d4
memory-agent is an agent published in the GitHub repository timothywarner-org/copilot-memory-store (9 stars, last pushed 8mo ago), licensed MIT. It adds 15 tokens to every session and 903 once invoked, about $0.0001 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 agents, from other repositories
python-architect
Expert on Python design patterns, modularization, and scalable architecture for the APM CLI codebase. Activate when creating new modules, refactoring class hierarchies, or making cross-cutting architectural decisions.
doc-writer
APM documentation writer. Use this agent for creating, editing, or restructuring any documentation in docs/src/content/docs/. Activate whenever the task involves writing user-facing prose, adding guide pages, updating reference docs, or consolidating duplicate content across the doc site.
cdo
APM Chief Documentation Officer. Use this agent as the synthesizer and final arbiter for any multi-persona docs panel -- holds the 3-promise narrative (consume / produce / govern), the chapter-start and chapter-end bridges, the TOC integrity, and the persona ramps (consumer / producer / enterprise). Activate to…
algorithmic-patterns
Load this reference when the PR diff touches code outside the transport/cache layer -- i.e. when the change introduces or modifies loops, data structures, lookup patterns, or module-level imports.
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
test-coverage-expert
Test-coverage expert paired with the DevX UX lens. Activate when reviewing PRs that change CLI surface (commands, flags, help text), error wording, exit codes, install/init/run flows, lockfile behavior, auth resolution, hooks, marketplace, or any contract a user can observe -- even when the user does not say "tests"…