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/arsenyspb/comet-boundary/gemini-mdgit clone --depth 1 https://github.com/arsenyspb/comet-boundaryWrote 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/arsenyspb/comet-boundary/gemini-md)<a href="https://agentmods.dev/instructions/arsenyspb/comet-boundary/gemini-md"><img src="https://agentmods.dev/badge/instructions/arsenyspb/comet-boundary/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.00403 | $0.00403 |
| Opus 5 | $0.00201 | $0.00201 |
| Sonnet 5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
comet-boundary 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 6d 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
Project: Comet Boundary (Gemini CLI Context)
🎯 Model-Specific Instructions
This file provides Gemini-specific strategies for operating within this repository. For general architectural grounding, refer to AGENTS.md.
1. Context Efficiency
- State Discovery: Use
gh issue listto identify active tasks before proposing changes. - Environment State: Run
./scripts/02_verify-setup.shas your first turn to establish a verified baseline. - Log Inspection: When debugging, use
docker logsfor the relevant service (backend/frontend) rather than reading massive log files.
2. Tool-Calling Optimization
- Parallelism: You can run
grep_searchandglobin parallel to map dependencies quickly. - Surgical Edits: Favor the
replacetool overwrite_filefor existing components to minimize token usage. - Sequential Dependencies: If a tool depends on the side-effect of a previous one (e.g.,
make setupbeforemake start), setwait_for_previous: true.
3. Architectural Standards
- HVD Alignment: All planning, architectural decisions, and infrastructure implementations MUST align with HashiCorp Validated Designs. Before proposing changes or writing configuration, you MUST read the relevant guides in
docs/hvd/and validate your approach against them. - Host Abstraction: NEVER create targets using the
-addressattribute. All new targets MUST follow the hierarchy: Host Catalog -> Host -> Host Set -> Target.
🚀 First-Run Access
If you are starting a new session, verify the environment:
./scripts/02_verify-setup.sh
If verification fails, establish a fresh state:
make replay
Access Details: Check .env for credentials. LDAP users are alice and bob (password: changeme).
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.
- 6d ago First seen · 33 lines · 403 tokens per session scan A af76054d1c82
comet-boundary GEMINI.md is an instructions file published in the GitHub repository arsenyspb/comet-boundary (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 403 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-08-31.
Other instructions, from other repositories
vuestrata AGENTS.md
AGENTS.md instructions for boussadjra/vuestrata, covering using vite+, the unified toolchain for the web, built-in commands vs scripts, tool versions, review checklist and vuestrata project rules.
vuestrata CLAUDE.md
Claude Code instructions for boussadjra/vuestrata, covering claude.md, the one thing that trips people up, slash commands, verifying and testing reka-backed components.
clum AGENTS.md
AGENTS.md instructions for tddh/clum, covering clum 项目开发规则, mcp 工具使用规则（最高优先级）, 开发规范, 项目结构 and 常用命令.
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).
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 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).