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/leeyudok/agents-scaffold/gemini-mdgit clone --depth 1 https://github.com/LeeYudok/agents-scaffoldWrote 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/leeyudok/agents-scaffold/gemini-md)<a href="https://agentmods.dev/instructions/leeyudok/agents-scaffold/gemini-md"><img src="https://agentmods.dev/badge/instructions/leeyudok/agents-scaffold/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.00107 | $0.00107 |
| Opus 5 | $0.00053 | $0.00053 |
| Sonnet 5 | $0.00021 | $0.00021 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
agents-scaffold 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.
This is a copy
91% identical to agents-scaffold 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.
What it actually says
GEMINI.md
이 프로젝트의 가이드·규칙·컨벤션은 AGENTS.md 를 단일 진실원천으로 한다.
아래 import 로 AGENTS.md 내용을 그대로 로드한다.
@AGENTS.md
메모리 인덱스도 함께 로드한다(@ import 는 이 파일 전용 — AGENTS.md 는 하네스 중립을
유지하기 위해 import 를 쓰지 않는다).
@.claude/memory/MEMORY.md
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 · 12 lines · 107 tokens per session scan A 0e23162d2351
agents-scaffold GEMINI.md is an instructions file published in the GitHub repository LeeYudok/agents-scaffold (25 stars, last pushed 7d ago), licensed MIT. It adds 107 tokens to every session, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to agents-scaffold CLAUDE.md, differing in 2 lines, and is treated as a copy.
Other instructions, from other repositories
claude-code-starter-kit CLAUDE.md
Instructions for dachivadachkoria/claude-code-starter-kit, covering project: [your project name], tech stack, project structure, development commands and install dependencies.
ai-rules CLAUDE.md
Claude Code instructions for SpaceMalamute/ai-rules, covering ai rules - multi-target ai tool configurations, structure, principles, adding a technology and git.
easy-cheese python.instructions.md
Instructions for paulnsorensen/easy-cheese, covering hard rules, what to flag and what not to flag.
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core, parameterized queries, migration strategy.
AmbyKit CLAUDE.md
Claude Code instructions for ambystechcom/AmbyKit, covering claude code — notes for the ambykit repo and claude-specific.
sugar AGENTS.md
AGENTS.md instructions for roboticforce/sugar, covering sugar - agents.md, git branching rules (strict), always create branches from develop, after work is complete and then create pr targeting develop.