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/timeline-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/timeline-analyst)<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.
<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>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.00056 | $0.03073 |
| Opus 5 | $0.00028 | $0.01537 |
| Sonnet 5 | $0.00011 | $0.00615 |
| Haiku 4.5 | $0.00006 | $0.00307 |
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.
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_findingdescription. 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.
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.
- 11d ago First seen · 211 lines · 56 tokens per session scan A 9e576c1c1648
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.
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.
Messaging Architect
Message house development and value proposition frameworks for SaaS.