Claude Code, two commands.
Every bundle you download is a self-contained Claude Code plugin marketplace — the entitlement check happens at download, so you install straight from the local folder. No tokens to paste, no hosted endpoint to trust.
How it's packaged.
Unzip a bundle and you'll see a Claude Code plugin laid out the way the runtime expects:
osint-foundations-2026/ ├── .claude-plugin/ │ └── marketplace.json ← a local marketplace named "osint-tradecraft" ├── osint-foundations/ ← the plugin │ ├── .claude-plugin/ │ │ └── plugin.json │ └── skills/ │ ├── seed-discovery-from-email/SKILL.md │ ├── ssl-certificate-pivoting/SKILL.md │ └── … └── README.md
The marketplace points at the plugin by relative path — which resolves because you add it as a local folder, not a URL. Claude Code can't authenticate a hosted marketplace against a license key, so we gate at the download instead. Cleaner, and it works offline.
Install.
Download & unzip
osint-foundations-2026/.Add the local marketplace
From the directory where you unzipped it:
claude plugin marketplace add ./osint-foundations-2026
Install the plugin & reload
claude plugin install osint-foundations@osint-tradecraft # then, inside Claude Code: /reload-plugins
Swap osint-foundations for whichever bundle you're installing — the plugin name matches the bundle slug.
Confirm & use
Claude auto-invokes the right skill when you describe an investigation task. List what's loaded with /help:
/help > osint-foundations (osint-tradecraft) > seed-discovery-from-email > ssl-certificate-pivoting > wayback-machine-deep-dive > …
Staying current.
With an active Update Subscription, every revision and new skill we add to bundles you own ships as a new edition. To pull it: re-download the bundle from your dashboard, unzip over the old folder, and re-run the two install commands — a one-command re-sync to the latest edition.
One-time bundle owners keep the edition they bought, forever. Re-download is available while your purchase is on file.
Not on Claude Code?
The SKILL.md files are plain Markdown — they work anywhere. Drop them into an OpenAI Custom GPT's knowledge, a local ~/.skills directory, or any agent that reads skill files.