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/danielsimonjr/memory-mcp/exploregit clone --depth 1 https://github.com/danielsimonjr/memory-mcpWrote 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/danielsimonjr/memory-mcp/explore)<a href="https://agentmods.dev/commands/danielsimonjr/memory-mcp/explore"><img src="https://agentmods.dev/badge/commands/danielsimonjr/memory-mcp/explore.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.00011 | $0.01023 |
| Opus 5 | $0.00005 | $0.00511 |
| Sonnet 5 | $0.00002 | $0.00205 |
| Haiku 4.5 | $0.00001 | $0.00102 |
Grade A, and why
EXPLORE 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 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.
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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Exploration & Knowledge Indexing
Explore the current project, index key information to memory, and optionally update CLAUDE.md.
Instructions
Perform a comprehensive project exploration and knowledge update:
Phase 1: Gather Current State
-
Get project metadata:
# Package info cat package.json | head -30 # Git status git log --oneline -10 git status --short -
Count and analyze source files:
# TypeScript files find src -name "*.ts" | wc -l # Test files find src -name "*.test.ts" | wc -l -
Check for recent changes:
git diff --stat HEAD~5 -
Review key entry points:
- Read
src/memory/index.ts - Check
src/memory/server/toolDefinitions.tsfor tool count - Scan for new files not in CLAUDE.md
- Read
Phase 2: Update Knowledge Graph
-
Search for existing project entity:
- Use
search_nodeswith "memory-mcp"
- Use
-
Create or update project entity:
- If not exists: Create entity with type "project"
- Add observations about current state:
- Version number
- Tool count
- Test count
- Recent changes summary
- Key architectural patterns
-
Create entities for new components:
- Any new managers or major classes
- New tool categories
- New features discovered
-
Update relations:
- Connect components to the main project
- Map dependencies between modules
Phase 3: CLAUDE.md Update (if --update-claude-md)
If --update-claude-md flag is provided, analyze and update CLAUDE.md:
-
Check for discrepancies:
- Version number in package.json vs CLAUDE.md
- Tool count (grep toolDefinitions.ts vs documented 47)
- Test count (run quick test --dry-run or count test files)
- File counts per module
- Dependencies in package.json vs documented
-
Update outdated sections:
- Version numbers
- Tool counts
- Test statistics
- Dependency versions
- New slash commands in commands list
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 · 149 lines · 11 tokens per session scan A 9db5f2b0c49c
EXPLORE is a command published in the GitHub repository danielsimonjr/memory-mcp (3 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 1,023 once invoked, about $0.0001 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-31.
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.