Repository navigation
Command Reference
OSINT Forge has four command families: framework management, single-adapter execution, batch execution, and durable case management.
osint --help
osint --versionosint forge list [--installed | --available] [--json]
osint forge search QUERY
osint forge info TOOL
osint forge categories
osint forge install TOOL... [--dry-run]
osint forge update TOOL... [--dry-run]
osint forge remove TOOL... [--dry-run]
osint forge doctor [TOOL...]
osint forge validate [--json]
osint forge versionUnknown tools and invalid plugin contracts are rejected. Lifecycle dry-runs preview commands without executing them.
osint run PLUGIN {address,domain,email,file,image,ip,name,phone,username} TARGET \
[--output PATH] [--dry-run]Adapter availability depends on the plugin's declared target types. Targets are validated and passed as argument-array elements, not interpolated shell strings.
osint batch [INPUT] [--name NAME] [--output-root PATH] \
[--plugins TOOL...] [--jobs 1-8] [--dry-run]The default input is ~/.config/osint-forge/targets.txt. See Batch Workflows.
osint case create CASE --purpose TEXT --authorization TEXT
osint case add CASE {address,domain,email,file,image,ip,name,phone,username} TARGET
osint case run CASE [--plugins TOOL...] [--jobs 1-8] [--rerun] [--dry-run]
osint case status CASE [--json]
osint case entities CASE [--json]
osint case report CASE [--output PATH] [--force]Name, phone, address, and osint case entities are stable v0.4 features. See
Case Management.
Commands return nonzero status for validation failures, unknown tools, failed lifecycle operations, malformed case data, and failed jobs. Dry-run output is a preview and does not mark case jobs successful.
Later committed releases add entity-aware extraction and planning; they do not silently change today's adapters. New execution and recursion behavior will be versioned, bounded, auditable, and documented before release. See Roadmap.