# Gemini CLI coding-agent preflight proof

**Named segment:** teams using Gemini CLI / `google-gemini/gemini-cli` or a Gemini-style terminal coding agent before they let the assistant inspect a real repository, propose edits, execute shell commands, or touch package/deploy workflows.

**Public target evidence captured this pulse:** `google-gemini/gemini-cli` at https://github.com/google-gemini/gemini-cli has 105,795 GitHub stars and was last updated `2026-07-06T08:59:50Z`. Description observed: "An open-source AI agent that brings the power of Gemini directly into your terminal.".

## Why this buyer should care before checkout

Gemini CLI users often run the assistant from a terminal with direct workspace access. The free scanner gives a local, shareable preflight receipt before repository context, package scripts, workflow files, MCP/tool config, or secret-adjacent paths are brought into the agent session.

## 60-second local proof

1. Run the free lite scanner before expanding a Gemini CLI session into a repo.
2. Attach the generated Markdown receipt to the issue, PR, or task where the agent work is being authorized.
3. Use the Green / Yellow / Red output to decide whether the free receipt is enough or whether to buy the paid starter pack for repeatable command hooks, review comments, and handoff templates.

## Buy / skip trigger for Gemini CLI teams

- **Green:** keep using the free scanner and paste the receipt into the PR/task.
- **Yellow or Red:** buy the $7 starter pack at https://payhip.com/b/1nmxV when the repo includes checked-in agent config, package scripts, deploy workflows, tool/MCP definitions, or secret-adjacent environment paths that need a repeatable preflight command and review comment.

## Copy/paste receipt example

```text
Gemini CLI workspace preflight: ran ai_agent_safety_lite.py before expanding terminal-agent scope.
Result: Yellow — package scripts plus workflow/tool config detected.
Action: require repo preflight hook + review comment before Gemini-assisted edits merge.
Paid trigger: buy the $7 pack only if this Yellow/Red receipt needs repeatable commands/templates.
```

## Privacy and trust posture

The free proof stays local: no private code, secrets, or repository contents need to be sent to the seller. Buyers can verify the public source first at the GitHub repo, then use the paid pack only when they want the packaged hook/template workflow.