Agy Powerline

The agy-powerline skill helps configure and inspect a status bar for Antigravity CLI, also called agy. On each refresh, agy pipes session JSON to a local statusline that renders the model, context window, git branch and changes, tokens, subagents, and available quota information. Quotas include Gemini's five-hour and seven-day windows, Claude/GPT, and Gemini 4 Argon when the session supplies them. Reset times appear alongside supported quotas. The package is licensed under MIT.

The skill covers setup, diagnosis, and visual customization using the package's commands. Its controlling prerequisite requires an already installed tool whose exact version, complete dependency tree, and integrity have been reviewed. It does not authorize bootstrapping an external package or activating a plugin. A missing reviewed installation stops that executable path, although static analysis can continue. A same-named workspace script or moving branch is not an acceptable substitute.

Use it when a user asks to install, repair, update, or restyle an agy statusline, inspect quotas without repeatedly entering /usage, or export an existing configuration. It does not configure status bars for Claude Code or Gemini CLI. Antigravity CLI is the required host. Windows, macOS, Linux, and WSL are supported with Node.js 20 or newer; tokensToday and tokensWeek need Node.js 22.13 or newer.

An installation request still has to satisfy the reviewed-artifact requirement. A separate installation task must pin immutable artifacts, stage them outside active assistant directories with lifecycle scripts disabled, inspect bundled files and executable entry points, and obtain activation approval. A preinstalled bootstrap command does not make its later downloads reviewed.

Inputs are the agy session fields, an approved installed tool, the user's requested appearance, and any authorized setup change. The statusline cannot display a field agy does not send. Widgets without data hide themselves; Argon information depends on an eligible plan rather than the statusline creating quota access. Shared diagnostic output should redact session details, paths, and quota metadata.

The setup workflow checks node -v, explains the download and settings change, and uses the documented initialization command only after its prerequisites are satisfied:

agy-powerline init --yes

Initialization places the local statusline in ~/.agy-powerline and changes only the statusLine setting after backing up configuration. Invalid JSON settings are refused. Failure is reported as printed rather than bypassed by hand-editing settings. The doctor command checks configuration after install or update, but its success does not prove the host loaded the bar. An authorized agy restart and actual refresh establish that separately. Later appearance changes appear on the next refresh.

Customization lists available choices before applying them and shows the command's preview. Theme, preset, layout, caps, gradient, and export commands cover colors, widgets, text layout, pill ends, row gradients, and backups. Presets include default, compact, agent, git, tokens, quotas, and full. Layouts include pills, lines, and classic. A preset replaces the widget list while preserving theme and layout; gradient off removes a gradient. The --stack option keeps agy's built-in line above the added bar.

The configure command is an interactive full-screen editor for the user's own terminal, not an assistant shell tool. Missing icon glyphs can be addressed with a Nerd Font or ASCII mode. Uninstall backs up settings and removes statusLine; --delete additionally removes local files only when requested. Imported shell-command widgets would execute on every refresh, so --allow-exec must never be passed by the assistant; only the user can approve the exact imported commands.

It suits Antigravity CLI users who want session information and controlled visual customization in their terminal. Initialization needs npm network access, while the installed statusline makes no network calls during refresh. Reviewed installation, configuration diagnosis, and actual host rendering are separate checks, each with its own evidence.