run-long-command GEMINI.md

Instructions for a Gemini CLI extension that runs long shell commands in the background. The Gemini CLI is a command-line AI assistant, and tmux is a tool for keeping terminal sessions running.

In plain words
What is it for?
Use it for commands expected to take a long time, such as heavy builds, extended tests, or large data-processing jobs, in the required tmux environment.
Why use it?
It prevents lengthy builds, tests, or data jobs from blocking the assistant's conversation and reports when they finish.

Instructions file for Gemini CLI

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/stevenathompson/run-long-command/gemini-md
Clone the repo
git clone --depth 1 https://github.com/stevenAthompson/run-long-command

Made for: Gemini CLI.

Per session 571 This file is loaded in full into every session.
When invoked 571 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00571 $0.00571
Opus 5 $0.00285 $0.00285
Sonnet 5 $0.00114 $0.00114
Haiku 4.5 $0.00057 $0.00057

Measured 3d ago against content hash 157c4a768dce, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

run-long-command GEMINI.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

GEMINI.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Run Long Command Extension

This extension provides the run_long_command tool, which allows the Gemini CLI agent to execute long-running shell commands in the background without blocking further interaction.

Usage

When you encounter a task that involves a command expected to take a significant amount of time (e.g., complex builds, long-running tests, data processing), use run_long_command.

Tool Signature

run_long_command({
  command: string; // The shell command to execute.
});

Example

{
  "command": "npm run build-heavy-project"
}

How It Works

  1. Environment Check: The tool first verifies that it is running within a tmux session named gemini-cli. This is required for the tool to "wake up" the agent upon completion.
  2. Immediate Return: If the environment is valid, the tool spawns the command as a detached background process and returns immediately to the agent.
  3. Agent Continuation: The agent receives a confirmation message and can continue with other tasks or end its turn.
  4. Completion Notification: Once the background process finishes, the tool uses tmux send-keys to inject a completion message into the gemini-cli session. This message effectively "nudges" the agent to resume and process the results.

Response to the Agent

Initial Response (Immediate)

When the tool is called, it returns a text content block similar to:

Command "npm run build-heavy-project" started in the background (PID: 12345, CWD: /path/to/project). I will notify you when it finishes.

Completion Message (via tmux)

When the command completes, a message will appear in your input buffer as if typed by the user:

Background command completed: "npm run build-heavy-project" (Exit code: 0) Output: [Project built successfully in 120s...]

If the command fails to start or encounters an error, the notification will reflect the failure:

Background command failed: "npm run build-heavy-project" (Error: spawn npm ENOENT)

Read the full file on GitHub · 60 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 60 lines · 571 tokens per session scan A 157c4a768dce

Subscribe to this mod's changes

run-long-command GEMINI.md is an instructions file published in the GitHub repository stevenAthompson/run-long-command (7 stars, last pushed 7mo ago), licensed MIT. It adds 571 tokens to every session, about $0.0029 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.