Browser Forensics with Hindsight

Browser Forensics with Hindsight is a Data skill for Claude Code, published by mukul975 in Anthropic-Cybersecurity-Skills.

27.8K stars3.4K forkson mukul975/Anthropic-Cybersecurity-SkillsAdded 2026/08/14Repository updated 2026/08/08

View source on GitHub Download repo ZIP

ai-agentsclaude-codecloud-securitycybersecuritydevsecopsethical-hackingincident-responseinfosecllmmalware-analysismcpmitre-attacknist-csfosintpenetration-testingred-teamsecuritysecurity-automationthreat-huntingthreat-intelligence

Install in seconds

Install Browser Forensics with Hindsight

Copy Browser Forensics with Hindsight into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/analyzing-browser-forensics-with-hindsight ~/.claude/skills/analyzing-browser-forensics-with-hindsight

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/analyzing-browser-forensics-with-hindsight/SKILL.md in mukul975/Anthropic-Cybersecurity-Skills
Installs to: ~/.claude/skills/analyzing-browser-forensics-with-hindsight
Collection: One of 25 skills cataloged from this repository
Category: Data — 668 skills

What Browser Forensics with Hindsight does

Browser Forensics with Hindsight parses Chromium-based browser databases (Chrome, Edge, Brave, Opera, Vivaldi) to extract and correlate web activity artifacts into a unified timeline for incident response, insider-threat investigations, and criminal cases.

Browser Forensics with Hindsight is cataloged under Data on DirSkills. Browser Forensics with Hindsight comes from a repository tagged ai-agents, claude-code, cloud-security, cybersecurity and devsecops.

Documentation

README

Excerpt

Analyzing Browser Forensics with Hindsight

Overview

Hindsight is an open-source browser forensics tool designed to parse artifacts from Google Chrome and other Chromium-based browsers (Microsoft Edge, Brave, Opera, Vivaldi). It extracts and correlates data from multiple browser database files to create a unified timeline of web activity. Hindsight can parse URLs, download history, cache records, bookmarks, autofill records, saved passwords, preferences, browser extensions, HTTP cookies, Local Storage (HTML5 cookies), login data, and session/tab information. The tool produces chronological timelines in multiple output formats (XLSX, JSON, SQLite) that enable investigators to reconstruct user web activity for incident response, insider threat investigations, and criminal cases.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Browser Forensics with Hindsight

What else does mukul975 publish alongside Browser Forensics with Hindsight?
Browser Forensics with Hindsight is one of 25 skills that DirSkills catalogs from mukul975/Anthropic-Cybersecurity-Skills, the repository it ships in. Its siblings there include API Gateway Log Analysis, Abusing DPAPI for Credential Access and Achieving CMMC Level 2 Compliance. Each one is a separate skill with its own page in this directory, installs the same way Browser Forensics with Hindsight does, and is maintained by mukul975 in that same repository. The rest of the collection is listed on the mukul975/Anthropic-Cybersecurity-Skills page.
How does Browser Forensics with Hindsight compare to other Data skills?
Browser Forensics with Hindsight ranks #63 by stars among the 668 Data skills in this catalog. The most-starred ones next to it are Benchmark Methodology, Jupyter Notebook and Solana. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Browser Forensics with Hindsight against them. Open each page to compare what they document and how they install.