# Codex Plugin Revenue Pack

Updated: 2026-05-04T19:52:57.729Z

This is a sales operator artifact. It is not proof of bundle downloads, installs, paid revenue, or marketplace publication by itself.

## Objective
Turn Codex plugin discovery into tracked guide opens, bundle downloads, Pro checkout starts, and qualified workflow-hardening conversations.

## Canonical Identity
- Display name: ThumbGate
- Slug: thumbgate
- Repository: https://github.com/IgorGanapolsky/ThumbGate
- Homepage: https://thumbgate-production.up.railway.app
- GitHub description: Agent governance for ThumbGate: 👍/👎 become Pre-Action Checks that block repeat mistakes before code, money, or customer systems change.
- Short description: Auto-updating MCP plugin and hook launcher for Codex with Pre-Action Checks, thumbs-up/down feedback memory, and a local-first Reliability Gateway.

ThumbGate gives Codex a proof-backed install path, pre-action gate enforcement, and local-first feedback memory. Use the install page when the buyer needs screenshots and trust context before download, then route serious install intent through the setup guide before any upgrade ask. Use the direct bundle only after the buyer already wants the portable asset or repo-local marketplace surface.

## Evidence-Backed Buyer Signals
### Warm discovery leads already exist
- Count: 4
- Summary: 4 current targets already named concrete workflow pain before any Codex-specific pitch.
- Examples: @Deep_Ad1959, @game-of-kton, @leogodin217

### Workflow control surfaces remain the strongest buyer signal
- Count: 11
- Summary: 11 current targets expose review, approval, governance, or workflow control surfaces where a Codex install story can convert into a workflow-hardening offer.
- Examples: montenegronyc/backporcher, dolutech/engine_context, Adqui9608/ai-code-review-agent

### Production rollout proof matters
- Count: 7
- Summary: 7 targets touch production-sensitive workflows where proof and rollback safety should appear before the buyer expands usage.
- Examples: montenegronyc/backporcher, dolutech/engine_context, Adqui9608/ai-code-review-agent

## Submission Surfaces
### Codex plugin install page
- Role: Human install and trust-building surface
- Operator status: Refresh when CTA order, screenshots, proof links, or pricing guardrails change.
- Conversion goal: install_page_to_setup_guide
- Buyer: Codex users who want a documented install path before trusting a bundle or CLI setup.
- Submission path: https://thumbgate-production.up.railway.app/codex-plugin
- Repository: https://github.com/IgorGanapolsky/ThumbGate
- Homepage: https://thumbgate-production.up.railway.app/codex-plugin?utm_source=codex&utm_medium=install_page&utm_campaign=codex_plugin_install_page&utm_content=page&campaign_variant=install_page&offer_code=CODEX-INSTALL_PAGE&cta_id=codex_install_page&cta_placement=codex_surface&surface=codex_install_page
- Proof: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md
- Support: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/CODEX_PLUGIN_OPERATIONS.md
- Tags: thumbgate, pre-action-checks, agent-reliability, guardrails, developer-tools, codex

Short description: Auto-updating MCP plugin and hook launcher for Codex with Pre-Action Checks, thumbs-up/down feedback memory, and a local-first Reliability Gateway.

ThumbGate gives Codex a proof-backed install path, pre-action gate enforcement, and local-first feedback memory. Use the install page when the buyer needs screenshots and trust context before download, then route serious install intent through the setup guide before any upgrade ask. Use the direct bundle only after the buyer already wants the portable asset or repo-local marketplace surface.

Proof links: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md | https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

