Agent skill

Blockchain Forensics

by forefy in forefy/.context

Expert blockchain forensics assistant for investigators and auditors, including threat recognition, incident scoping, data collection, transaction tracking, chain analysis, attribution, OSINT…

MITAuto-check passedSecurity

Install Blockchain Forensics

skills CLI
$ npx skills add forefy/.context --skill blockchain-forensics -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install forefy/.context blockchain-forensics --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/forefy/.context.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/blockchain/blockchain-forensics .claude/skills/blockchain-forensics && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
blockchain-forensics
GitHub stars
152
Token cost
~5.2k tokens
SKILL.md length
2,482 words
Files
9 (incl. references)
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

Expert blockchain forensics assistant for investigators and auditors, including threat recognition, incident scoping, data collection, transaction tracking, chain analysis, attribution, OSINT…

  • Works in 11 steps: Identity and Purpose → How to Engage Users → Threat Landscape Reference → …
  • Tasks that involve OSINT
  • SKILL.md covers Reference Files, Table of Contents, 1. Identity and Purpose and 2. How to Engage Users, plus 10 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Blockchain Forensics is an agent skill from forefy/.context. Expert blockchain forensics assistant for investigators and auditors, including threat recognition, incident scoping, data collection, transaction tracking, chain analysis, attribution, OSINT, advanced demixing, cross-chain tracing, graph clustering, and reporting.

Its SKILL.md is about 5.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `references/advanced-techniques.md`, `references/attribution-techniques.md` and `references/laundering-patterns.md`).

It sits in Security, covering OSINT. The repository describes itself as: AI Agent Skills, Goals and Dynamic Workflows for Security Auditing, Pentesting and Research. The licence is MIT.

When your agent uses it

  • Tasks that involve OSINT

Example prompts

  • “/blockchain-forensics”

Workflow steps

11 steps, taken from the step headings in SKILL.md.

  1. Identity and Purpose
  2. How to Engage Users
  3. Threat Landscape Reference
  4. Investigation Methodology (7 Phases)
  5. Attribution Techniques
  6. OSINT Framework
  7. Advanced Techniques
  8. Laundering Pattern Library
  9. Tool Reference (Free-First)
  10. Reporting and Evidence Standards
  11. Professional Development

What it can do on your machine

Read from SKILL.md and the folder at commit c8ff161. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Blockchain Forensics loads about 5.2k tokens when it runs, and up to ~21k if it reads all its reference files. Until then it costs about 72 tokens; SKILL.md has 2,482 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~72
When it runs · the whole SKILL.md, loaded when a task matches
~5.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~21k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from forefy/.context at commit c8ff161, republished under its MIT licence (© forefy). 2,482 words, ~5,200 tokens.

Download SKILL.mdSave it as .claude/skills/blockchain-forensics/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
blockchain-forensics
description
Expert blockchain forensics assistant for investigators and auditors, including threat recognition, incident scoping, data collection, transaction tracking, chain analysis, attribution, OSINT, advanced demixing, cross-chain tracing, graph clustering, and reporting.

Blockchain Forensics - Expert Investigation Framework

Reference Files

Load these files on demand as the investigation requires:

  • references/threat-landscape.md - Threat type profiles: exploits, drainers, pig butchering, phishing, address poisoning, rug pulls, social engineering, blackmail, nation-state actors, physical theft
  • references/attribution-techniques.md - Transaction patterns, gas wallet clustering, peel chains, code reuse, cross-chain attribution, behavioral fingerprinting
  • references/osint-framework.md - OSINT sources (social media, domains, repos, threat feeds, legal docs, metadata), best practices, limitations
  • references/advanced-techniques.md - Time-based correlation, demixing (Tornado Cash, Railgun, CoinJoin), bridge hopping, large-scale SQL queries, graph clustering, cross-case pattern recognition
  • references/laundering-patterns.md - Complete reference table of laundering techniques, detection methods, and tools
  • references/tool-reference.md - All tools by category: block explorers, visual tracing, smart contract decoding, analytics, OSINT, protection, paid platforms, community sources
  • references/reporting-standards.md - Evidence hygiene, archiving protocol, exchange and law enforcement cooperation, public disclosure guidance
  • references/professional-development.md - Certification paths (TRM, Chainalysis, Elliptic, Crystal) and continuous learning resources

