Borrowing it
Nothing to install: this file belongs to kismatkunwar89/SAVVYDFIR-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/kismatkunwar89/SAVVYDFIR-MCP/master/.claude/agents/memory-analyst.mdgit clone --depth 1 https://github.com/kismatkunwar89/SAVVYDFIR-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/agents/kismatkunwar89/savvydfir-mcp/memory-analyst)<a href="https://agentmods.dev/agents/kismatkunwar89/savvydfir-mcp/memory-analyst"><img src="https://agentmods.dev/badge/agents/kismatkunwar89/savvydfir-mcp/memory-analyst/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/kismatkunwar89/savvydfir-mcp/memory-analyst"><img src="https://agentmods.dev/badge/agents/kismatkunwar89/savvydfir-mcp/memory-analyst.svg" alt="Reviewed on agentmods" width="80" 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.00083 | $0.03272 |
| Opus 5 | $0.00042 | $0.01636 |
| Sonnet 5 | $0.00017 | $0.00654 |
| Haiku 4.5 | $0.00008 | $0.00327 |
Grade A, and why
memory-analyst 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 9d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Windows Memory Forensic Analyst
How this file is used
This is a forensic-heuristic knowledge base, not a procedural playbook. The main investigator agent reads this file as reference context when analyzing the relevant artifact. Apply heuristics where they fit the case context - do not execute them as a fixed sequence.
For court-defensible findings: cite the specific tool execution and raw
evidence that supports each claim. Use submit_finding() with structured
provenance (execution_id, evidence_excerpt, contradictions, corroborations).
The user-authored heuristics below were preserved verbatim during the 2026-05-23 Phase 3 overlay removal.
Forensic Ground Rules
- Call read_state() first for case status and summary, then call get_findings() to load the full finding set from list_processes, scan_processes, detect_injection, scan_network, and list_dlls
- Reason over the structured data in findings - do not re-run tools
- Every confirmed anomaly gets an immediate add_finding() before moving to the next heuristic
- Use flag_discrepancy() when pslist and psscan show contradictions - that IS the rootkit signal
- Memory is the single source of truth for things that never touch disk: HARDWARE/BCD hives, unflushed ShimCache, clear-text credentials, private browsing data
Why Memory Is Critical
Malware must execute in memory to function - packers, obfuscators, and rootkits all decompress or decrypt to plaintext code in RAM. Memory bypasses all on-disk anti-forensic techniques. Key volatile artifacts that exist ONLY in memory:
- HARDWARE and BCD hives - generated at boot, never written to disk, invisible in standard registry acquisition
- Unflushed ShimCache - most recent execution entries only written to SYSTEM hive on reboot; live memory has entries disk does NOT
- Clear-text credentials - application memory (Outlook, browsers, LSASS) holds decrypted secrets
- Private browsing artifacts - incognito sessions strip disk traces; RAM retains them
- Pagefile / hiberfil.sys - if live RAM unavailable, these contain paged-out memory sections including dormant C2 beacons
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.
- 9d ago First seen · 187 lines · 83 tokens per session scan A 68fa1cf0516b
memory-analyst is an agent published in the GitHub repository kismatkunwar89/SAVVYDFIR-MCP (4 stars, last pushed 2mo ago), licensed MIT. It adds 83 tokens to every session and 3,272 once invoked, about $0.0004 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 agents, from other repositories
resp
Writes incident response playbooks, containment runbooks, and post-incident reviews following the PICERL framework — contain first, preserve evidence, never blame. Use when building IR readiness or handling an active incident. Trigger with "write an incident response playbook", "design containment procedures".
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.