SAVVYDFIR-MCP: Agent for Claude Code

.claude/agents/amcache-analyst.md

amcache-analyst is an agent for Claude Code from kismatkunwar89/SAVVYDFIR-MCP. It costs 67 tokens per session (3,540 once invoked), scanned A, original, MIT.

A specialist guide for examining Windows Amcache records, which can show that executable files were present on a computer. It focuses on hashes, renamed or deleted files, drivers, and compilation-time clues.

In plain words
What is it for?
Use it to identify suspicious executables by SHA-1 hash, investigate renamed or deleted malware, profile vulnerable drivers, and document historical file presence.
Why use it?
It helps distinguish evidence that a file existed from evidence that it actually ran, while preserving targeted queries and supporting details for findings.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is kismatkunwar89/SAVVYDFIR-MCP's own configuration. It tells Claude Code how to work on SAVVYDFIR-MCP itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything SAVVYDFIR-MCP configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/kismatkunwar89/SAVVYDFIR-MCP/master/.claude/agents/amcache-analyst.md
Clone the repo
git clone --depth 1 https://github.com/kismatkunwar89/SAVVYDFIR-MCP

Made for: Claude Code.

Wrote 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.

agentmods badge for amcache-analyst

README.md
[![agentmods](https://agentmods.dev/badge/agents/kismatkunwar89/savvydfir-mcp/amcache-analyst/github.svg)](https://agentmods.dev/agents/kismatkunwar89/savvydfir-mcp/amcache-analyst)
Your own site
<a href="https://agentmods.dev/agents/kismatkunwar89/savvydfir-mcp/amcache-analyst"><img src="https://agentmods.dev/badge/agents/kismatkunwar89/savvydfir-mcp/amcache-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.

agentmods 80×15 button for amcache-analyst

Your own site · 80×15
<a href="https://agentmods.dev/agents/kismatkunwar89/savvydfir-mcp/amcache-analyst"><img src="https://agentmods.dev/badge/agents/kismatkunwar89/savvydfir-mcp/amcache-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,540 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00067 $0.03540
Opus 5 $0.00034 $0.01770
Sonnet 5 $0.00013 $0.00708
Haiku 4.5 $0.00007 $0.00354

Measured 9d ago against content hash 798b2a5b4dde, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

amcache-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.

.claude/agents/amcache-analyst.md · 271 lines

How it starts

The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Windows Amcache 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

  • NEVER load raw CSV rows into context - write targeted Pandas queries via run_analysis only
  • Schema discovery is mandatory first - AmcacheParser column names differ between versions
  • Every confirmed anomaly gets an immediate add_finding before the next query
  • Call read_state first for case status and attack-window summary, then call get_findings when you need the full prior MFT/Prefetch finding set

Critical Forensic Distinction

Amcache proves PRESENCE, not EXECUTION. The Microsoft Compatibility Appraiser scheduled task scans common folders and populates Amcache automatically - a file can appear here without ever running. To prove execution, corroborate with Prefetch (.pf file) or EVTX EID 4688. However, Amcache proving PRESENCE of a deleted file is still powerful - it survives secure deletion and proves the file was on the system.

What Amcache Tells You

  • SHA-1 hash (FileId/SHA1): calculated for files up to ~31.4 MB - the most powerful field; identifies renamed malware definitively. Note: FileId field prepends 0000 - truncate first 4 zeros to get pure SHA-1
  • FullPath: exact absolute path where the file lived
  • LinkDate: PE internal compilation time - extracted from binary metadata, immune to filesystem timestomping
  • FileKeyLastWriteTimestamp: when Amcache recorded the file - approximates first introduction to the system
  • Publisher: from PE resource metadata - empty or mismatched publisher on system32 path = suspicious
  • FileSize: preserved even if file deleted from disk
  • Program categorisation: InventoryApplicationFile = standalone "loose" executable; InventoryApplication = formally installed package

Read the full file on GitHub · 271 lines

Changes

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.

  1. 9d ago First seen · 271 lines · 67 tokens per session scan A 798b2a5b4dde

Subscribe to this mod's changes

amcache-analyst is an agent published in the GitHub repository kismatkunwar89/SAVVYDFIR-MCP (4 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 3,540 once invoked, about $0.0003 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.