Custom Plugins

Dedicated source-of-truth repository for Codex plugins maintained by Hyatus Living.

Included plugins

• thread-share: exports a Codex thread into a clean static share page backed by a sanitized Euphony JSONL session.
• thread-finder: searches and extracts local Codex thread history with a plugin-owned SQLite index.
• reservations-melted-grid: read-only reservation availability and melted-grid diagnostics.
• aws-billing-insights: generates AWS Cost Explorer billing reports with gross spend, credits, net cost, and charts.
• message-finder: indexes and searches local iMessage and WhatsApp history with a plugin-owned SQLite index.
• res-dive: runs read-only Hyatus reservation investigations with SQL, Mongo, communications, and risk evidence helpers.
• hyatus-security-sweep: runs local IOC, supply-chain, dependency, and secret scans with persistent markdown logging.
• token-usage-report: generates local Codex/Claude/OpenCode/Pi/ZCode/Cursor token-usage and estimated-cost reports via ccusage (preferred) with ccusage fallback plus local Cursor readers.

Repository layout

• .agents/plugins/marketplace.json: repo-local marketplace manifest
• plugins/<plugin-name>/: plugin source

Automation templates

Recurring Codex automations are not plugin source. Maintain reusable automation examples in the custom-skills automation directory.

The current examples are bounded current-thread heartbeats. They are source references for Codex's automation_update tool, not files to copy into ~/.codex/automations/. Heartbeats must use destination = "thread", have a finite COUNT or UNTIL, and explicitly retire themselves. The Codex app resolves and persists the actual target thread; do not store or copy raw target thread IDs.

Templates must not include machine-specific paths, real run history, Slack or mailbox identifiers, connected-account details, tokens, or secrets. Keep persisted automation state, local memory, and durable history outside Git.

Common commands

Publish the current Codex thread:

python3 plugins/thread-share/scripts/share_codex_thread.py --deploy vercel

Search local Codex thread history:

python3 plugins/thread-finder/scripts/thread_finder_core.py search "topic"

Inspect local message source availability:

python3 plugins/message-finder/scripts/message_finder_core.py overview

Run a reservation dive prerequisite check:

python3 plugins/res-dive/scripts/res_dive_doctor.py

Run the Hyatus security sweep:

python3 plugins/hyatus-security-sweep/scripts/hyatus_security_sweep.py

Generate a local token usage report:

node plugins/token-usage-report/scripts/generate_token_usage_report.mjs --output /tmp/token-usage-report

Publish notes

Some plugins expect local data or CLI auth:

• Thread plugins expect local Codex history under ~/.codex.
• thread-share expects Vercel CLI auth when deploying share pages.
• aws-billing-insights expects AWS CLI credentials with Cost Explorer access.
• message-finder reads iMessage and WhatsApp source databases read-only and writes only to ~/.codex/message-finder/index.sqlite.
• res-dive reads reservation-history MySQL and Pricing GPT Mongo read-only.
• hyatus-security-sweep writes only its markdown run log by default, under ~/.codex/security-sweep/run-log.md.
• token-usage-report expects tokscale (preferred), ccusage (fallback), node, python3, and sqlite3 locally.