### Proof-backed setup guide
- Role: Self-serve activation surface after install intent
- Operator status: Use when the buyer wants steps, proof, and Commercial Truth before checkout.
- Conversion goal: setup_guide_to_paid_intent
- Buyer: Codex users who need setup clarity and proof before they decide between free install, Pro, or workflow hardening.
- Submission path: https://thumbgate-production.up.railway.app/guide
- Repository: https://github.com/IgorGanapolsky/ThumbGate
- Homepage: https://thumbgate-production.up.railway.app/guide?utm_source=codex&utm_medium=setup_guide&utm_campaign=codex_setup_guide&utm_content=guide&campaign_variant=setup_guide&offer_code=CODEX-SETUP_GUIDE&cta_id=codex_setup_guide&cta_placement=codex_surface&surface=codex_setup_guide
- Proof: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md
- Support: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/CODEX_PLUGIN_OPERATIONS.md
- Tags: codex, setup-guide, proof, workflow-hardening

Short description: Proof-backed setup path for Codex buyers who want the install flow, Commercial Truth, and verification evidence in one place.

Send the setup guide after the buyer already wants the tool path. Keep the guide as the self-serve bridge between Codex install intent and either Pro checkout or the Workflow Hardening Sprint.

Proof links: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md | https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

### GitHub release bundle
- Role: Portable plugin distribution surface
- Operator status: Use only after the buyer asked for the direct asset or bundle path.
- Conversion goal: bundle_download_to_follow_on
- Buyer: Codex users who want the standalone zip with manifest, MCP config, marketplace entry, and install docs.
- Submission path: https://github.com/IgorGanapolsky/ThumbGate/releases/latest/download/thumbgate-codex-plugin.zip
- Repository: https://github.com/IgorGanapolsky/ThumbGate
- Homepage: https://github.com/IgorGanapolsky/ThumbGate/releases/latest/download/thumbgate-codex-plugin.zip?utm_source=codex&utm_medium=bundle&utm_campaign=codex_release_bundle&utm_content=download&campaign_variant=release_bundle&offer_code=CODEX-RELEASE_BUNDLE&cta_id=codex_release_bundle&cta_placement=codex_surface&surface=codex_release_bundle
- Proof: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md
- Support: https://github.com/IgorGanapolsky/ThumbGate/blob/main/plugins/codex-profile/INSTALL.md
- Tags: codex, bundle, mcp, pre-action-checks

Short description: Portable Codex plugin bundle with the manifest, MCP config, marketplace entry, and install docs in one asset.

Do not lead with the raw zip. Use the bundle after the buyer already wants the portable asset, then route serious usage to the guide, proof links, and paid-intent follow-on offers.

Proof links: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md | https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

## Follow-On Offers
- ThumbGate Pro: $19/mo or $149/yr
  Buyer: Solo Codex operators who want the self-serve dashboard and proof-ready exports after install.
  CTA: https://thumbgate-production.up.railway.app/checkout/pro?utm_source=codex&utm_medium=setup_guide&utm_campaign=codex_pro_follow_on&utm_content=pro&campaign_variant=pro_follow_on&offer_code=CODEX-PRO_FOLLOW_ON&cta_id=codex_pro_follow_on&cta_placement=codex_follow_on&plan_id=pro&surface=codex_follow_on
- Workflow Hardening Sprint: Workflow Hardening Sprint, then Team at $49/seat/mo with 3-seat minimum after qualification
  Buyer: Teams who already named one repeated Codex-adjacent workflow failure and need rollout proof.
  CTA: https://thumbgate-production.up.railway.app/?utm_source=codex&utm_medium=setup_guide&utm_campaign=codex_sprint_follow_on&utm_content=workflow_sprint&campaign_variant=sprint_follow_on&offer_code=CODEX-SPRINT_FOLLOW_ON&cta_id=codex_sprint_follow_on&cta_placement=codex_follow_on&surface=codex_follow_on#workflow-sprint-intake

## Operator Follow-Up Sequences
### Buyer wants a documented Codex path before trusting a zip or CLI setup.
- Goal: Move cold install curiosity into a tracked guide or setup click.
- Evidence: The install page is the primary human trust surface and keeps proof plus support links close to the download path.
- CTA: https://thumbgate-production.up.railway.app/codex-plugin?utm_source=codex&utm_medium=install_page&utm_campaign=codex_plugin_install_page&utm_content=page&campaign_variant=install_page&offer_code=CODEX-INSTALL_PAGE&cta_id=codex_install_page&cta_placement=codex_surface&surface=codex_install_page

