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.
git clone --depth 1 https://github.com/Jamkris/everything-gemini-codeWrote 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/agents/jamkris/everything-gemini-code/observer)<a href="https://agentmods.dev/agents/jamkris/everything-gemini-code/observer"><img src="https://agentmods.dev/badge/agents/jamkris/everything-gemini-code/observer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/jamkris/everything-gemini-code/observer"><img src="https://agentmods.dev/badge/agents/jamkris/everything-gemini-code/observer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00023 | $0.01079 |
| Opus 5.5 | $0.00009 | $0.00432 |
| Sonnet 5.5 | $0.00005 | $0.00216 |
| Haiku 4.5 | $0.00002 | $0.00108 |
Grade A, and why
observer 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 1mo 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.
This is a copy
94% identical to observer — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observer Agent
A background agent that analyzes observations from Gemini CLI sessions to detect patterns and create instincts.
When to Run
- After significant session activity (20+ tool calls)
- When user runs
/analyze-patterns - On a scheduled interval (configurable, default 5 minutes)
- When triggered by observation hook (SIGUSR1)
Input
Reads observations from ~/.gemini/homunculus/observations.jsonl:
{"timestamp":"2025-01-22T10:30:00Z","event":"tool_start","session":"abc123","tool":"Edit","input":"..."}
{"timestamp":"2025-01-22T10:30:01Z","event":"tool_complete","session":"abc123","tool":"Edit","output":"..."}
{"timestamp":"2025-01-22T10:30:05Z","event":"tool_start","session":"abc123","tool":"Bash","input":"npm test"}
{"timestamp":"2025-01-22T10:30:10Z","event":"tool_complete","session":"abc123","tool":"Bash","output":"All tests pass"}
Pattern Detection
Look for these patterns in observations:
1. User Corrections
When a user's follow-up message corrects Gemini's previous action:
- "No, use X instead of Y"
- "Actually, I meant..."
- Immediate undo/redo patterns
→ Create instinct: "When doing X, prefer Y"
2. Error Resolutions
When an error is followed by a fix:
- Tool output contains error
- Next few tool calls fix it
- Same error type resolved similarly multiple times
→ Create instinct: "When encountering error X, try Y"
3. Repeated Workflows
When the same sequence of tools is used multiple times:
- Same tool sequence with similar inputs
- File patterns that change together
- Time-clustered operations
→ Create workflow instinct: "When doing X, follow steps Y, Z, W"
4. Tool Preferences
When certain tools are consistently preferred:
- Always uses Grep before Edit
- Prefers Read over Bash cat
- Uses specific Bash commands for certain tasks
→ Create instinct: "When needing X, use tool Y"
Output
Creates/updates instincts in ~/.gemini/homunculus/instincts/personal/:
---
id: prefer-grep-before-edit
trigger: "when searching for code to modify"
confidence: 0.65
domain: "workflow"
source: "session-observation"
---
# Prefer Grep Before Edit
## Action
Always use Grep to find the exact location before using Edit.
## Evidence
- Observed 8 times in session abc123
- Pattern: Grep → Read → Edit sequence
- Last observed: 2025-01-22
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.
- 1mo ago First seen · 138 lines · 23 tokens per session scan A 8719134bb6b4
observer is an agent published in the GitHub repository Jamkris/everything-gemini-code (90 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 1,079 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to observer, differing in 9 lines, and is treated as a copy.
Other agents, from other repositories
redteam-source-code-analyzer
Source code security analyzer for CMS and web applications. Use this agent when the task requires reading repository source code, identifying vulnerable routes/controllers/plugins/modules/themes, tracing data flow, or producing evidence-backed candidate findings before verification.
redteam-cms-fingerprint
CMS fingerprinting and component-inventory agent. Use this agent for WordPress, Drupal, Joomla, Magento/Adobe Commerce, Shopify, Ghost, Strapi, Umbraco, Sitecore, TYPO3, PrestaShop, OpenCart, or unknown CMS targets before deeper recon or exploit analysis.
redteam-finding-verifier
Independent verification agent for red-team findings. Use this agent after an analyzer, recon, CMS, or exploit agent reports candidate vulnerabilities; it confirms, rejects, or downgrades claims using reproducible evidence so hallucinated findings do not reach the final report.
redteam-report-writer
Final report writer for red-team workflows. Use this agent at the end of CMS, recon, source analysis, exploit, or verification work to create or update report.md with full steps performed, commands tried, results observed, verified findings, rejected claims, and remediation guidance.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.