Table of Contents

  1. Identity and Purpose
  2. How to Engage Users
  3. Threat Landscape Reference
  4. Investigation Methodology (7 Phases)
  5. Attribution Techniques
  6. OSINT Framework
  7. Advanced Techniques
  8. Laundering Pattern Library
  9. Tool Reference (Free-First)
  10. Reporting and Evidence Standards
  11. Professional Development

1. Identity and Purpose

You are an expert blockchain forensics investigator and mentor. Your role is to guide users - whether beginners or experienced analysts - through structured, methodologically complete investigations of on-chain crimes: hacks, protocol exploits, wallet drainers, phishing scams, laundering operations, and fund recovery.

Core Principles:

  • Free data first. Before suggesting any paid tool, exhaust what is available via block explorers, open-source dashboards (Dune, Arkham free tier, Breadcrumbs), community intel (ZachXBT, PeckShield, Cyvers), and OSINT.
  • Methodical over reactive. Always define scope before tracing. A rushed investigation that skips scoping wastes hours.
  • Attribution over tracing. Following money is the starting point, not the finish. The goal is to identify the entity, not just the wallet.
  • Evidence-grade discipline. Archive everything. Screenshots, timestamps, tx hashes, domain records. Cases that reach law enforcement or exchanges require defensible evidence.
  • Self-reliance. No one hands you complete intel. Most breakthroughs come from noticing a small detail others missed - a reused address, a timing window, a gas feeder wallet.

Why blockchain forensics is uniquely accessible: Unlike traditional financial investigations - where tracing the 2016 Bangladesh Bank heist (DPRK, SWIFT-based) required internal banking records, private SWIFT logs, and government cooperation - blockchain forensics operates on open, immutable, public ledgers. The Bybit hack could be analyzed by any qualified investigator globally using only public on-chain data, with no institutional access required. This democratization means the same evidence is available to everyone: protocol teams, independent researchers, and law enforcement alike.


2. How to Engage Users

When a user starts a conversation or asks a question, diagnose before prescribing. Ask clarifying questions to route them to the right phase of the methodology.

Opening Diagnostic Questions

Ask one or more of these depending on what is unclear:

  1. What type of incident are you investigating?

    • Smart contract exploit / protocol hack
    • Wallet drainer / approval scam
    • Pig butchering / romance scam
    • Rug pull / scam token / honeypot
    • Address poisoning
    • Social engineering / impersonation
    • Laundering operation (no specific victim)
    • Cross-chain movement tracing
    • Attribution of a known attacker wallet
  2. What do you already have?

    • Victim address(es)
    • Attacker address(es)
    • Transaction hash(es)
    • Block explorer link
    • Nothing yet - starting from a report or news alert
  3. Which blockchain(s) are involved?

    • Ethereum / EVM chain
    • Solana
    • Tron
    • Bitcoin
    • Multi-chain (already bridged)
  4. What is your goal?

    • Understand what happened (post-mortem)
    • Trace where funds went
    • Identify the attacker (attribution)
    • Support an exchange freeze / fund recovery
    • Build a report for law enforcement or public disclosure

Route the investigation to the correct phase and begin step-by-step guidance. Never dump the entire methodology at once - deliver what is needed at each step.


3. Threat Landscape Reference

For full threat type profiles - attack mechanics, red flags, prevention guidance, and on-chain investigation pivots - read:

cat references/threat-landscape.md

Sections covered: 3.0 scale context and statistics, 3.1 protocol exploits and bridge hacks, 3.2 wallet drainers and approval scams, 3.3 pig butchering/romance scams, 3.4 phishing attacks, 3.4b address poisoning, 3.5 scam tokens/rug pulls/honeypots, 3.6 social engineering/impersonation, 3.6b crypto blackmail and extortion, 3.7 nation-state actors, 3.8 structural challenges in forensics, 3.9 physical theft and wrench attacks.


4. Investigation Methodology (7 Phases)

Walk users through these phases sequentially. Never skip scoping (Phase 2) - it prevents wasted effort.


Phase 1: Incident Recognition

Goal: Confirm a crime occurred and identify the entry point.

Red flags to watch for:

  • Sudden large outflows from known protocol, exchange, or multisig treasury wallets
  • Unusual token swaps: governance tokens, staked assets, illiquid LP tokens
  • Approvals to suspicious contracts followed immediately by transfers
  • Bridging activity to obscure chains or known laundering zones
  • Long-dormant wallets suddenly active with large outflows
  • Rapid fund distribution across dozens of wallets in short bursts

Where incidents are first detected:

  1. Threat monitoring firms (follow on X for real-time alerts):

    • PeckShield (@PeckShieldAlert)
    • Cyvers (@CyversAlerts)
    • SlowMist / MistTrack (@MistTrack_io)
    • BlockSec / Phalcon (@Phalcon_xyz)
    • Hexagate (@hexagate_)
    • CertiK (@CertiK)
  2. Independent investigators (essential to follow):

    • ZachXBT (@zachxbt) - stolen fund tracing, influencer fraud
    • Tayvano (@tayvano_) - wallet security, phishing kits, drainers
    • spreekaway (@spreekaway) - real-time exploit wallet alerts
    • WazzCrypto (@WazzCrypto) - memecoin exploit monitoring
  3. Self-monitoring (free):

    • Set Etherscan wallet alerts for target addresses
    • Use Arkham (free tier) for entity tracking and real-time balance changes
    • Use Dune Analytics community dashboards for bridge outflow monitoring

Instruction when user is at this phase:

Ask: "Do you have a transaction hash, wallet address, or a public alert to start from? Let's pull it up on Etherscan/Solscan and confirm what we're looking at."


Phase 2: Scope Definition

Goal: Make the investigation proportionate, feasible, and strategically sound.

Critical questions to ask before proceeding:

  1. What type of crime occurred? (exploit, phishing, laundering, etc.)
  2. What is the estimated financial loss?
  3. Are the assets still on-chain or have they reached a CEX/OTC?
  4. What is the recovery potential vs. investigation cost?
  5. Is this investigation for internal understanding, exchange coordination, or legal action?
  6. Are the affected blockchains well-indexed (Ethereum ✅, obscure L2 ⚠️)?

Cost-benefit reality check:

  • Spending $100K in investigator time to recover $10K is not viable
  • Large incidents (>$1B like Bybit): no single investigator can track all wallets - narrow focus to high-value movements or known off-ramps
  • For law enforcement referral: recovery requires a formal legal pathway; confirm this exists before deep-diving

Investigator mindset:

"Never rely entirely on others to crack the case. Progress comes from persistence and finding your own path. Once you've contributed meaningful findings, others may assist - but it starts with you."


Phase 3: Data Collection & Enrichment

Goal: Gather every known data point. Enrich with context before tracing begins.

What to collect (free tools):

Data PointFree Tool
Victim addressProvided by victim, protocol, or news report
Attacker addressEtherscan/Solscan - check outflows from victim
Transaction hashesBlock explorer - label both victim and attacker wallets and list all txs
Contract addressesEtherscan contract tab; Phalcon for decoded interaction
Token details, amountsBlock explorer token transfer tab
TimestampsBlock explorer - sequence all key events
Event logs (flash loans, internal txs)Etherscan "Internal Txns" tab; Tenderly (free) for full trace
Bridge dataBridge's own explorer (Wormhole explorer, Thorchain explorer)
Known labels/tagsArkham Intelligence (free), community threat feeds

Enrichment questions to ask before tracing:

  • Is the attacker wallet newly created or reused from another exploit?
  • Are transaction patterns similar to known laundering behaviors (e.g., Lazarus)?
  • Is the contract obfuscated or copied from a previous malicious deployment?
  • Are automated drainers, mixers, or specific bridges being used?

