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 commands/dmzoneill/redhat-ai-workflow/memory-editgit clone --depth 1 https://github.com/dmzoneill/redhat-ai-workflowWhat 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.00000 | $0.00736 |
| Opus 5 | $0.00000 | $0.00368 |
| Sonnet 5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00074 |
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.
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
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 · 125 lines · 0 tokens per session scan A eda50cef3810
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.
Other commands, from other repositories
pr-address
Address PR review comments on current branch.
enforce_standards
CRITICAL: Before running the code standards enforcer, we must prepare the stack properly and abort if there are merge conflicts.
OPSX: Verify
Verify implementation matches change artifacts before archiving.
OPSX: Sync
Sync delta specs from a change to main specs.
context
项目上下文管理:初始化 .context 目录、记录决策日志、压缩归档、查看历史.
triage
Triage Linear issue with comprehensive analysis.