Draft:
> If you want to see the Codex install path before downloading anything, start with the install page: https://thumbgate-production.up.railway.app/codex-plugin?utm_source=codex&utm_medium=install_page&utm_campaign=codex_plugin_install_page&utm_content=page&campaign_variant=install_page&offer_code=CODEX-INSTALL_PAGE&cta_id=codex_install_page&cta_placement=codex_surface&surface=codex_install_page . It shows the bundle path, install docs, and proof links in one place so you can decide whether the free setup is enough first.

### Buyer already wants the tool path and asks for steps, proof, or setup clarity.
- Goal: Move install intent into either a qualified sprint conversation or a tracked Pro checkout start.
- Evidence: The setup guide is the designated self-serve bridge between Codex install intent and paid intent.
- CTA: https://thumbgate-production.up.railway.app/guide?utm_source=codex&utm_medium=setup_guide&utm_campaign=codex_setup_guide&utm_content=guide&campaign_variant=setup_guide&offer_code=CODEX-SETUP_GUIDE&cta_id=codex_setup_guide&cta_placement=codex_surface&surface=codex_setup_guide

Draft:
> Here is the proof-backed Codex setup guide: https://thumbgate-production.up.railway.app/guide?utm_source=codex&utm_medium=setup_guide&utm_campaign=codex_setup_guide&utm_content=guide&campaign_variant=setup_guide&offer_code=CODEX-SETUP_GUIDE&cta_id=codex_setup_guide&cta_placement=codex_surface&surface=codex_setup_guide . Use it when the buyer wants the exact install flow plus Commercial Truth and verification evidence before choosing between free install, Pro, or a workflow-hardening conversation.

### Solo operator already proved one blocked repeat and wants the self-serve lane.
- Goal: Move proven solo usage into tracked Pro checkout intent.
- Evidence: The pack keeps Pro as the post-proof follow-on after one blocked repeat is real.
- CTA: https://thumbgate-production.up.railway.app/checkout/pro?utm_source=codex&utm_medium=setup_guide&utm_campaign=codex_pro_follow_on&utm_content=pro&campaign_variant=pro_follow_on&offer_code=CODEX-PRO_FOLLOW_ON&cta_id=codex_pro_follow_on&cta_placement=codex_follow_on&plan_id=pro&surface=codex_follow_on

Draft:
> If you already proved one blocked repeat in Codex and just want the self-serve lane, Pro is the clean next step: https://thumbgate-production.up.railway.app/checkout/pro?utm_source=codex&utm_medium=setup_guide&utm_campaign=codex_pro_follow_on&utm_content=pro&campaign_variant=pro_follow_on&offer_code=CODEX-PRO_FOLLOW_ON&cta_id=codex_pro_follow_on&cta_placement=codex_follow_on&plan_id=pro&surface=codex_follow_on . That keeps the dashboard and proof-ready exports attached without forcing a services motion.

### Team already named one repeated approval-boundary, handoff, or rollout failure.
- Goal: Move team pain into a qualified workflow-hardening conversation.
- Evidence: The Workflow Hardening Sprint remains the primary paid motion when one owner and one repeated failure are explicit.
- CTA: https://thumbgate-production.up.railway.app/?utm_source=codex&utm_medium=setup_guide&utm_campaign=codex_sprint_follow_on&utm_content=workflow_sprint&campaign_variant=sprint_follow_on&offer_code=CODEX-SPRINT_FOLLOW_ON&cta_id=codex_sprint_follow_on&cta_placement=codex_follow_on&surface=codex_follow_on#workflow-sprint-intake

