analyzing-windows-lnk-files-for-artifacts

analyzing-windows-lnk-files-for-artifacts is a skill for Claude Code from oyi77/1ai-skills. It costs 50 tokens per session (934 once invoked), scanned A, original, MIT.

A digital-forensics guide for examining Windows LNK files, which are shortcut files that record details about opened files, locations, and devices. It extracts paths, timestamps, volume information, and machine identifiers.

In plain words
What is it for?
Use it to trace opened documents, network shares, removable media, and remote paths during a Windows investigation.
Why use it?
It helps investigators reconstruct file-access activity when other records are incomplete.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the 1ai-skills plugin — 209 skills, 4 commands shipped together

Good fit Use it to trace opened documents, network shares, removable media, and remote paths during a Windows investigation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oyi77/1ai-skills/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 oyi77/1ai-skills --skill analyzing-windows-lnk-files-for-artifacts
Clone the repo
git clone --depth 1 https://github.com/oyi77/1ai-skills

Made for: Claude Code.

Or install 1ai-skills, the plugin that ships this one along with the rest of its 209 skills, 4 commands.

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/oyi77/1ai-skills/analyzing-windows-lnk-files-for-artifacts/github.svg)](https://agentmods.dev/skills/oyi77/1ai-skills/analyzing-windows-lnk-files-for-artifacts)
Your own site
<a href="https://agentmods.dev/skills/oyi77/1ai-skills/analyzing-windows-lnk-files-for-artifacts"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/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/oyi77/1ai-skills/analyzing-windows-lnk-files-for-artifacts"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/analyzing-windows-lnk-files-for-artifacts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 934 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00050 $0.00934
Opus 5 $0.00025 $0.00467
Sonnet 5 $0.00010 $0.00187
Haiku 4.5 $0.00005 $0.00093

Measured 8d ago against content hash 7f6f2afcf8b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 8d 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.

cybersecurity/_deprecated/analyzing-windows-lnk-files-for-artifacts/SKILL.md · 110 lines

How it starts

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

Analyzing Windows Lnk Files For Artifacts

Overview

Cybersecurity skill for analyzing windows lnk files for artifacts. Follows industry best practices and security standards.

When to Use

Trigger phrases:

  • "analyzing windows lnk files for artifacts"

  • "Parse Windows LNK shortcut files to extract target paths, timestamps, volume inf"

  • 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

When NOT to Use

  • When you lack proper authorization for testing
  • For production systems without change management
  • When the task requires legal or compliance expertise beyond technical scope

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

# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> dict:
    return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
  1. Scope the Analysis — Define what windows lnk files artifacts or data sources to examine and the investigation timeline.
  2. Preserve Evidence — Create forensic copies of relevant data. Maintain chain of custody documentation.
  3. Extract Key Indicators — Use artifacts to parse and extract relevant windows lnk files data points from collected artifacts.
  4. Correlate Findings — Cross-reference extracted data with other sources (threat intel, logs, timelines).
  5. Build Timeline — Construct a chronological sequence of events related to windows lnk files.
  6. Document Analysis — Write findings report with evidence, conclusions, and recommendations.

Read the full file on GitHub · 110 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. 8d ago First seen · 110 lines · 50 tokens per session scan A 7f6f2afcf8b4

Subscribe to this mod's changes

analyzing-windows-lnk-files-for-artifacts is a skill published in the GitHub repository oyi77/1ai-skills (12 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 934 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-09-04.

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

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

26zl/cybersec-toolkit · 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.

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