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 skills/openshift-online/agent-control-plane/memorynpx skills add openshift-online/agent-control-plane --skill memorygit clone --depth 1 https://github.com/openshift-online/agent-control-planeWhat 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.00099 | $0.00957 |
| Opus 5 | $0.00049 | $0.00478 |
| Sonnet 5 | $0.00020 | $0.00191 |
| Haiku 4.5 | $0.00010 | $0.00096 |
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 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.
This is a copy
100% identical to memory — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Management
Manage the auto-memory system for the Ambient Code Platform project.
Usage
/memory # Show summary of all memories
/memory search <query> # Search for a topic
/memory audit # Check for stale/duplicate memories
/memory prune # Remove stale memories (with confirmation)
/memory add <topic> # Create a new memory
User Input
$ARGUMENTS
Parse the subcommand from $ARGUMENTS. Default to summary if empty.
Memory Location
All memory files live at:
$HOME/.claude/projects/<project-slug>/memory/
Use the active project's slug (the repo path with / replaced by -).
The index file is MEMORY.md in that directory.
Subcommands
/memory — Summary
- Read
MEMORY.mdto get the index - Count total memories by type (user, feedback, project, reference)
- List the most recently modified files
- Report: total count, breakdown by type, last modified dates
/memory search <query>
- Read
MEMORY.mdfor the index - Grep through all memory files for the query term
- Read matching files and show relevant excerpts
- Report: matching files with frontmatter (name, type, description)
/memory audit
Check for quality issues:
- Stale memories — project/reference memories older than 3 months may be outdated
- Duplicate memories — similar names or descriptions across files
- Missing frontmatter — files without proper
name,description,typefields - Orphaned files — memory files not referenced in
MEMORY.md - Broken links —
MEMORY.mdentries pointing to nonexistent files - Oversized index —
MEMORY.mdapproaching the 200-line truncation limit
Report each issue with the file path and suggested action.
/memory prune
- Run the audit checks
- Present findings to the user
- For each stale/duplicate/orphaned memory, ask: keep, update, or delete?
- Execute confirmed deletions
- Update
MEMORY.mdindex accordingly
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 129 lines · 99 tokens per session scan A a2fd9bd480ae
memory is a skill published in the GitHub repository openshift-online/agent-control-plane (10 stars, last pushed 4d ago), licensed MIT. It adds 99 tokens to every session and 957 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to memory, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
fleet-manager
Use when managing, triaging, restarting, escalating, or summarizing Codewhale Pod runs and workers.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
security-review
Review trust boundaries, auth/authz, injection, secrets, filesystem/network exposure, dependencies, and exploitability without pretending a shallow lint is an audit.
ppt-review
Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.