Draft:
> If one approval, handoff, or rollout failure keeps repeating around Codex or a neighboring review lane, route it to the Workflow Hardening Sprint instead of a generic plugin pitch: https://thumbgate-production.up.railway.app/?utm_source=codex&utm_medium=setup_guide&utm_campaign=codex_sprint_follow_on&utm_content=workflow_sprint&campaign_variant=sprint_follow_on&offer_code=CODEX-SPRINT_FOLLOW_ON&cta_id=codex_sprint_follow_on&cta_placement=codex_follow_on&surface=codex_follow_on#workflow-sprint-intake . That keeps the conversation anchored on one workflow, one owner, and one proof review.

Use Commercial Truth and Verification Evidence only after the buyer confirms the workflow pain or asks for proof.

## Ready-Now Target Queue
### Send Now: Codex-Adjacent Workflow Hardening
- Motion: Workflow Hardening Sprint
- Summary: Use these when the buyer already named one repeated failure, mature review boundary, or rollout risk.

#### 1. @Deep_Ad1959
- Temperature: warm
- Source: reddit / reddit_dm
- Evidence score: 10
- Why now: Warm Reddit engager already named a repeated workflow risk, so the fastest path is a founder-led diagnostic.
- Evidence: warm inbound engagement; workflow pain named: rollback risk; already in DMs
- Contact: https://www.reddit.com/user/Deep_Ad1959/
- CTA: https://thumbgate-production.up.railway.app/#workflow-sprint-intake
- Proof rule: Use proof pack only after the buyer confirms pain.
- Pipeline lead id: reddit_deep_ad1959_r_cursor
- Log after send: `npm run sales:pipeline -- advance --lead 'reddit_deep_ad1959_r_cursor' --channel 'reddit_dm' --stage 'contacted' --note 'Sent Workflow Hardening Sprint first touch focused on rollback risk.'`

First-touch draft:
> Your question about rollback rates when context changes is exactly the right one. I am looking for one AI-agent workflow to harden end-to-end this week: repeated failure, prevention rule, and proof run. If you have one workflow where context drift or rollback risk keeps showing up, I can harden that workflow for you. Worth a 15-minute diagnostic?

#### 2. @game-of-kton
- Temperature: warm
- Source: reddit / reddit_dm
- Evidence score: 9
- Why now: Warm Reddit engager already works on advanced agent memory, so discovery should center on one repeated failure pattern.
- Evidence: warm inbound engagement; built serious memory systems; workflow pain named: stale context and conflicting facts
- Contact: https://www.reddit.com/user/game-of-kton/
- CTA: https://thumbgate-production.up.railway.app/#workflow-sprint-intake
- Proof rule: Use proof pack only after the buyer confirms pain.
- Pipeline lead id: reddit_game_of_kton_r_cursor
- Log after send: `npm run sales:pipeline -- advance --lead 'reddit_game_of_kton_r_cursor' --channel 'reddit_dm' --stage 'contacted' --note 'Sent Workflow Hardening Sprint first touch focused on stale context and conflicting facts.'`

First-touch draft:
> Your ACT-R engram work is fascinating, especially the conflict resolution for opposing facts and the decay model. I am looking for one serious AI-agent workflow to harden end-to-end this week. If your memory system has one recurring failure mode such as stale context, opposing facts, bad handoffs, or unsafe tool calls, I can turn that into a prevention rule and proof run. Open to a 15-minute diagnostic?

#### 3. @leogodin217
- Temperature: warm
- Source: reddit / reddit_dm
- Evidence score: 9
- Why now: Warm Reddit engager already described a mature workflow, so the next step is a targeted diagnostic on one failure mode.
- Evidence: warm inbound engagement; mature multi-step workflow described; workflow pain named: review boundaries and context risk
- Contact: https://www.reddit.com/user/leogodin217/
- CTA: https://thumbgate-production.up.railway.app/#workflow-sprint-intake
- Proof rule: Use proof pack only after the buyer confirms pain.
- Pipeline lead id: reddit_leogodin217_r_claudecode
- Log after send: `npm run sales:pipeline -- advance --lead 'reddit_leogodin217_r_claudecode' --channel 'reddit_dm' --stage 'contacted' --note 'Sent Workflow Hardening Sprint first touch focused on review boundaries and context risk.'`

