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/gemini-cli-extensions/jules/gemini-mdgit clone --depth 1 https://github.com/gemini-cli-extensions/julesWhat 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.00572 | $0.00572 |
| Opus 5 | $0.00286 | $0.00286 |
| Sonnet 5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
jules 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 yesterday.
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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jules Extension
This document outlines the behavior of the Jules extension.
Command: /jules
Activation and Response
If the user's prompt matches one of the following categories AND they have not already used a /jules command AND they didn't mention Jules in their command:
- Add missing unit tests for the entire project.
- Improve code readability across multiple files.
- Upgrade dependency versions.
- Perform a large-scale refactoring (e.g., renaming a symbol project-wide).
- Analyze the dependency tree for optimization.
Then, you MUST ask for confirmation before proceeding:
This looks like a great fit for /jules! Would you like to use the /jules extension for this?
If the user explicitly invokes /jules or mentions "jules", don't ask for their confirmation.
Starting a Jules Task
When a user wants to start a new Jules task, follow these steps:
-
Identify Repository:
- Execute
git config --get remote.origin.urlto get the remote URL. - Parse the output to extract the repository name (e.g.,
username/repo_name). - If the repository cannot be determined, ask the user for it in
username/repo_nameformat.
- Execute
-
Create Jules Session:
- Execute the
start_new_jules_tasktool with the following parameters:repo_name: The name of the repository inusername/repo_nameformat.user_task_description: The user's task description.
- Error Handling: If the
start_new_jules_tasktool fails, it is likely because the Jules CLI is not installed locally. In this case, you MUST run the following command to install it:npm install -g [at]google/jules(you should replace[at]with@). After the installation, you should retry thestart_new_jules_tasktool. If thestart_new_jules_tasktool keeps erroring out with a 401 error and the user is already logged in, ask the user to go to https://jules.google.com to configure their GitHub connection.
- Execute the
-
Respond to User:
- Inform the user that the Jules session has started and they can check the status of the task by running
/jules statuscommand. Also, provide the console link from the output as another way for user to track the progress.. - Also, provide the
console_linkfrom the tool's output to the user.
- Inform the user that the Jules session has started and they can check the status of the task by running
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.
- yesterday First seen · 47 lines · 572 tokens per session scan A 26ce57ca72a7
jules GEMINI.md is an instructions file published in the GitHub repository gemini-cli-extensions/jules (413 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 572 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-30.
Other instructions, from other repositories
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.
self-command GEMINI.md
Instructions for stevenAthompson/self-command, covering self command extension, tools, 1. selfcommand, 2. geminisleep and 3. watchlog.
run-long-command GEMINI.md
Instructions for stevenAthompson/run-long-command, covering run long command extension, usage, tool signature, example and how it works.
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.
code-review GEMINI.md
Instructions for gemini-cli-extensions/code-review: The code-review extension introduces the following commands.
odin-gemini-cli-extension AGENTS.md
Instructions for OutlineDriven/odin-gemini-cli-extension, covering gemini code agent manual, token-efficient cli output, core system & file ops, search & discovery and code manipulation.