osint-methodology skillA
osint-methodology is agent-read markdown (skill) from miosa-osa/osa: Structured OSINT methodology framework: target definition, source selection, collection workflows, data correlation, timeline reconstruction, and reporting. Covers sock-puppet OpSec, cryptocurrency and L2 tracing, image/video geolocation, chronolocation (shadow/astronomical/satellite), threat-actor investigation with attribution discipline, RU/CN-specific pivots, people and social-media investigation, infrastructure OSINT, Telegram/WeChat, case management, and synthetic-media verification. Use t.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# OSINT Methodology When this skill is active: 1. Apply the methodology below as the operational checklist 2. Follow steps in order unless the operator specifies otherwise 3. For each technique, weigh applicability to the current target/context 4. Track which checklist items are complete 5. Suggest next steps from what each tool returns CLI tools marked `[LOCAL]` (verified), `[INSTALL]` (one-command install), `[UPSTREAM-REF]` (reference only — API keys/commercial/interactive). ## OpSec — sock puppets first - Fake account that cannot be linked to you; build posting history before investigating - Separate browser profiles/containers per case and persona (Firefox Multi-Account Containers); never log into personal accounts from an investigation profile - Disposable VoIP/SMS numbers (Burner, Silent Link) for platform verification - Audit every browser extension before install — supply-chain attacks on investigator extensions are documented since 2024 - Hardware-backed passkeys for critical accounts; recovery codes offline - Minimal chain-of-custody: timestamp every action, hash key artifacts, record tool versions per case …
Read the whole file at its exact version.
How to install
mdr add miosa-osa/osa/osint-methodology@git:20260913.e13b6b8mdr add miosa-osa/osa/osint-methodology@sha256:e4aa682531277ea7Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_3erz2dwdkjlr6vw5)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (16347 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
miosa-osa/osa · 74 stars · license NOASSERTION · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3erz2dwdkjlr6vw5 GET https://markdownregistry.com/api/v1/resolve?ref=miosa-osa/osa/osint-methodology GET https://markdownregistry.com/api/v1/blob/e4aa682531277ea7854342994e546e4b2939ca0e213849ef48c5bfdb8a944e5f
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.