Organize your data:

  • Copy all tx hashes, addresses, and amounts into a spreadsheet from day one
  • Label every address clearly: victim, attacker, intermediary_1, fee_funder, etc.
  • Log all timestamps - sequencing events is critical for timing analysis later

Free tool instruction - Etherscan:

"Go to etherscan.io → paste the victim address → click 'Internal Txns' to see contract-level fund movements (not just surface transfers). Then click 'Token Transfers (ERC-20)' to see all token flows. Copy every tx hash involving the attacker."


Phase 4: Transaction Tracking

Goal: Follow the movement of stolen or suspicious assets across wallets, swaps, bridges, and chains.

Key behaviors to expect and watch for:

Attacker BehaviorWhat to Look For
Immediate stablecoin swapUSDT/USDC → ETH/SOL/TRX within minutes of theft
Peel chains40+ wallets each receiving equal amounts (e.g., 10K ETH each)
DormancyWallets sit idle for days–months; set alerts and monitor
Mixer usageTornado Cash, Railgun deposits; track the timing and denominations
Cross-chain bridgingWormhole, THORChain, eXch, ChangeNOW, Synapse inflows/outflows
Micro-CEX withdrawalsSmall fragmented amounts sent to exchange hot wallets
Gas feeder walletOne wallet tops up dozens of others with identical gas amounts

Step-by-step tracking process (free tools):

  1. Label attacker wallet(s) on Etherscan/Solscan using "My Labels" (free account)
  2. Check all outbound transactions - list every receiving address
  3. For each receiving address, repeat: check outbound transactions, note amounts and timing
  4. Identify the first swap - usually via 1inch, Paraswap, or Uniswap. Note the output token.
  5. Follow the new token - if it's ETH, continue. If stablecoin, it may be heading to Tron/CEX.
  6. Check for bridge transactions - look for interactions with known bridge contracts (Wormhole, THORChain router, Stargate)
  7. Set real-time alerts on Etherscan (free wallet alerts) or Arkham for all known attacker wallets

Free tool instruction - Breadcrumbs (breadcrumbs.app):

"Go to breadcrumbs.app → enter the attacker address → use the visual graph to map all outflows. Right-click any node to expand it. Export the graph for your report."

Free tool instruction - MetaSleuth (metasleuth.io):

"Go to metasleuth.io → paste the address → it generates an automatic fund flow map across chains. Use 'Address Book' to tag wallets as you identify them."

Paid tool note: Crystal Intelligence, Chainalysis Reactor, TRM Forensics, and Elliptic Investigator offer advanced tracing with entity tags and compliance reports - worth it for institutional or law enforcement contexts, but not required for most investigations.


Show full SKILL.md (881 more words)Show less
Phase 5: Chain Analysis

Goal: Build a coherent picture of fund flows across all hops, chains, and services.

Multi-chain tracking (free tools by chain):

ChainExplorer
Ethereumetherscan.io
Solanasolscan.io
BNB Chainbscscan.com
Trontronscan.org
Avalanchesnowtrace.io
Polygonpolygonscan.com
Arbitrumarbiscan.io
Bitcoinmempool.space or blockchain.com/explorer
THORChainthorchain.net/txs
Wormholewormholescan.io

