analyzing-windows-lnk-files-for-artifacts

analyzing-windows-lnk-files-for-artifacts is a skill for Claude Code from 26zl/cybersec-toolkit. It costs 36 tokens per session (3,202 once invoked), scanned A, a copy of analyzing-windows-lnk-files-for-artifacts, MIT.

A digital-forensics guide for reading Windows LNK files, the shortcut files Windows creates for documents, programs, folders, and locations. These files can retain paths, timestamps, drive details, and computer identifiers.

In plain words
What is it for?
Use it to examine Recent Items, Desktop, Quick Launch, and other shortcuts, then trace accessed files, network shares, and removable drives.
Why use it?
It helps reconstruct which files or network locations a user may have opened, even when the original file is unavailable. It adds user-activity clues to an incident timeline.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Part of the cybersec-toolkit plugin — 197 skills, 2 hooks, 1 MCP server shipped together

Good fit Use it to examine Recent Items, Desktop, Quick Launch, and other shortcuts, then trace accessed files, network shares, and removable drives.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/26zl/cybersec-toolkit/analyzing-windows-lnk-files-for-artifacts
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add 26zl/cybersec-toolkit --skill analyzing-windows-lnk-files-for-artifacts
Clone the repo
git clone --depth 1 https://github.com/26zl/cybersec-toolkit

Made for: Claude Code.

Or install cybersec-toolkit, the plugin that ships this one along with the rest of its 197 skills, 2 hooks, 1 MCP server.

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 analyzing-windows-lnk-files-for-artifacts

