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/depsgit 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/deps)<a href="https://agentmods.dev/commands/danielsimonjr/memory-mcp/deps"><img src="https://agentmods.dev/badge/commands/danielsimonjr/memory-mcp/deps.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.1 | $0.00006 | $0.00382 |
| Opus 5 | $0.00003 | $0.00191 |
| Sonnet 5 | $0.00001 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
DEPS 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 6d 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.
What it actually says
Dependency Graph Analysis
Generate a dependency graph for a TypeScript project and provide analysis.
Instructions
- Run the dependency graph tool:
C:\mcp-servers\memory-mcp\tools\create-dependency-graph\create-dependency-graph.exe $ARGUMENTS
-
After generation, locate and read the output files:
dependency-graph.json- Full graph datadependency-summary.md- Human-readable summary (if generated)
-
Provide analysis including:
- Total files and modules
- Circular dependencies (if any)
- Most connected files (hot paths)
- Module structure overview
Usage Examples
# Generate graph for current directory
/project:DEPS
# Generate graph for specific project
/project:DEPS C:\mcp-servers\deepthinking-mcp
# Generate and focus on summary
/project:DEPS . --summary
Output Files
The tool generates several files in the project's docs/architecture/ directory:
| File | Purpose |
|---|---|
dependency-graph.json |
Full dependency data |
dependency-graph.yaml |
YAML format (if enabled) |
dependency-summary.compact.json |
CTON-compressed for LLM context |
unused-analysis.md |
Potentially unused files/exports |
Analysis Focus Areas
- Circular Dependencies - Runtime vs type-only
- Hot Paths - Files with most imports/exports
- Module Boundaries - How code is organized
- Unused Code - Files/exports that may be dead code
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.
- 6d ago First seen · 59 lines · 6 tokens per session scan A d2409f8fe48b
DEPS is a command published in the GitHub repository danielsimonjr/memory-mcp (3 stars, last pushed 2d ago), licensed MIT. It adds 6 tokens to every session and 382 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-31.
Other commands, from other repositories
step-research
Always research before proposing a fix. The Untether bug you're chasing is often a known upstream engine quirk, a previously-fixed regression, or a documented config gotcha.
iterate-feature
Iterate on the feature "$ARGUMENTS" to fix issues and address feedback.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor.es
Diagnostica problemas de inferencia LLM en Mac: asiai doctor verifica el estado de los motores, conflictos de puertos, carga de modelos y estado de la GPU.