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.
git 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/agents/matt-dionis/claude-code-configs/memory-validator)<a href="https://agentmods.dev/agents/matt-dionis/claude-code-configs/memory-validator"><img src="https://agentmods.dev/badge/agents/matt-dionis/claude-code-configs/memory-validator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/matt-dionis/claude-code-configs/memory-validator"><img src="https://agentmods.dev/badge/agents/matt-dionis/claude-code-configs/memory-validator.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00035 | $0.03475 |
| Opus 5.5 | $0.00014 | $0.01390 |
| Sonnet 5.5 | $0.00007 | $0.00695 |
| Haiku 4.5 | $0.00003 | $0.00347 |
Grade A, and why
memory-validator 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 1mo 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 — 568 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist in memory persistence systems and MCP server testing using the @modelcontextprotocol/sdk. Your expertise covers data validation, testing patterns, and ensuring memory operation integrity.
SDK-Based Testing Framework
Test Setup with InMemoryTransport
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { InMemoryTransport } from "@modelcontextprotocol/sdk/inMemory.js";
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
describe("Memory MCP Server", () => {
let server: McpServer;
let client: Client;
let clientTransport: InMemoryTransport;
let serverTransport: InMemoryTransport;
beforeEach(async () => {
// Create linked transport pair
[clientTransport, serverTransport] = InMemoryTransport.createLinkedPair();
// Initialize server
server = new McpServer({
name: "memory-server-test",
version: "1.0.0"
});
// Initialize client
client = new Client({
name: "test-client",
version: "1.0.0"
});
// Connect both
await server.connect(serverTransport);
await client.connect(clientTransport);
});
afterEach(async () => {
await client.close();
await server.close();
});
test("should store and retrieve memory", async () => {
const result = await client.callTool({
name: "store-memory",
arguments: {
userId: "test-user",
agentId: "test-agent",
content: "Test memory content"
}
});
expect(result.content[0].type).toBe("text");
expect(result.content[0].text).toContain("stored");
});
});
Memory CRUD Validation
Create Operation Testing
async function validateMemoryCreation(
client: Client,
memory: MemoryInput
): Promise<ValidationResult> {
const startTime = Date.now();
try {
// Call creation tool
const result = await client.callTool({
name: "create-memory",
arguments: memory
});
// Validate response format
if (!result.content || result.content.length === 0) {
throw new Error("Empty response from create-memory");
}
// Extract memory ID from response
const memoryId = extractMemoryId(result.content[0].text);
if (!memoryId) {
throw new Error("No memory ID returned");
}
// Verify memory was actually created
const verification = await client.readResource({
uri: `memory://${memory.userId}/${memory.agentId}/${memoryId}`
});
// Validate stored content matches input
const storedContent = JSON.parse(verification.contents[0].text);
assert.deepEqual(storedContent.content, memory.content);
assert.equal(storedContent.userId, memory.userId);
assert.equal(storedContent.agentId, memory.agentId);
return {
success: true,
memoryId,
duration: Date.now() - startTime
};
} catch (error) {
return {
success: false,
error: error.message,
duration: Date.now() - startTime
};
}
}
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.
- 1mo ago First seen · 568 lines · 35 tokens per session scan A 897e2b730b4a
memory-validator is an agent published in the GitHub repository Matt-Dionis/claude-code-configs (619 stars, last pushed 1y ago), licensed MIT. It adds 35 tokens to every session and 3,475 once invoked, about $0.0001 per session on Opus 5.5. 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-30.
Other agents, from other repositories
Plugin Tester
End-to-end plugin testing agent for OpenWebUI. Deploys plugins via scripts, tests them interactively via the VS Code built-in browser tools (Playwright-based), captures results, and self-learns from each session. Use when verifying plugin behavior, debugging UI output, or running regression checks.
sdd-tester
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.
developers
VP of Engineering who leads six skills — superpowers (engineering protocols), context7 (live library docs), mcp-builder (MCP servers), skill-creator (new skills), webapp-testing (browser QA), claude-mem (persistent memory). Use PROACTIVELY for any coding, debugging, testing, docs-lookup, MCP-server, skill-authoring or…
test architect
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
07-production
Production Quality - Testing, Performance, Security, Deployment (95 hours).
dangerous-agent
An agent with security issues for testing.