Skip to content
Skill

Extracting browser history artifacts

Extract and analyze browser history, cookies, cache, downloads, and bookmarks from Chrome, Firefox, and Edge for forensic evidence of user w

Install
Scripts
None
Platforms
Claude Code, Codex, Cursor
GitHub stars
72
Last commit
18 days ago
License
Apache-2.0
Listing updated
today

When your agent uses it

Extract and analyze browser history, cookies, cache, downloads, and bookmarks from Chrome, Firefox, and Edge for forensic evidence of user web activity.

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 1 file (11 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Install

This skill ships in the asi plugin. In Claude Code, add the marketplace and install the plugin (it may include other skills too):

/plugin marketplace add plurigrid/asi
/plugin install asi@asi

Or copy only this skill to ~/.claude/skills/extracting-browser-history-artifacts:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/plurigrid/asi.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/extracting-browser-history-artifacts &&
cp -R "$tmp/plugins/asi/skills/extracting-browser-history-artifacts" ~/.claude/skills/extracting-browser-history-artifacts &&
rm -rf "$tmp"

For one project only, put the folder in .claude/skills/extracting-browser-history-artifacts inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/extracting-browser-history-artifacts to use it in every repository:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/plurigrid/asi.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/extracting-browser-history-artifacts &&
cp -R "$tmp/plugins/asi/skills/extracting-browser-history-artifacts" ~/.agents/skills/extracting-browser-history-artifacts &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/extracting-browser-history-artifacts inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/extracting-browser-history-artifacts to use it in every project:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/plurigrid/asi.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/extracting-browser-history-artifacts &&
cp -R "$tmp/plugins/asi/skills/extracting-browser-history-artifacts" ~/.cursor/skills/extracting-browser-history-artifacts &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/extracting-browser-history-artifacts inside it instead.

Cursor docs on skills

Run in a terminal (add --scope workspace to install it for the current workspace only):

gemini skills install https://github.com/plurigrid/asi.git --path plugins/asi/skills/extracting-browser-history-artifacts

Or copy the folder to ~/.gemini/skills/extracting-browser-history-artifacts yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/extracting-browser-history-artifacts:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/plurigrid/asi.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/extracting-browser-history-artifacts &&
cp -R "$tmp/plugins/asi/skills/extracting-browser-history-artifacts" ~/.copilot/skills/extracting-browser-history-artifacts &&
rm -rf "$tmp"

For one project only, put the folder in .github/skills/extracting-browser-history-artifacts inside it instead.

VS Code docs on skills

Get the folder:

git clone --depth 1 https://github.com/plurigrid/asi.git

Then copy asi/plugins/asi/skills/extracting-browser-history-artifacts into your agent's skills folder as extracting-browser-history-artifacts. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

Extracting browser history artifacts FAQ

How do I install Extracting browser history artifacts in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/extracting-browser-history-artifacts to use it in all your projects, or to .claude/skills/extracting-browser-history-artifacts in one project. Or install the asi plugin, which includes it: /plugin marketplace add plurigrid/asi, then /plugin install asi@asi.

Does Extracting browser history artifacts run scripts?

No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

Which AI agents can use Extracting browser history artifacts?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

What are the best alternatives to Extracting browser history artifacts?

The closest alternatives to Extracting browser history artifacts are Playwright automation fill in form, Playwright explore website, Playwright, Playwright interactive and Azure resource manager playwright dotnet.

More from plurigrid/asi

  1. Org-agenda-like transient views for ASI skill orchestration via nbb/squint + Emacs hydra

    • Open source
    • 72 GitHub stars
  2. Connect and stream from OpenBCI Cyton/Daisy via USB dongle, including first-time radio channel pairing

    • Open source
    • 72 GitHub stars
  3. Hypothesis-Test Loops via REPL for Exploratory Abductive Inference with Gay.jl colors

    • Open source
    • 72 GitHub stars
  4. Layer 4 Learning and Pattern Extraction for Cognitive Surrogate Systems

    • Open source
    • 72 GitHub stars
  5. Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration

    • Open source
    • 72 GitHub stars
  6. Automated code review for pull requests using specialized review patterns

    • Open source
    • 72 GitHub stars
    • Developer tools

Alternatives to Extracting browser history artifacts

  1. Website exploration for testing using Playwright MCP

    • Open source
    • 41.3K GitHub stars
    • Browser automation
  2. Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, U

    • 28.8K GitHub stars
    • Browser automation
  3. Persistent browser and Electron interaction through `js_repl` for fast iterative UI debugging.

    • 28.8K GitHub stars
    • Browser automation
  4. This skill should be used when pages of a web site or app need screenshots for a design, UX or accessibility review - at phone and desktop w

    • Open source
    • 58 GitHub stars
    • Browser automation