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/matt-dionis/claude-code-configs/memory-opsgit clone --depth 1 https://github.com/Matt-Dionis/claude-code-configsWrote 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/commands/matt-dionis/claude-code-configs/memory-ops)<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/memory-ops"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/memory-ops.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.00009 | $0.02361 |
| Opus 5 | $0.00005 | $0.01180 |
| Sonnet 5 | $0.00002 | $0.00472 |
| Haiku 4.5 | $0.00001 | $0.00236 |
Grade A, and why
memory-ops scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl https://api.openai.com/v1/embeddings \ How it starts
The opening of the file, as written. The whole thing — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Operations Testing
Test and debug memory operations for the Memory MCP Server focusing on $ARGUMENTS:
Create Memory
Test memory creation with embedding generation:
# Create a simple memory
npx @modelcontextprotocol/cli call create_memory '{
"content": "User prefers dark mode interfaces",
"type": "preference",
"importance": 0.8
}'
# Create memory with expiration
npx @modelcontextprotocol/cli call create_memory '{
"content": "Meeting with team at 3pm tomorrow",
"type": "event",
"importance": 0.9,
"expires_at": "2024-12-31T15:00:00Z"
}'
# Create memory with metadata
npx @modelcontextprotocol/cli call create_memory '{
"content": "Project deadline is March 15",
"type": "task",
"importance": 1.0,
"metadata": {
"project": "Memory MCP Server",
"priority": "high"
}
}'
# Batch memory creation
for i in {1..10}; do
npx @modelcontextprotocol/cli call create_memory "{
\"content\": \"Test memory $i for performance testing\",
\"type\": \"test\",
\"importance\": 0.5
}"
done
Search Memories
Test vector similarity search:
# Basic semantic search
npx @modelcontextprotocol/cli call search_memories '{
"query": "What are the user preferences?",
"limit": 5
}'
# Search with similarity threshold
npx @modelcontextprotocol/cli call search_memories '{
"query": "upcoming meetings and events",
"limit": 10,
"threshold": 0.7
}'
# Search by type
npx @modelcontextprotocol/cli call search_memories '{
"query": "tasks and deadlines",
"filter": {
"type": "task"
},
"limit": 20
}'
# Search with date range
npx @modelcontextprotocol/cli call search_memories '{
"query": "recent activities",
"filter": {
"created_after": "2024-01-01",
"created_before": "2024-12-31"
}
}'
Update Memory
Test memory updates and importance adjustments:
# Update memory content
npx @modelcontextprotocol/cli call update_memory '{
"id": "memory-uuid-here",
"content": "Updated content with new information",
"regenerate_embedding": true
}'
# Adjust importance
npx @modelcontextprotocol/cli call update_memory '{
"id": "memory-uuid-here",
"importance": 0.95
}'
# Extend expiration
npx @modelcontextprotocol/cli call update_memory '{
"id": "memory-uuid-here",
"expires_at": "2025-12-31T23:59:59Z"
}'
# Mark as accessed
npx @modelcontextprotocol/cli call update_memory '{
"id": "memory-uuid-here",
"increment_access_count": true
}'
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.
- 3d ago First seen · 397 lines · 9 tokens per session scan A 51c881faf04a
memory-ops is a command published in the GitHub repository Matt-Dionis/claude-code-configs (625 stars, last pushed 1y ago), licensed MIT. It adds 9 tokens to every session and 2,361 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.