memory

An agent-memory pattern for C# applications that attaches an AI context provider to a chat agent. The provider can add context and run custom code around the agent’s requests.

In plain words
What is it for?
Use it to add memory or other changing context to a supported ChatClientAgent. It can also support logging, message inspection, and custom actions around calls to the AI service.
Why use it?
It helps an agent use relevant information across its work instead of relying only on the current request. It also provides places to inspect messages and customize what happens before and after a request.

Agent for Codex

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 agents/managedcode/prompterone/memory
Clone the repo
git clone --depth 1 https://github.com/managedcode/PrompterOne

Made for: Codex.

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,484 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.00013 $0.03484
Opus 5 $0.00006 $0.01742
Sonnet 5 $0.00003 $0.00697
Haiku 4.5 $0.00001 $0.00348

Measured yesterday against content hash 0da9bfaceac0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

  • memory — 100% identical, 0 lines differ
  • memory — 100% identical, 0 lines differ
.codex/skills/dotnet-microsoft-agent-framework/references/official-docs/tutorials/agents/memory.md · 386 lines

How it starts

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

Adding Memory to an Agent

::: zone pivot="programming-language-csharp" This tutorial shows how to add memory to an agent by implementing an AIContextProvider and attaching it to the agent.

[!IMPORTANT] Not all agent types support AIContextProvider. This step uses a ChatClientAgent, which does support AIContextProvider.

Prerequisites

For prerequisites and installing NuGet packages, see the Create and run a simple agent step in this tutorial.

Create an AIContextProvider

AIContextProvider is an abstract class that you can inherit from, and which can be associated with the AgentThread for a ChatClientAgent. It allows you to:

  1. Run custom logic before and after the agent invokes the underlying inference service.
  2. Provide additional context to the agent before it invokes the underlying inference service.
  3. Inspect all messages provided to and produced by the agent.

Pre and post invocation events

The AIContextProvider class has two methods that you can override to run custom logic before and after the agent invokes the underlying inference service:

  • InvokingAsync - called before the agent invokes the underlying inference service. You can provide additional context to the agent by returning an AIContext object. This context will be merged with the agent's existing context before invoking the underlying service. It is possible to provide instructions, tools, and messages to add to the request.
  • InvokedAsync - called after the agent has received a response from the underlying inference service. You can inspect the request and response messages, and update the state of the context provider.

Serialization

AIContextProvider instances are created and attached to an AgentThread when the thread is created, and when a thread is resumed from a serialized state.

The AIContextProvider instance might have its own state that needs to be persisted between invocations of the agent. For example, a memory component that remembers information about the user might have memories as part of its state.

Read the full file on GitHub · 386 lines

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. yesterday First seen · 386 lines · 13 tokens per session scan A 0da9bfaceac0

Subscribe to this mod's changes

memory is an agent published in the GitHub repository managedcode/PrompterOne (42 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 3,484 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-30.

Related

Other agents, from other repositories

se-technical-writer

Technical writing specialist. Use PROACTIVELY to create or update developer documentation under docs/ when new features are implemented or implementation details need documenting. Produces guides, tutorials, ADRs, and reference docs.

Andes-Software-Solutions/Andes.Extensions.AI · 48 tokens

release-manager

Owns the end-to-end modelcontextprotocol/csharp-sdk release process, orchestrating the prepare-release and publish-release skills (and the bump-version and breaking-changes skills they build on) across five stages: prepare (assess SemVer, bump the version, run ApiCompat/ApiDiff, review docs, draft release notes, open…

modelcontextprotocol/csharp-sdk · 317 tokens

wpf-data-binding-expert

WPF data binding specialist. Implements complex bindings (MultiBinding, PriorityBinding), custom converters, validation patterns, and debugging binding issues.

christian289/dotnet-with-claudecode · 34 tokens

wpf-control-designer

WPF CustomControl design and implementation specialist. Defines DependencyProperty, implements Parts and States Model, OnApplyTemplate patterns.

christian289/dotnet-with-claudecode · 30 tokens

serena-initializer

Serena MCP initialization agent. Checks if current project is activated and onboarded in Serena, performs activation and onboarding if not completed. Use when starting work on a new project or when Serena tools fail.

christian289/dotnet-with-claudecode · 46 tokens

theme-slot-auditor

Read-only auditor for Fluence.Wpf theming structure. Use after any theme, brush, color, accent, or ApplicationThemeManager change to verify the three-slot MergedDictionaries invariant, that slot [0] is rebuilt and replaced every Apply, DynamicResource usage, BrushFactory auto-twinning, canonical WinUI key names, and…

sintaxasn/Fluence.Wpf · 90 tokens