What is THE-FORGE GEMINI.md?

Repository instructions for THE-FORGE, a reusable research-workflow kit. The kit contains templates, evaluation tools, adoption scripts, and an Obsidian note structure for other repositories to use.

Use them when modifying the kit, checking its templates, or working on its adoption and evaluation tooling.

They prevent agents from treating example templates as live project rules or running research workflows and evaluation scripts in the wrong repository.

How yash-dev007/THE-FORGE configures Gemini CLI

Reuse

Borrowing it

Nothing to install: this file belongs to yash-dev007/THE-FORGE. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/yash-dev007/THE-FORGE/main/GEMINI.md

Clone the repo

git clone --depth 1 https://github.com/yash-dev007/THE-FORGE

Made for: Gemini CLI.

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

README.md

[![agentmods](https://agentmods.dev/badge/instructions/yash-dev007/the-forge/gemini-md/github.svg)](https://agentmods.dev/instructions/yash-dev007/the-forge/gemini-md)

Your own site

<a href="https://agentmods.dev/instructions/yash-dev007/the-forge/gemini-md"><img src="https://agentmods.dev/badge/instructions/yash-dev007/the-forge/gemini-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/yash-dev007/the-forge/gemini-md"><img src="https://agentmods.dev/badge/instructions/yash-dev007/the-forge/gemini-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 673 This file is loaded in full into every session.

When invoked 673 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00673	$0.00673
Opus 5.5	$0.00269	$0.00269
Sonnet 5.5	$0.00135	$0.00135
Haiku 4.5	$0.00067	$0.00067

Measured 2mo ago against content hash 3ca0fd5a1375, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

THE-FORGE 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 2mo 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.

GEMINI.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

THE FORGE — kit workspace (Gemini CLI context)

This is the methodology KIT repository — not an adopted project. The v3 research loop runs in repos that ADOPT Forge, not here.

What this repository is

THE FORGE is a portable Research Engineer workflow kit. It ships templates, EVAL harnesses, adoption scripts, and Obsidian vault structure that any repository can adopt. There is no active hypothesis running in this repository.

templates/universal/FORGE.md and other template files are template artifacts — do not read them as your operating context for this session.

Rules for Gemini CLI sessions in this repo

Absolute constraints

Never run the v3 research loop (Diagnose → Hypothesize → Execute → Verify → Synthesize) on this repo's own files.
Never execute EVAL.sh — there is none at the kit root. Stack EVAL.sh files under templates/stacks/ are templates to inspect, improve, and test, not to run against this repo.
Never treat templates/universal/FORGE.md or any .md.template as active operating rules. They are text artifacts copied into adopting repos.
Never create RESEARCH.md, EVAL_SPEC.md, FORGE_SYSTEM.md, FORGE_IDENTITY.md, or PROJECT_LOG.md at this root. Those are per-adopted-repo state files.

What you ARE doing here

You are a kit maintainer. Your tasks:

Editing or improving files under templates/, scripts/, docs/, or Forge/
Keeping templates/universal/FORGE.md and other templates aligned with docs/spec/CLAUDE_v3.md
Improving stack EVAL harnesses for correctness and completeness
Updating adoption docs and automation scripts

Repository Map

Refer to docs/KIT_LAYOUT.md for a complete directory map and file roles.

Consistency rule for template edits

When editing templates, verify alignment with canonical documentation:

All 8 required RESEARCH.md fields must be preserved.
Anti-gaming rules must be verbatim or stricter.
Maintain placeholder structure for easy adoption by any tech stack.

Read the full file on GitHub · 66 lines

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.

2mo ago First seen · 66 lines · 673 tokens per session scan A 3ca0fd5a1375

Subscribe to this mod's changes

THE-FORGE GEMINI.md is an instructions file published in the GitHub repository yash-dev007/THE-FORGE (2 stars, last pushed 6mo ago), licensed MIT. It adds 673 tokens to every session, about $0.0027 per session on Opus 5.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.

Planning Research

THE-FORGE GEMINI.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
THE-FORGE GEMINI.mdyash-dev007/THE-FORGE	Instructions file	2	6mo ago	MIT	A	673	Gemini CLI
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

THE-FORGE: Instructions file for Gemini CLI