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/proffesor-for-testing/agentic-qe/memory-managementnpx skills add proffesor-for-testing/agentic-qe --skill memory-managementgit clone --depth 1 https://github.com/proffesor-for-testing/agentic-qeWrote 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.
[](https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/memory-management)<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/memory-management"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/memory-management.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00095 | $0.00787 |
| Opus 5 | $0.00048 | $0.00394 |
| Sonnet 5 | $0.00019 | $0.00157 |
| Haiku 4.5 | $0.00010 | $0.00079 |
Grade A, and why
memory-management 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.
This is a copy
100% identical to memory-management — 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Management Skill
Purpose
AgentDB memory system with HNSW vector search. Provides 150x-12,500x faster pattern retrieval, persistent storage, and semantic search capabilities for learning and knowledge management.
When to Trigger
- need to store successful patterns
- searching for similar solutions
- semantic lookup of past work
- learning from previous tasks
- sharing knowledge between agents
- building knowledge base
When to Skip
- no learning needed
- ephemeral one-off tasks
- external data sources available
- read-only exploration
Commands
Store Pattern
Store a pattern or knowledge item in memory
npx @claude-flow/cli memory store --key "[key]" --value "[value]" --namespace patterns
Example:
npx @claude-flow/cli memory store --key "auth-jwt-pattern" --value "JWT validation with refresh tokens" --namespace patterns
Semantic Search
Search memory using semantic similarity
npx @claude-flow/cli memory search --query "[search terms]" --limit 10
Example:
npx @claude-flow/cli memory search --query "authentication best practices" --limit 5
Retrieve Entry
Retrieve a specific memory entry by key
npx @claude-flow/cli memory get --key "[key]" --namespace [namespace]
Example:
npx @claude-flow/cli memory get --key "auth-jwt-pattern" --namespace patterns
List Entries
List all entries in a namespace
npx @claude-flow/cli memory list --namespace [namespace]
Example:
npx @claude-flow/cli memory list --namespace patterns --limit 20
Delete Entry
Delete a memory entry
npx @claude-flow/cli memory delete --key "[key]" --namespace [namespace]
Initialize HNSW Index
Initialize HNSW vector search index
npx @claude-flow/cli memory init --enable-hnsw
Memory Stats
Show memory usage statistics
npx @claude-flow/cli memory stats
Export Memory
Export memory to JSON
npx @claude-flow/cli memory export --output memory-backup.json
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.
- yesterday First seen · 127 lines · 95 tokens per session scan A 57ecdd02b607
memory-management is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (473 stars, last pushed 3d ago), licensed MIT. It adds 95 tokens to every session and 787 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-management, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
hindsight-local
Store user preferences, learnings from tasks, and procedure outcomes. Use to remember what works and recall context before new tasks. (user).
sl_capture
How to capture new reusable patterns into ktx's semantic layer - when a measure, segment, or join belongs in the catalog and how to write it generically so it stays small and useful over time. Loaded by the post-turn memory-agent only. The research agent does not write to the SL.
ax-agent-context
This skill helps an LLM pick the right AxAgent context tool for a job - contextMap for recurring corpora, contextPolicy presets for within-run trajectory compaction, agent.optimize for offline GEPA instruction/demo tuning, agent.playbook for an evolving context playbook (offline evolve + online update), and…
cocohealth
Context utilization monitor — background monitor that samples context window utilization via PostToolUse hook, surfaces advisory at 60% and critical warning with recovery decision matrix at 70%.
memory-md-management
Provides comprehensive memory file management capabilities including auditing, quality assessment, and targeted improvements for files such as CLAUDE.md. Use when user asks to check, audit, update, improve, fix, maintain, or validate project memory files. Also triggers for "project memory optimization", "CLAUDE.md…
authoring-claude-md
Creating and maintaining CLAUDE.md project memory files and .claude/rules/ rule files that provide non-obvious codebase context. Use when (1) creating a new CLAUDE.md for a project, (2) adding architectural patterns or design decisions to existing CLAUDE.md, (3) capturing project-specific conventions that aren't…