agent-vault GEMINI.md

A set of repository instructions for agent-vault, including how to maintain scaffolding, generate project context, author pull requests, and identify automated GitHub posts.

In plain words
What is it for?
Use it when editing agent-vault defaults, changing generated-project behavior, creating pull requests, or writing GitHub issues and comments.
Why use it?
It keeps changes to the scaffold and project-generation scripts consistent and makes agent-authored GitHub activity identifiable.

Instructions file for Gemini CLI

Install

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.

agentmods
npx agentmods add instructions/ssheld/agent-vault/gemini-md
Clone the repo
git clone --depth 1 https://github.com/ssheld/agent-vault

Made for: Gemini CLI.

Per session 450 This file is loaded in full into every session.
When invoked 450 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 98% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00450 $0.00450
Opus 5 $0.00225 $0.00225
Sonnet 5 $0.00090 $0.00090
Haiku 4.5 $0.00045 $0.00045

Measured 2d ago against content hash 85e833ad8ac2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agent-vault 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 2d 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.

Origin

This is a copy

98% identical to agent-vault CLAUDE.md — 2 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.

GEMINI.md · 37 lines

What it actually says

GEMINI.md

Purpose

This repository holds reusable scaffold files for agent-vault/.

Rules

  • Edit scaffold/agent-vault/ for defaults used in future project initialization.
  • Do not store project-specific context in this repository.
  • Generate project context only via scripts/new-project.sh.
  • When updating generated-project behavior, modify scaffold files and script templates together.

PR Authoring

  • For agent-authored pull requests in generated projects, follow scaffold/agent-vault/AGENTS.md section PR Authoring Standards.
  • Use .github/pull_request_template.md when present.

GitHub Post Attribution

  • For GitHub issues, issue comments, and non-review PR conversation comments, begin the body with:
> 🤖 **Post by {Model Name}** · via {Client Tool}
  • Use your actual model name/version when known. If the exact version is unavailable, use the best identifier you have.
  • If the post is specifically PR review feedback or a PR review-feedback response, use the review-policy format instead.
  • Never present GitHub posts as if they are the human account owner's personal opinion.
  • Prefer repo-relative paths or GitHub links over local filesystem paths in GitHub posts.

@scaffold/agent-vault/review-policy.md

Target Project Usage

In generated project vaults:

  • agent-vault/Templates/ is template source only. Instantiated notes belong in canonical runtime files under agent-vault/.
  • Start substantive work by reading agent-vault/README.md, agent-vault/context-log.md, agent-vault/plan.md, and agent-vault/coding-standards.md.
  • Skim agent-vault/open-questions.md for blockers and agent-vault/decision-log.md for active decisions relevant to the task.
  • Use agent-vault/context-log.md as canonical cross-session memory.
  • Use agent-vault/daily/, agent-vault/design-log/, agent-vault/context/handoffs/, and agent-vault/decisions/ for runtime artifacts when the workflow calls for them.
Changes

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.

  1. 2d ago First seen · 37 lines · 450 tokens per session scan A 85e833ad8ac2

Subscribe to this mod's changes

agent-vault GEMINI.md is an instructions file published in the GitHub repository ssheld/agent-vault (2 stars, last pushed 1mo ago), licensed MIT. It adds 450 tokens to every session, about $0.0022 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to agent-vault CLAUDE.md, differing in 2 lines, and is treated as a copy.

Related

Other instructions, from other repositories

vibe-coding-essentials AGENTS.md

Instructions for ashp15205/vibe-coding-essentials, covering agents.md — vibe coding essentials runtime, identity, mvp context (update daily), active mode and core rules.

ashp15205/vibe-coding-essentials · 1,394 tokens

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).

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens