memory-cleanup

memory-cleanup is a command for coding agents from dmzoneill/redhat-ai-workflow. It costs 0 tokens per session (502 once invoked), scanned A, original, Apache-2.0.

A command that removes old or stale entries from an agent's stored memory, with a preview mode available by default. A dry run shows what would be removed without applying the cleanup.

In plain words
What is it for?
Use it to preview stale memory entries or run the memory-cleanup process with the dry-run option disabled.
Why use it?
It helps keep stored project context manageable and lets developers review proposed removals before changing memory.

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-cleanup
Clone the repo
git clone --depth 1 https://github.com/dmzoneill/redhat-ai-workflow

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

agentmods badge for memory-cleanup

README.md
[![agentmods](https://agentmods.dev/badge/commands/dmzoneill/redhat-ai-workflow/memory-cleanup.svg)](https://agentmods.dev/commands/dmzoneill/redhat-ai-workflow/memory-cleanup)
Your own site
<a href="https://agentmods.dev/commands/dmzoneill/redhat-ai-workflow/memory-cleanup"><img src="https://agentmods.dev/badge/commands/dmzoneill/redhat-ai-workflow/memory-cleanup.svg" alt="Measured on agentmods" height="20"></a>
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 502 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.00502
Opus 5 $0.00000 $0.00251
Sonnet 5 $0.00000 $0.00100
Haiku 4.5 $0.00000 $0.00050

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

Security

Grade A, and why

memory-cleanup 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 4d 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-cleanup.md · 91 lines

What it actually says

/memory-cleanup

Clean up stale entries from memory.

Overview

Clean up stale entries from memory.

Underlying Skill: memory_cleanup

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

Arguments

Argument Required Description
dry_run No -

Usage

Examples

skill_run("memory_cleanup", '{}')
skill_run("memory_cleanup", '{"dry_run": false}')
/memory-cleanup

Process Flow

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

flowchart LR
    START([User runs /memory-cleanup]) --> VALIDATE[Validate Arguments]
    VALIDATE --> CALL[Call memory_cleanup 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
```text

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

## Details

## Usage

**Preview what would be removed (dry run - default):**
```text
skill_run("memory_cleanup", '{}')
```text

**Actually remove stale entries:**
```text
skill_run("memory_cleanup", '{"dry_run": false}')
```text

## What Gets Cleaned

- **Active Issues**: Issues with status "Done", "Closed", or "Resolved"
- **Open MRs**: MRs with pipeline status "merged" or "closed"
- **Ephemeral Namespaces**: Namespaces older than 7 days (configurable)

## Options

- `dry_run`: Preview changes without applying (default: true)
- `days`: Remove ephemeral namespaces older than this (default: 7)

## Example

```text
/memory-cleanup

This shows what would be cleaned. Run with dry_run: false to apply.

(To be determined based on command relationships)

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. 4d ago First seen · 91 lines · 0 tokens per session scan A 6a8c3ed03409

Subscribe to this mod's changes

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