Borrowing it
Nothing to install: this file belongs to allenhutchison/obsidian-gemini. 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/allenhutchison/obsidian-gemini/master/AGENTS.mdgit clone --depth 1 https://github.com/allenhutchison/obsidian-geminiWrote 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/allenhutchison/obsidian-gemini/agents-md)<a href="https://agentmods.dev/instructions/allenhutchison/obsidian-gemini/agents-md"><img src="https://agentmods.dev/badge/instructions/allenhutchison/obsidian-gemini/agents-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.07893 | $0.07893 |
| Opus 5 | $0.03947 | $0.03947 |
| Sonnet 5 | $0.01579 | $0.01579 |
| Haiku 4.5 | $0.00789 | $0.00789 |
Grade A, and why
obsidian-gemini AGENTS.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.
How it starts
The opening of the file, as written. The whole thing — 363 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Overview
Obsidian Gemini Scribe is an Obsidian plugin that integrates Google's Gemini AI models for AI-driven assistance within Obsidian. It provides context-aware chat, document summarization, text rewriting, and IDE-style completions.
Project Structure & Module Organization
src/contains TypeScript plugin code;src/main.tsis the entry point with domain folders such asagent/,api/,tools/,ui/, andservices/, plus shared utilities inutils/.docs/hosts user and operator guides;prompts/ships default agent prompts;evals/holds the agent eval harness (task fixtures, runner, baselines).- Unit tests live in the
test/directory mirroringsrc/structure as*.test.ts; generated artifacts (main.js,manifest.json,styles.css) stay in the repo root for Obsidian.
Commands
Development
npm install # Install dependencies
npm run dev # Development build with watch mode
npm run build # Production build (generates refs, runs TypeScript check, then bundles)
npm run generate-refs # Regenerate help references from docs/ (runs automatically in build/dev)
npm test # Run Vitest tests
npm run format # Format code with Prettier
npm run format-check # Check formatting without changes
npm run lint # Lint with ESLint (eslint-plugin-obsidianmd recommended preset)
npm run lint:fix # Auto-fix ESLint violations where possible
npm run lint:cycles # Fail on circular imports (madge --circular over src/; baseline is 0 and CI's lint workflow enforces it)
npm run knip # Detect unused files, exports, types, and dependencies (configured in knip.json; CI's knip workflow enforces it, so a newly-dead export fails the PR — put intentional public surface in knip.json rather than re-arguing it per PR)
npm run install:test-vault # Copy built artifacts into test vault. Target precedence: TEST_VAULT_PLUGIN_DIR (exact plugin folder, validated by id) > TEST_VAULT_DIR (vault root, scanned by id) > default ~/Obsidian/Test Vault
npm run translate # Regenerate AI translations in src/i18n/ (needs GOOGLE_API_KEY; not part of build/test — runs in its own `Update UI translations` workflow on en.ts changes, or manually)
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.
- 2d ago Changed · +81 tokens per session c2348d7c6d9d
- 8d ago First seen · 363 lines · 7,812 tokens per session scan A be6f15a2174a
obsidian-gemini AGENTS.md is an instructions file published in the GitHub repository allenhutchison/obsidian-gemini (523 stars, last pushed yesterday), licensed MIT. It adds 7,893 tokens to every session, about $0.0395 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-30.
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.