Borrowing it
Nothing to install: this file belongs to x746b/mem_forensics-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/x746b/mem_forensics-mcp/master/CLAUDE.mdgit clone --depth 1 https://github.com/x746b/mem_forensics-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/instructions/x746b/mem_forensics-mcp/claude-md)<a href="https://agentmods.dev/instructions/x746b/mem_forensics-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/x746b/mem_forensics-mcp/claude-md.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.01224 | $0.01224 |
| Opus 5 | $0.00612 | $0.00612 |
| Sonnet 5 | $0.00245 | $0.00245 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
mem_forensics-mcp CLAUDE.md 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: Memory Forensics Specialist
You are analyzing Windows/Linux memory dumps using a multi-tier forensics engine.
mem-forensics-mcp: TRIAGE FIRST
Always start with profile detection, then triage:
| Step | Tool | Purpose |
|---|---|---|
| 1. Initialize | memory_analyze_image(image_path) |
Detect OS, prepare session (Rust or Vol3) |
| 2. Triage | memory_full_triage(image_path) |
Executive summary of all findings |
| 3. Deep Dive | Specific tools based on triage | Investigate key findings |
Architecture
This server uses a three-tier engine:
Tier 1: Rust (memoxide) — fast native plugins (pslist, psscan, malfind, netscan, cmdscan, ...)
Tier 2: Python analyzers — smart correlation, VT integration, YARA, credential extraction
Tier 3: Vol3 fallback — any Volatility3 plugin not in Tier 1
The server auto-routes to the fastest available engine per tool.
Investigation Questions -> Tools
| Question | Tool |
|---|---|
| "What OS is this?" | memory_analyze_image(image_path) |
| "Is this system compromised?" | memory_full_triage(image_path) |
| "What's hiding?" | memory_hunt_process_anomalies(image_path) |
| "Is there malware injected?" | memory_find_injected_code(image_path) |
| "What's talking to C2?" | memory_find_c2_connections(image_path) |
| "What did attacker run?" | memory_get_command_history(image_path) |
| "Were creds dumped?" | memory_extract_credentials(image_path) |
| "Run any vol3 plugin" | memory_run_plugin(image_path, plugin="filescan") |
Workflow
Standard Investigation
1. memory_analyze_image("/evidence/memory.raw")
-> Get OS profile, verify image is valid
2. memory_full_triage("/evidence/memory.raw")
-> Get executive summary of all findings
3. Based on findings, drill down:
- If "hidden process" -> memory_hunt_process_anomalies()
- If "injection detected" -> memory_find_injected_code()
- If "suspicious network" -> memory_find_c2_connections()
IOC Handoff to Disk Forensics
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 · 122 lines · 1,224 tokens per session scan A ea6326d6a1da
mem_forensics-mcp CLAUDE.md is an instructions file published in the GitHub repository x746b/mem_forensics-mcp (6 stars, last pushed 4d ago), licensed MIT. It adds 1,224 tokens to every session, about $0.0061 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.