First-touch draft:
> Your arch-create to sprint workflow is one of the most mature agent processes I have seen anyone describe. I am looking for one AI-agent workflow to harden end-to-end this week. Your workflow already has phases, review boundaries, and context risk, so it is a strong fit: pick one repeating failure and I will help turn it into an enforceable Pre-Action Check plus proof run. Worth 15 minutes?

#### 4. @Enthu-Cutlet-1337
- Temperature: warm
- Source: reddit / reddit_dm
- Evidence score: 8
- Why now: Warm Reddit engager already understands the adaptive-gate thesis, so offer one concrete workflow hardening diagnostic.
- Evidence: warm inbound engagement; responded to adaptive-gate positioning; workflow pain named: brittle guardrails
- Contact: https://www.reddit.com/user/Enthu-Cutlet-1337/
- CTA: https://thumbgate-production.up.railway.app/#workflow-sprint-intake
- Proof rule: Use proof pack only after the buyer confirms pain.
- Pipeline lead id: reddit_enthu_cutlet_1337_r_claudecode
- Log after send: `npm run sales:pipeline -- advance --lead 'reddit_enthu_cutlet_1337_r_claudecode' --channel 'reddit_dm' --stage 'contacted' --note 'Sent Workflow Hardening Sprint first touch focused on brittle guardrails.'`

First-touch draft:
> Appreciate the kind words on the Thompson Sampling approach. You nailed the core insight: most guardrails are brittle prompt hacks that break when context shifts. I am looking for one AI-agent workflow to harden end-to-end this week: repeated failure, prevention rule, and proof run. If you have a workflow where brittle guardrails keep failing, I can harden that workflow with you. Open to a 15-minute diagnostic?

### Send Next: Codex Self-Serve Install + Pro
- Motion: Pro at $19/mo or $149/yr
- Summary: Use these when the buyer already exposes a plugin, local-hook, or repo-backed tooling surface and should start with the guide path.

#### 1. agynio/gh-pr-review
- Temperature: cold
- Source: github / github
- Evidence score: 15
- Why now: Target looks like a local hook, plugin, or config surface, so start with the setup guide and Pro follow-on before pitching a sprint.
- Evidence: workflow control surface; business-system integration; self-serve agent tooling; 144 GitHub stars; updated in the last 7 days
- Contact: https://agyn.io/
- CTA: https://thumbgate-production.up.railway.app/guide
- Proof rule: Use proof pack only after the buyer confirms pain.
- Pipeline lead id: github_agynio_gh_pr_review
- Log after send: `npm run sales:pipeline -- advance --lead 'github_agynio_gh_pr_review' --channel 'manual' --stage 'contacted' --note 'Sent Pro at $19/mo or $149/yr self-serve first touch focused on one business-system workflow that needs approval boundaries, rollback safety, and proof.'`

First-touch draft:
> Hey @agynio, saw you're building around `gh-pr-review`. If you want the clean self-serve tool path first, start with the proof-backed setup guide: https://thumbgate-production.up.railway.app/guide. If one repeated agent mistake is still slowing the workflow down after that, Pro is the clean next step.

#### 2. greenpolo/cc-multi-cli-plugin
- Temperature: cold
- Source: github / github
- Evidence score: 14
- Why now: Target looks like a local hook, plugin, or config surface, so start with the setup guide and Pro follow-on before pitching a sprint.
- Evidence: workflow control surface; business-system integration; self-serve agent tooling; 72 GitHub stars; updated in the last 7 days
- Contact: https://github.com/greenpolo
- CTA: https://thumbgate-production.up.railway.app/guide
- Proof rule: Use proof pack only after the buyer confirms pain.
- Pipeline lead id: github_greenpolo_cc_multi_cli_plugin
- Log after send: `npm run sales:pipeline -- advance --lead 'github_greenpolo_cc_multi_cli_plugin' --channel 'manual' --stage 'contacted' --note 'Sent Pro at $19/mo or $149/yr self-serve first touch focused on one business-system workflow that needs approval boundaries, rollback safety, and proof.'`

