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/testgit 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/test)<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/test"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/test.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.00007 | $0.01608 |
| Opus 5 | $0.00003 | $0.00804 |
| Sonnet 5 | $0.00001 | $0.00322 |
| Haiku 4.5 | $0.00001 | $0.00161 |
Grade A, and why
test 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 4d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory MCP Server Test Generation
Generate comprehensive test cases for $ARGUMENTS with focus on MCP protocol compliance and memory operations:
Unit Tests
MCP Protocol Tests
// Test MCP message handling
describe('MCP Protocol', () => {
it('should handle JSON-RPC 2.0 requests', async () => {
// Test request with id
// Test notification without id
// Test batch requests
});
it('should return proper error codes', async () => {
// -32700: Parse error
// -32600: Invalid request
// -32601: Method not found
// -32602: Invalid params
// -32603: Internal error
});
it('should validate tool parameters with Zod', async () => {
// Test required fields
// Test type validation
// Test nested schemas
});
});
Memory Operations Tests
// Test memory CRUD operations
describe('Memory Operations', () => {
it('should create memory with embeddings', async () => {
// Test successful creation
// Test OpenAI API failure handling
// Test vector dimension validation
});
it('should perform vector similarity search', async () => {
// Test similarity threshold
// Test result limit
// Test empty results
// Test index usage
});
it('should handle memory lifecycle', async () => {
// Test expiration
// Test archival
// Test soft delete
// Test importance decay
});
it('should consolidate memories', async () => {
// Test deduplication
// Test summarization
// Test relationship creation
});
});
Database Tests
// Test database operations
describe('Database Operations', () => {
it('should handle transactions', async () => {
// Test commit on success
// Test rollback on error
// Test isolation levels
});
it('should use pgvector correctly', async () => {
// Test vector operations
// Test distance calculations
// Test index scans
});
it('should maintain referential integrity', async () => {
// Test foreign keys
// Test cascade deletes
// Test orphan prevention
});
});
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.
- 4d ago First seen · 306 lines · 7 tokens per session scan A 929b976955d3
test is a command published in the GitHub repository Matt-Dionis/claude-code-configs (625 stars, last pushed 1y ago), licensed MIT. It adds 7 tokens to every session and 1,608 once invoked, about $0.0000 per session on Opus 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 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.