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/panoptes/panoptes-utils/gemini-mdgit clone --depth 1 https://github.com/panoptes/panoptes-utilsWrote 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/panoptes/panoptes-utils/gemini-md)<a href="https://agentmods.dev/instructions/panoptes/panoptes-utils/gemini-md"><img src="https://agentmods.dev/badge/instructions/panoptes/panoptes-utils/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.00399 | $0.00399 |
| Opus 5 | $0.00199 | $0.00199 |
| Sonnet 5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
panoptes-utils 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.
What it actually says
Gemini CLI Guidelines for PANOPTES Utilities
This document provides specific instructions for the Gemini CLI agent. For all general project guidelines, development workflows, and technical standards, refer to the primary agent documentation.
Primary Guidelines
Default to AGENTS.md: All architectural patterns, coding standards, testing requirements, and module-specific instructions defined in AGENTS.md are foundational mandates and take absolute precedence.
Gemini-Specific Instructions
Environment & Tooling
- UV Executable: Always use the
uvexecutable for environment management, dependency installation, and running commands (e.g.,uv run pytest,uv lock). - Shell Commands: When using
run_shell_command, ensure that commands are compatible with theuvenvironment.
Workflow Integration
- Documentation: All documentation must be written in Markdown for MkDocs. Do not use reStructuredText (.rst) or Sphinx.
- Research Phase: Use
grep_searchandglobto align with the patterns described inAGENTS.mdbefore proposing changes. - Validation: Always run tests using
uv run pytestafter any modification. Note the specific testing markers and plot-blocking doctests mentioned inAGENTS.md. - Changelog: Rigorously follow the
CHANGELOG.mdupdate requirements specified in the "Making Changes" section ofAGENTS.md.
Utility Awareness
- Search Before Implementation: Always check
panoptes.utilsfor existing functionality. Specifically, usepanoptes.utils.serializersfor any data transmission or persistence tasks to ensure astronomical types (Quantities, Times) are handled correctly and consistently.
Quick Links
- AGENTS.md - Full project guidelines.
- CONTRIBUTING.md - Development workflow.
- pyproject.toml - Dependencies and tool configuration.
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 · 28 lines · 399 tokens per session scan A 572caf197757
panoptes-utils GEMINI.md is an instructions file published in the GitHub repository panoptes/panoptes-utils (4 stars, last pushed 2d ago), licensed MIT. It adds 399 tokens to every session, about $0.0020 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-09-04.
Other instructions, from other repositories
presidio recognizers.instructions.md
Instructions for data-privacy-stack/presidio, covering recognizer changes, the load-bearing rule: test the configuration path, placement and naming, pattern scores and context words.
nina AGENTS.md
AGENTS.md instructions for isbeorn/nina, covering agents.md, scope, documentation boundary, repository knowledge and code style and formatting.
PyAutoArray copilot-instructions.md
Copilot instructions for PyAutoLabs/PyAutoArray: You are working on PyAutoArray, the low-level data-structure and numerical layer of the PyAuto ecosystem (package autoarray).
specs-driven-development-spring-angular frontend-code.instructions.md
Frontend code guardrails for Angular implementation, testing, and accessibility.
ai-instructions spring-boot-test.instructions.md
Spring Boot testing contract for layer-focused tests, API-contract assertions, and cross-cutting governance checks.
kernel_chat GEMINI.md
Instructions for Ravi-Teja-konda/kernel_chat, covering building and running, writing tests, test structure and framework, mocking (vi from vitest) and commonly mocked modules.