memory-edit

A command for changing or removing saved entries in the agent's memory files.

In plain words
What is it for?
Updating fields and removing matching items such as active issues, merge requests, or environment records.
Why use it?
It lets you correct outdated information or remove records that are no longer relevant.

Command

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 commands/dmzoneill/redhat-ai-workflow/memory-edit
Clone the repo
git clone --depth 1 https://github.com/dmzoneill/redhat-ai-workflow
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 736 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.00000 $0.00736
Opus 5 $0.00000 $0.00368
Sonnet 5 $0.00000 $0.00147
Haiku 4.5 $0.00000 $0.00074

Measured 2d ago against content hash eda50cef3810, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

memory-edit 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.

docs/commands/memory-edit.md · 125 lines

How it starts

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

/memory-edit

Modify or remove entries from memory.

Overview

Modify or remove entries from memory.

Underlying Skill: memory_edit

This command is a wrapper that calls the memory_edit skill. For detailed process information, see skills/memory_edit.md.

Arguments

Argument Required Description
file No -
action No -
list_path No -
match_key No -
match_value No -

Usage

Examples

skill_run("memory_edit", '{
  "file": "state/current_work",
  "action": "remove",
  "list_path": "active_issues",
  "match_key": "key",
  "match_value": "AAP-12345"
}')
skill_run("memory_edit", '{
  "file": "state/current_work",
  "action": "remove",
  "list_path": "open_mrs",
  "match_key": "id",
  "match_value": "123"
}')
skill_run("memory_edit", '{
  "file": "state/environments",
  "action": "update",
  "field_path": "environments.stage.status",
  "new_value": "healthy"
}')

Process Flow

This command invokes the memory_edit skill. The process flow is:

flowchart LR
    START([User runs /memory-edit]) --> VALIDATE[Validate Arguments]
    VALIDATE --> CALL[Call memory_edit skill]
    CALL --> EXECUTE[Execute Skill Steps]
    EXECUTE --> RESULT[Return Result]
    RESULT --> END([Complete])

    style START fill:#6366f1,stroke:#4f46e5,color:#fff
    style END fill:#10b981,stroke:#059669,color:#fff
    style CALL fill:#3b82f6,stroke:#2563eb,color:#fff
```bash

For detailed step-by-step process, see the [memory_edit skill documentation](../skills/memory_edit.md).

## Details

## Usage

### Remove an Item

Remove a closed issue from active_issues:
```text
skill_run("memory_edit", '{
  "file": "state/current_work",
  "action": "remove",
  "list_path": "active_issues",
  "match_key": "key",
  "match_value": "AAP-12345"
}')
```text

Remove a merged MR from open_mrs:
```text
skill_run("memory_edit", '{
  "file": "state/current_work",
  "action": "remove",
  "list_path": "open_mrs",
  "match_key": "id",
  "match_value": "123"
}')
```bash

Read the full file on GitHub · 125 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. 2d ago First seen · 125 lines · 0 tokens per session scan A eda50cef3810

Subscribe to this mod's changes

memory-edit is a command published in the GitHub repository dmzoneill/redhat-ai-workflow (5 stars, last pushed 23d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 736 tokens. 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.