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 skills add MarcelRoozekrans/memorylens-mcp --skill memorylensgit clone --depth 1 https://github.com/MarcelRoozekrans/memorylens-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/skills/marcelroozekrans/memorylens-mcp/memorylens)<a href="https://agentmods.dev/skills/marcelroozekrans/memorylens-mcp/memorylens"><img src="https://agentmods.dev/badge/skills/marcelroozekrans/memorylens-mcp/memorylens.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.00027 | $0.00901 |
| Opus 5 | $0.00014 | $0.00451 |
| Sonnet 5 | $0.00005 | $0.00180 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
memorylens 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 8d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MemoryLens — Memory Profiling Skill
Prerequisites
This skill requires the memorylens MCP server tools (list_processes, snapshot, compare_snapshots, analyze, get_rules). Collection happens in-process over EventPipe, so there is nothing to install or verify before profiling — if the MCP tools aren't available at all, inform the user to install the memorylens plugin.
When to Use
- On demand: User requests memory analysis (
/memorylens) - During debugging: When
systematic-debuggingidentifies symptoms like high memory usage, OutOfMemoryException, slow GC, or growing memory over time - During brainstorming: When designing performance-sensitive features that involve caching, event systems, or long-lived objects
Announce Line
"MemoryLens activated. I'll profile your application's memory and suggest concrete fixes."
Workflow
Step 1: Identify target
MemoryLens attaches to an already-running .NET process. It cannot launch one.
- Call
list_processesand let the user pick, or take a pid the user supplies. - If the app is not running yet, ask the user to start it first, then re-run
list_processes. snapshotandcompare_snapshotsboth require apid. Do not passcommand— the parameter is accepted for compatibility but is not implemented, and a call without a pid returns an error.
Step 2: Choose profiling mode
Based on the user's ask:
- "How does my memory look?" → Single
snapshot - "Is there a leak?" / "What changed?" →
compare_snapshots - Unclear → Ask: "Do you want a single snapshot of current state, or a before/after comparison to detect growth?"
Step 3: Capture
Execute snapshot or compare_snapshots with the target parameters.
Step 4: Analyze
Call analyze with the returned snapshotId and nothing else — the id is all it needs.
Rule configuration is not a parameter. The server reads .memorylens.json from its own
working directory once at startup; changing that file needs a server restart to take
effect. Use get_rules to see which rules are currently active.
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.
- 8d ago First seen · 95 lines · 27 tokens per session scan A ccd29869624d
memorylens is a skill published in the GitHub repository MarcelRoozekrans/memorylens-mcp (10 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 901 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.