First-touch draft:
> Hey @greenpolo, saw you're building around `cc-multi-cli-plugin`. If you want the clean self-serve tool path first, start with the proof-backed setup guide: https://thumbgate-production.up.railway.app/guide. If one repeated agent mistake is still slowing the workflow down after that, Pro is the clean next step.

#### 3. levnikolaevich/claude-code-skills
- Temperature: cold
- Source: github / github
- Evidence score: 14
- Why now: Target looks like a local hook, plugin, or config surface, so start with the setup guide and Pro follow-on before pitching a sprint.
- Evidence: workflow control surface; agent infrastructure; self-serve agent tooling; 447 GitHub stars; updated in the last 7 days
- Contact: https://levnikolaevich.com/
- CTA: https://thumbgate-production.up.railway.app/guide
- Proof rule: Use proof pack only after the buyer confirms pain.
- Pipeline lead id: github_levnikolaevich_claude_code_skills
- Log after send: `npm run sales:pipeline -- advance --lead 'github_levnikolaevich_claude_code_skills' --channel 'manual' --stage 'contacted' --note 'Sent Pro at $19/mo or $149/yr self-serve first touch focused on the proof-backed setup guide and local-first enforcement before any team-motion pitch.'`

First-touch draft:
> Hey @levnikolaevich, saw you're building around `claude-code-skills`. If you want the clean self-serve tool path first, start with the proof-backed setup guide: https://thumbgate-production.up.railway.app/guide. If one repeated agent mistake is still slowing the workflow down after that, Pro is the clean next step.

## Sample Targets Behind This Pack
- @Deep_Ad1959 (warm): Warm Reddit engager already named a repeated workflow risk, so the fastest path is a founder-led diagnostic.
- @game-of-kton (warm): Warm Reddit engager already works on advanced agent memory, so discovery should center on one repeated failure pattern.
- @leogodin217 (warm): Warm Reddit engager already described a mature workflow, so the next step is a targeted diagnostic on one failure mode.
- @Enthu-Cutlet-1337 (warm): Warm Reddit engager already understands the adaptive-gate thesis, so offer one concrete workflow hardening diagnostic.
- montenegronyc/backporcher (cold): Lead with one business-system workflow that needs approval boundaries, rollback safety, and proof.
- dolutech/engine_context (cold): Lead with one business-system workflow that needs approval boundaries, rollback safety, and proof.

## 90-Day Measurement Plan
- North star: codex_install_intent_to_paid_intent
- Policy: Treat Codex page views, guide opens, and bundle downloads as acquisition evidence only after a tracked checkout start or qualified workflow-hardening conversation exists.
- Minimum useful signal: one tracked Pro checkout start or one qualified workflow-hardening conversation
- Strong signal: three tracked paid-intent events across Pro or Workflow Hardening Sprint motion

Tracked metrics:
- codex_install_page_views
- setup_guide_clicks
- bundle_download_clicks
- pro_checkout_starts
- qualified_team_conversations
- paid_conversions

Milestones:
- days_0_30: Keep the Codex install page, setup guide, and release bundle aligned with proof links and tracked follow-on offers. Decision rule: Do not rewrite the Codex value prop until guide clicks or checkout starts show a mismatch.
- days_31_60: Promote whichever paid motion converts better after Codex install intent: Pro or Workflow Hardening Sprint. Decision rule: If setup-guide traffic rises without paid intent, move the proof-backed offer stack higher on the Codex page and guide.
- days_61_90: Decide whether Codex remains a self-serve lane or becomes a workflow-hardening entry point for teams. Decision rule: Only prioritize team rollout motion when qualified conversations exist.

Do not count as success:
- page views without guide clicks
- bundle downloads without a tracked follow-on event
- unverified revenue, install, or marketplace approval claims
