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 rules/pridiuksson/orchestration-patterns-for-llms/gemini-cligit clone --depth 1 https://github.com/pridiuksson/orchestration-patterns-for-llmsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/pridiuksson/orchestration-patterns-for-llms/gemini-cli)<a href="https://agentmods.dev/rules/pridiuksson/orchestration-patterns-for-llms/gemini-cli"><img src="https://agentmods.dev/badge/rules/pridiuksson/orchestration-patterns-for-llms/gemini-cli.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00852 |
| Opus 5 | $0.00000 | $0.00426 |
| Sonnet 5 | $0.00000 | $0.00170 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
gemini-cli 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona: Gemini CLI Usage Guide
Description
This document provides instructions on how to use the Gemini CLI for large codebase analysis, leveraging its massive context window. This is a reference guide for all AI agents.
Core Directive
Use the gemini -p command with the @ syntax to include large files, multiple files, or entire directories in your prompts for deep analysis, implementation verification, and architectural understanding.
How to use Gemini CLI
Using Gemini CLI for Large Codebase Analysis
When analyzing large codebases or multiple files that might exceed context limits, use the Gemini CLI with its massive context window. Use gemini -p to leverage Google Gemini's large context capacity.
File and Directory Inclusion Syntax
Use the @ syntax to include files and directories in your Gemini prompts. The paths should be relative to WHERE you run the gemini command.
Examples:
-
Single file analysis:
gemini -p "@src/main.py Explain this file's purpose and structure" -
Multiple files:
gemini -p "@package.json @src/index.js Analyze the dependencies used in the code" -
Entire directory:
gemini -p "@src/ Summarize the architecture of this codebase" -
Multiple directories:
gemini -p "@src/ @tests/ Analyze test coverage for the source code" -
Current directory and subdirectories:
gemini -p "@./ Give me an overview of this entire project" -
Or use --all_files flag:
gemini --all_files -p "Analyze the project structure and dependencies"
Implementation Verification Examples
-
Check if a feature is implemented:
gemini -p "@src/ @lib/ Has dark mode been implemented in this codebase? Show me the relevant files and functions" -
Verify authentication implementation:
gemini -p "@src/ @middleware/ Is JWT authentication implemented? List all auth-related endpoints and middleware" -
Check for specific patterns:
gemini -p "@src/ Are there any React hooks that handle WebSocket connections? List them with file paths"
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 · 93 lines · 0 tokens per session scan A a655ecbcf0e1
gemini-cli is a cursor rule published in the GitHub repository pridiuksson/orchestration-patterns-for-llms (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 852 tokens. 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 cursor rules, from other repositories
executing-red-team-engagement-planning
Red team engagement planning is the foundational phase that defines scope, objectives, rules of engagement (ROE), threat model selection, and operational timelines before any offensive testing begins.
omni-yaml-conventions
Omni Analytics model YAML conventions — file types, syntax patterns, field references, and common pitfalls. Apply when writing or editing Omni view, topic, or relationship YAML.
cypress-e2e-testing-cursorrules-prompt-file
Cursor rules for Cypress development with E2E testing.
deno-integration-techniques-cursorrules-prompt-fil
Cursor rules for Deno development with integration techniques.
cursorrules
Cursor rule "cursorrules" from Clarity-Digital-Twin/brain-go-brrr, covering .cursorrules - brain-go-brrr project (fixed architecture), rule #1: no parallel implementations ever, experiments/trainanything.py - must be thin, rule #2: check before building and rule #3: normalization is critical.
typescript-coding-style
description: Enforces code style and best practices for TypeScript files. globs: /.ts.