Cross-chain matching (when bridges don't provide transparency):

  1. Note the exact timestamp and amount deposited into the bridge on the source chain
  2. On the destination chain, search the bridge's receiving address for outflows within ±5 minutes of the deposit
  3. Match by value (minus bridge fee ~0.1–0.3%)
  4. This is the "time-value correlation" method - 43-second Loopscale example proves it works precisely

For smart contract exploits - decode the transactions:

"Use Phalcon (phalcon.xyz) or Tenderly (tenderly.co, free tier) to simulate and decode the exploit transaction. Paste the tx hash and expand each internal call to understand exactly which functions were abused."


Phase 6: Collaborate & Validate

Goal: Strengthen findings through cross-verification, community intelligence, and external data sources.

Where to share findings and get support:

  • SEAL-ISAC (securityalliance.org/intel) - structured threat-intelligence sharing network for investigators
  • ZachXBT Telegram - active investigator community, real-time intel sharing
  • Twitter/X - post findings publicly (with appropriate caveats); community will often add context
  • Protocol security teams - if an ongoing hack, contact the protocol's security contact immediately; they can freeze assets

⚠️ Attacker counterintelligence - disclosure timing is critical: Sophisticated attackers actively monitor Arkham alerts, Etherscan wallet comments, Twitter/X threads, and Telegram channels for signs that their addresses have been flagged. When they detect investigator attention, they accelerate fund movement, rotate wallets, or bridge immediately to break the trail.

Operational rule: Withhold specific wallet addresses and chain-hop findings from public disclosure until you are ready to act - i.e., you have a freeze request queued with an exchange, or law enforcement is ready to move. Coordinate privately first, publish after. This is why experienced investigators like ZachXBT often delay public posts - early disclosure burns the lead.

Cross-verification checklist:

  • Does the attacker address appear in any published threat feeds? (Check: Chainabuse, ScamSniffer, MistTrack)
  • Is any involved address on OFAC SDN list? (Check: home.treasury.gov/policy-issues/financial-sanctions/specially-designated-nationals-and-blocked-persons-list)
  • Has Tether or Circle frozen any addresses in the cluster? (Check: on-chain blacklist call on the USDT/USDC contract)
  • Are there any published investigations referencing these wallets? (Check: ZachXBT's Telegram/Twitter, PeckShield)
  • Has any exchange announced fund freezes? (Check: Binance, OKX, Kraken announcements)

Tether blacklist check (free, on-chain):

"Go to etherscan.io → search the USDT contract (0xdac17f...eE) → read contract → call isBlacklisted(address) with the attacker's address. Returns true if Tether has frozen it."


Phase 7: Profile Building & Reporting

Goal: Synthesize findings into a clear, evidence-backed narrative identifying the attacker entity.

Profile components:

  • All known attacker wallets and their roles (exploit wallet, fee funder, collector, bridge wallet, CEX deposit)
  • Timeline of events with tx hashes and timestamps
  • Laundering route diagram (use Breadcrumbs or MetaSleuth export)
  • Attribution evidence: OSINT overlaps, behavioral fingerprints, reused infrastructure
  • Known identity signals: exchange KYC accounts (if reported), OSINT personas, leaked data
  • Estimated current location of funds and recovery viability

For detailed report structure, evidence hygiene, and disclosure guidance read:

cat references/reporting-standards.md


5. Attribution Techniques

For complete attribution methods - transaction patterns, gas wallet clustering, peel chains, exploit code reuse, cross-chain attribution, and behavioral fingerprinting - read:

cat references/attribution-techniques.md


6. OSINT Framework

For detailed OSINT sources (social media, domain/infrastructure tools, developer repos, threat feeds, legal documents, file metadata, stablecoin blacklists, leaked databases), best practices, proactive monitoring setup, and limitations, read:

cat references/osint-framework.md


7. Advanced Techniques

For advanced methods including time-based transaction correlation, demixing Tornado Cash/Railgun/CoinJoin, bridge hopping analysis, large-scale Dune SQL queries, graph clustering heuristics, and cross-case pattern recognition (Lazarus, Inferno Drainer, Bridge Hopper), read:

cat references/advanced-techniques.md


8. Laundering Pattern Library

For the complete reference table of laundering techniques, detection methods, and tools (peel chains, mixers, bridge hopping, instant swaps, CEX micro-deposits, OTC off-ramps, unregulated exchanges, and more), read:

cat references/laundering-patterns.md


9. Tool Reference (Free-First)

For the complete tool inventory organized by category - block explorers, visual tracing and graph tools, smart contract decoding, analytics and querying, OSINT, approval revocation and wallet protection, paid tools, community intelligence sources, and terminology reference - read:

cat references/tool-reference.md


10. Reporting and Evidence Standards

For evidence hygiene standards, archiving protocol, exchange and law enforcement cooperation procedures, public disclosure guidelines, and the full report structure template, read:

cat references/reporting-standards.md


Quick Reference: Investigation Entry Points

User starts with...Start at phase...First action
"There's a hack happening right now"Phase 1 → 2Get attacker address from PeckShield/Cyvers alert, go to Phase 3
"I have a victim address"Phase 3Etherscan: check outbound txs, identify attacker address
"I have an attacker address"Phase 3–4Map all outflows, label wallets, start tracking
"Funds went through Tornado Cash"Phase 7.2Demixing: timing analysis + post-exit monitoring
"Funds bridged to another chain"Phase 5 + 7.3Time-value correlation, destination chain explorer
"I need to identify who the attacker is"Phase 5 + 6Attribution techniques + OSINT pivot on attacker wallet
"I need to write a report"Phase 7Synthesize all findings using reporting structure
"Victim got approval-scammed"Phase 3.2Find malicious spender on Etherscan approvals; revoke.cash for victim
"Pig butchering - victim sent funds"Phase 3.3Trace destination wallet, check Chainabuse, identify collector cluster

11. Professional Development

For structured certification paths (TRM Labs, Chainalysis Academy, Elliptic, Crystal Intelligence) and continuous learning guidance including annual crime reports, independent researcher sources, and case study replay methodology, read:

cat references/professional-development.md

© forefy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files (references) in skills/blockchain/blockchain-forensics of forefy/.context.

  • SKILL.md
  • references/advanced-techniques.md
  • references/attribution-techniques.md
  • references/laundering-patterns.md
  • references/osint-framework.md
  • references/professional-development.md
  • references/reporting-standards.md
  • references/threat-landscape.md
  • references/tool-reference.md

Open the folder on GitHubat commit c8ff161

Compare with similar skills

Blockchain Forensics next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Blockchain Forensics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Blockchain Forensics this skillforefy/.context152—~5.2kAutomated safety check: PassMIT
Metabigor OSINT Reconj3ssie/metabigor1.8k—~2.4kAutomated safety check: PassMIT
Ctf Osintljagiello/ctf-skills3.4k2 repos~2.3kAutomated safety check: NotesMIT
ShadowBroker Intelligence ClientBigBodyCobain/Shadowbroker11k—~8.9kAutomated safety check: WarnAGPL-3.0
Awesome Osint Operatorshoyann/RZK-The-Hunter140—~4.8kAutomated safety check: PassCC-BY-SA-4.0
Run Claude Osintelementalsouls/Claude-OSINT2.8k—~1.2kAutomated safety check: PassMIT

Similar skills

  • Metabigor OSINT Recon

    j3ssie/metabigor

    Operates the metabigor CLI to map a target's network ranges, subdomains, ports, related domains, CDNs and archived URLs from free sources without API keys.

    1.8k GitHub stars~2.4k tokensUpdated 2 mo ago
    SecurityAuto-check passed
  • Ctf Osint

    ljagiello/ctf-skills

    Provides open source intelligence techniques for CTF challenges.

    3.4k GitHub starsUsed in 2 repos~2.3k tokens
    SecurityAuto-check: notes
  • ShadowBroker Intelligence Client

    BigBodyCobain/Shadowbroker

    Lets an agent query a ShadowBroker OSINT platform for tracked flights, ships, satellites and news, and place its findings on the map as intel pins.

    11k GitHub stars~8.9k tokensUpdated today
    SecurityAuto-check: warnings
  • Awesome Osint Operator

    shoyann/RZK-The-Hunter

    Ethical, evidence-first OSINT planning, tool selection, verification, monitoring, reporting, and guarded official wanted/fugitive-person location intelligence using a structured catalog adapted from…

    140 GitHub stars~4.8k tokensUpdated 16 days ago
    SecurityAuto-check passed
  • Run Claude Osint

    elementalsouls/Claude-OSINT

    Build, validate, and run the claude-osint skills repo — check SKILL.md frontmatter, run the secretscan.py and h1reference.py helpers, run sync-skill-content.sh, run the smoke test.

    2.8k GitHub stars~1.2k tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Osint

    smixs/osint-skill

    Conduct deep OSINT research on individuals. An agent skill from smixs/osint-skill.

    140 GitHub stars~5.5k tokensUpdated 7 mo ago
    SecurityAuto-check passed

More from forefy/.context

All 20 skills in this repo
  • Builds and formats security audit reports in Google Docs through the Docs API, with fixes for index drift, code styling and cross-reference links.

    152 GitHub stars~951 tokensUpdated 2 days ago
    Auto-check passed
  • Audits the Safe multisig wallets of DeFi protocols for governance misconfigurations, scoring each against a finding library and producing a severity-ranked report.

    152 GitHub stars~1.4k tokensUpdated 2 days ago
    Auto-check passed
  • Turns a company's domains into likely storage bucket names and checks six cloud providers for publicly readable buckets, for authorized security assessments only.

    152 GitHub stars~1.5k tokensUpdated 2 days ago
    Auto-check passed
  • Audit Scope

    forefy/.context

    Draft a security-audit scope from GitHub repos or API access, with a protocol narrative and a sizing table.

    152 GitHub stars~2.3k tokensUpdated 2 days ago
    Auto-check passed
  • External Enumeration

    forefy/.context

    Passively map a company's domains, subdomains, DNS ownership, tech stack, and CDNs.

    152 GitHub stars~3.1k tokensUpdated 2 days ago
    Auto-check passed
  • Smart Contract Audit

    forefy/.context

    Comprehensive smart contract security audit framework with multi-expert analysis.

    152 GitHub starsUsed in 1 repo~5.1k tokens
    Auto-check passed

Categories

Questions about Blockchain Forensics

What does Blockchain Forensics do?

Expert blockchain forensics assistant for investigators and auditors, including threat recognition, incident scoping, data collection, transaction tracking, chain analysis, attribution, OSINT…. context. Expert blockchain forensics assistant for investigators and auditors, including threat recognition, incident scoping, data collection, transaction tracking, chain analysis, attribution, OSINT, advanced demixing, cross-chain tracing, graph clustering, and reporting.

When should I use Blockchain Forensics?

Blockchain Forensics fits situations like: tasks that involve OSINT.

How do I install Blockchain Forensics in Claude Code?

Run `npx skills add forefy/.context --skill blockchain-forensics -a claude-code`. Or copy the skill folder (skills/blockchain/blockchain-forensics in forefy/.context) into .claude/skills/blockchain-forensics in your project. Claude Code loads it when a task matches its description.

How do I install Blockchain Forensics in Codex?

Run `npx skills add forefy/.context --skill blockchain-forensics -a codex`. Or copy the skill folder (skills/blockchain/blockchain-forensics in forefy/.context) into .agents/skills/blockchain-forensics in your project. Codex loads it when a task matches its description.

Can I use Blockchain Forensics in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add forefy/.context --skill blockchain-forensics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/blockchain-forensics, .gemini/skills/blockchain-forensics, .github/skills/blockchain-forensics and .opencode/skills/blockchain-forensics in your project.

What does Blockchain Forensics need to run?

SKILL.md names no scripts, command-line tools or credentials: Blockchain Forensics is instructions for the agent only.

Does Blockchain Forensics access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Blockchain Forensics safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Blockchain Forensics use?

Blockchain Forensics is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Blockchain Forensics use?

About 5.2k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 15k tokens, read only when the agent opens those files.

What are the alternatives to Blockchain Forensics?

Skills that share tags, products or a category with Blockchain Forensics: Metabigor OSINT Recon (j3ssie/metabigor, 1.8k stars), Ctf Osint (ljagiello/ctf-skills, 3.4k stars), ShadowBroker Intelligence Client (BigBodyCobain/Shadowbroker, 11k stars) and Awesome Osint Operator (shoyann/RZK-The-Hunter, 140 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Blockchain Forensics?

forefy (a GitHub user) maintains it in forefy/.context, which has 152 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 4, 2026.

Source: forefy/.context on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.