EXTENSIONS
Built by operatives — models, drivers, vaults, and reports, the parts that plug into Swamp.
Filter by what you need and pull what fits.
Claimbook
Breach-claim ledger and verification state machine on DuckDB. Files claims with asserted levels (L0 rumor → L5 published), attaches sha256-attributed evidence, reconciles asserted dump profiles against observed inventories, records public statements, tracks onion watch-state diffs, and emits verification reports. Persistence layer of the breach-verification bench.
Onion
Tor onion-service observability model: bootstrap a persistent Tor daemon, probe onion endpoints, capture sha256-attributed evidence snapshots, crawl dump-inventory listings (filebrowser HTML or enumeration JSON) with PII-bearing filename masking. Network layer of the breach-verification bench.
Zocomputer
Zo Computer MCP + Ask: access every Zo tool (89+ tools) via MCP JSON-RPC and Zo's conversational AI via /zo/ask — all through a single swamp model. Includes convenience wrappers for web_search, read_file, generate_image, and full generic mcp_call_tool for any tool in the Zo surface.
Turso
Turso (libSQL) datastore for swamp: query model for ad-hoc SQL against Turso edge databases, and a datastore backend that stores swamp runtime data in a remote Turso database with row-based distributed locking.
Sops Age
SOPS + age vault for swamp: encrypt secrets at rest with AES-256-GCM via Mozilla SOPS and age. Zero network dependency — fully local, file-based. Works with existing SOPS workflows and zo.space secrets dashboards.
Duckdb
DuckDB integration for swamp: query model for ad-hoc SQL, and a datastore backend that stores swamp runtime data in a DuckDB database file with row-based distributed locking. Embedded, local-only — no network dependency.