Borrowing it
Nothing to install: this file belongs to kongyo2/gemini-time-injector. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kongyo2/gemini-time-injector/main/GEMINI.mdgit clone --depth 1 https://github.com/kongyo2/gemini-time-injectorWrote 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/instructions/kongyo2/gemini-time-injector/gemini-md)<a href="https://agentmods.dev/instructions/kongyo2/gemini-time-injector/gemini-md"><img src="https://agentmods.dev/badge/instructions/kongyo2/gemini-time-injector/gemini-md.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.1 | $0.00334 | $0.00334 |
| Opus 5 | $0.00167 | $0.00167 |
| Sonnet 5 | $0.00067 | $0.00067 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
gemini-time-injector 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 8d 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.
What it actually says
Time-Injector Extension
This extension solves a known weakness of large language models: you cannot perceive real-world time on your own. While you are reasoning the wall clock keeps moving, tool calls take seconds or minutes, and the user may walk away and come back hours later — none of which is visible from text alone.
To compensate, the gemini-time-injector extension fires a hook on every
lifecycle event and feeds you <hook_context>…</hook_context> blocks
containing:
- Current ISO 8601 UTC time and local time (refreshed each turn).
- Session elapsed time since the session was opened.
- Idle gap since the previous hook event (e.g. how long the user took to reply, or how long a tool call took).
- Tool duration measured between the matching
BeforeToolandAfterToolhooks.
How to use this information
- Treat the most recent
[time-injector]block as the authoritative current time. Do not rely on your training cutoff or earlier injections. - If the idle gap or session elapsed is large, acknowledge it before acting (e.g. "It looks like a few hours have passed — let me re-check the state before continuing").
- When a tool takes notably longer than expected, mention it in your user-facing summary so the user can decide whether to investigate.
- Never invent timestamps. If asked "what time is it", quote the most recent injected time verbatim instead of guessing.
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.
- 8d ago First seen · 30 lines · 334 tokens per session scan A ba2f9e25f783
gemini-time-injector GEMINI.md is an instructions file published in the GitHub repository kongyo2/gemini-time-injector (1 stars, last pushed 3mo ago), licensed MIT. It adds 334 tokens to every session, about $0.0017 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.