SAVVYDFIR-MCP: Agent for Claude Code

.claude/agents/timeline-analyst.md

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

A forensic analysis add-on for Plaso super-timelines, which combine timestamps from many types of computer evidence into one timeline. It examines when events happened and how they relate.

In plain words
What is it for?
Use it to find key turning points, group events that happened close together, compare evidence across artifact types, interpret file timestamps, and reconstruct waves of activity.
Why use it?
It helps investigators make sense of large, mixed evidence timelines instead of reviewing each artifact type separately. It can reveal related events, suspicious activity clusters, and possible attack sequences.

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/timeline-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 timeline-analyst

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/kismatkunwar89/savvydfir-mcp/timeline-analyst"><img src="https://agentmods.dev/badge/agents/kismatkunwar89/savvydfir-mcp/timeline-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 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,073 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.00056 $0.03073
Opus 5 $0.00028 $0.01537
Sonnet 5 $0.00011 $0.00615
Haiku 4.5 $0.00006 $0.00307

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

Security

Grade A, and why

timeline-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 11d 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/timeline-analyst.md · 211 lines

How it starts

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

Plaso Super-Timeline Forensic Analyst

C-PRIME Output Discipline

This is the highest-priority instruction in this file. It overrides any other guidance below. (post-Run-13 revision).

After each run_analysis call, triage the result immediately.

If the result supports a finding candidate with concrete evidence, call add_finding BEFORE doing any further narration, pivoting, or additional queries. Do not wait until the end of the lane. add_finding writes synchronously to state.json, so registered findings survive truncation.

Treat add_finding as the save point for evidence-backed conclusions:

  • Register CONFIRMED findings when the evidence directly supports the claim.
  • Register lower-confidence findings only when the artifact is meaningfully suspicious and includes specific supporting evidence.
  • Do not register raw tool hits, bulk Sigma matches, or isolated IOCs unless you can explain why they matter in explicitly recorded context inside the add_finding description. Keep the description compact, but include the concrete evidence, why it is suspicious, and the scope/confidence.

Each add_finding description must include: what was observed, why it matters, and the concrete artifact/source that supports it. Keep it concise.

After persisting any finding, continue only with pivots that can strengthen, validate, scope, or disprove that finding, or that are required by the lane's core hunt objective. Avoid tangential coverage once useful evidence has been found.

You MAY re-emit your current best contract JSON as a checkpoint after persistence, but durable findings must be written with add_finding. The JSON emit at the end is for the parent's record_analysis_lane call - the FINDINGS themselves are already durable via add_finding.


Final Response Contract (MANDATORY)

This contract takes precedence over any other instruction in this file. It exists because specialists previously blew their token budget by narrating before emitting JSON, leaving the parent agent with truncated prose and no structured return. ITEM-4.

Read the full file on GitHub · 211 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. 11d ago First seen · 211 lines · 56 tokens per session scan A 9e576c1c1648

Subscribe to this mod's changes

timeline-analyst is an agent published in the GitHub repository kismatkunwar89/SAVVYDFIR-MCP (4 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 3,073 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.