README.md
[![agentmods](https://agentmods.dev/badge/skills/26zl/cybersec-toolkit/analyzing-windows-lnk-files-for-artifacts/github.svg)](https://agentmods.dev/skills/26zl/cybersec-toolkit/analyzing-windows-lnk-files-for-artifacts)
Your own site
<a href="https://agentmods.dev/skills/26zl/cybersec-toolkit/analyzing-windows-lnk-files-for-artifacts"><img src="https://agentmods.dev/badge/skills/26zl/cybersec-toolkit/analyzing-windows-lnk-files-for-artifacts/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 analyzing-windows-lnk-files-for-artifacts

Your own site · 80×15
<a href="https://agentmods.dev/skills/26zl/cybersec-toolkit/analyzing-windows-lnk-files-for-artifacts"><img src="https://agentmods.dev/badge/skills/26zl/cybersec-toolkit/analyzing-windows-lnk-files-for-artifacts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,202 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 86% copy Near-identical to another mod 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.00036 $0.03202
Opus 5 $0.00018 $0.01601
Sonnet 5 $0.00007 $0.00640
Haiku 4.5 $0.00004 $0.00320

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

Security

Grade A, and why

analyzing-windows-lnk-files-for-artifacts 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 7d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/agent.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

86% identical to analyzing-windows-lnk-files-for-artifacts — 21 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/analyzing-windows-lnk-files-for-artifacts/SKILL.md · 329 lines

How it starts

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

Analyzing Windows LNK Files for Artifacts

When to Use

  • When reconstructing user file access history from Windows shortcut files
  • For tracking accessed files, network shares, and removable media
  • During investigations to prove a user opened specific documents
  • When correlating file access with other timeline artifacts
  • For identifying accessed paths on remote systems or USB devices

Prerequisites

  • Access to LNK files from forensic image (Recent, Desktop, Quick Launch)
  • LECmd (Eric Zimmerman), python-lnk, or LnkParser for analysis
  • Understanding of LNK file structure (Shell Link Binary format)
  • Knowledge of LNK file locations on Windows systems
  • Forensic workstation with analysis tools installed

Workflow

Step 1: Collect LNK Files from Forensic Image

# Mount forensic image
mount -o ro,loop,offset=$((2048*512)) /cases/case-2024-001/images/evidence.dd /mnt/evidence

mkdir -p /cases/case-2024-001/lnk/{recent,desktop,startup,custom}

# Copy Recent items LNK files (primary source)
cp /mnt/evidence/Users/*/AppData/Roaming/Microsoft/Windows/Recent/*.lnk \
   /cases/case-2024-001/lnk/recent/ 2>/dev/null

# Copy automatic destinations (Jump Lists)
cp /mnt/evidence/Users/*/AppData/Roaming/Microsoft/Windows/Recent/AutomaticDestinations/*.automaticDestinations-ms \
   /cases/case-2024-001/lnk/recent/ 2>/dev/null

# Copy custom destinations (pinned Jump List items)
cp /mnt/evidence/Users/*/AppData/Roaming/Microsoft/Windows/Recent/CustomDestinations/*.customDestinations-ms \
   /cases/case-2024-001/lnk/custom/ 2>/dev/null

# Copy Desktop shortcuts
cp /mnt/evidence/Users/*/Desktop/*.lnk /cases/case-2024-001/lnk/desktop/ 2>/dev/null

# Copy Startup folder shortcuts (persistence)
cp /mnt/evidence/Users/*/AppData/Roaming/Microsoft/Windows/Start\ Menu/Programs/Startup/*.lnk \
   /cases/case-2024-001/lnk/startup/ 2>/dev/null
cp "/mnt/evidence/ProgramData/Microsoft/Windows/Start Menu/Programs/Startup"/*.lnk \
   /cases/case-2024-001/lnk/startup/ 2>/dev/null

# Find all LNK files on the system
find /mnt/evidence/ -name "*.lnk" -type f 2>/dev/null > /cases/case-2024-001/lnk/all_lnk_locations.txt

# Count and hash
ls /cases/case-2024-001/lnk/recent/ | wc -l
sha256sum /cases/case-2024-001/lnk/recent/*.lnk > /cases/case-2024-001/lnk/lnk_hashes.txt 2>/dev/null

Read the full file on GitHub · 329 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 7d ago First seen · 329 lines · 36 tokens per session scan A 1204c4d2319f

Subscribe to this mod's changes

analyzing-windows-lnk-files-for-artifacts is a skill published in the GitHub repository 26zl/cybersec-toolkit (54 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 3,202 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to analyzing-windows-lnk-files-for-artifacts, differing in 21 lines, and is treated as a copy.

Related

Other skills, from other repositories

analyzing-windows-lnk-files-for-artifacts

Parse Windows LNK shortcut files to extract target paths, timestamps, volume information, and machine identifiers for forensic timeline reconstruction.

xalgorix/xalgorix · 36 tokens

analyzing-windows-lnk-files-for-artifacts

Use when parse Windows LNK shortcut files to extract target paths, timestamps, volume information, and machine identifiers for forensic timeline reconstruction. Use when working with analyzing windows lnk files for artifacts.

oyi77/1ai-skills · 50 tokens

analyzing-windows-lnk-files-for-artifacts

Parse Windows LNK shortcut files to extract target paths, timestamps, volume information, and machine identifiers for forensic timeline reconstruction.

pinkpixel-dev/skills-collection-1 · 36 tokens

analyzing-windows-lnk-files-for-artifacts

Parse Windows LNK shortcut files to extract target paths, MAC timestamps, volume serial numbers, and machine identifiers for forensic timeline reconstruction. Use when investigating recently-accessed files, tracking removable media or network paths referenced by shortcuts, or building a DFIR timeline from LNK…

Youngmaidainon/Agent-Level-Up · 67 tokens

analyzing-windows-lnk-files-for-artifacts

Parse Windows LNK shortcut files to extract target paths, timestamps, volume information, and machine identifiers for forensic timeline reconstruction.

marysatasselshaped667/skills-collection-1 · 36 tokens

analyzing-windows-lnk-files-for-artifacts

Parse Windows LNK shortcut files to extract target paths, timestamps, volume information, and machine identifiers for forensic timeline reconstruction.

autohandai/community-skills · 36 tokens