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.
npx agentmods add instructions/stevenathompson/run-long-command/gemini-mdgit clone --depth 1 https://github.com/stevenAthompson/run-long-commandWhat 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.
| Model | Per session | Once 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 |
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.
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
- Environment Check: The tool first verifies that it is running within a
tmuxsession namedgemini-cli. This is required for the tool to "wake up" the agent upon completion. - Immediate Return: If the environment is valid, the tool spawns the command as a detached background process and returns immediately to the agent.
- Agent Continuation: The agent receives a confirmation message and can continue with other tasks or end its turn.
- Completion Notification: Once the background process finishes, the tool uses
tmux send-keysto inject a completion message into thegemini-clisession. 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)
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.
- 3d ago First seen · 60 lines · 571 tokens per session scan A 157c4a768dce
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.
Other instructions, from other repositories
self-command GEMINI.md
Instructions for stevenAthompson/self-command, covering self command extension, tools, 1. selfcommand, 2. geminisleep and 3. watchlog.
security GEMINI.md
Instructions for gemini-cli-extensions/security, covering standard operating procedures: security analysis guidelines, persona and guiding principles, skillset: permitted tools & investigation, skillset: sast vulnerability analysis and 1.1. hardcoded secrets.
jules GEMINI.md
Instructions for gemini-cli-extensions/jules, covering jules extension, command: /jules, activation and response, starting a jules task and jules-related queries.
pickle-rick-extension GEMINI.md
Instructions for galdawave/pickle-rick-extension, covering pickle rick extension, project overview, key components, 1. configuration and 2. persona definition.
gemini-faf-mcp GEMINI.md
Instructions for Wolfe-Jam/gemini-faf-mcp, covering gemini.md — gemini-faf-mcp, test & verify, where things live, stack and before changing things.
code-review GEMINI.md
Instructions for gemini-cli-extensions/code-review: The code-review extension introduces the following commands.