Borrowing it
Nothing to install: this file belongs to juanklagos/spec-driven-development-template. 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/juanklagos/spec-driven-development-template/main/GEMINI.mdgit clone --depth 1 https://github.com/juanklagos/spec-driven-development-templateWrote 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/juanklagos/spec-driven-development-template/gemini-md)<a href="https://agentmods.dev/instructions/juanklagos/spec-driven-development-template/gemini-md"><img src="https://agentmods.dev/badge/instructions/juanklagos/spec-driven-development-template/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.
<a href="https://agentmods.dev/instructions/juanklagos/spec-driven-development-template/gemini-md"><img src="https://agentmods.dev/badge/instructions/juanklagos/spec-driven-development-template/gemini-md.svg" alt="Reviewed on agentmods" width="80" 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.00410 | $0.00410 |
| Opus 5.5 | $0.00164 | $0.00164 |
| Sonnet 5.5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
spec-driven-development-template 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.
What it actually says
Gemini Operating Rules for this Template
Canonical source:
template-context/core-instructions/AGENT_OPERATING_SYSTEM.mdsdd.policy.yaml
Hard stop:
- No code before approved spec and consistent plan.
- No hay código sin spec aprobada y plan consistente.
Execution workspace:
- Inside THIS template repository, put runnable code under
www/<project-name>/. - For a project that already exists somewhere else — the common case — install the compact
spec/sidecar in it and leave the code where it is. That is the recommended default workspace for real work. - Dentro de ESTA plantilla, el código ejecutable va en
www/<nombre-proyecto>/. - Para un proyecto que ya existe en otro sitio —el caso normal— instala el sidecar compacto
spec/y deja el código donde está. Ese es el espacio de trabajo recomendado por defecto para el trabajo real. - The user may choose another target path.
- If the target project lives inside this template, keep it under
www/. - For real external projects, install the compact
spec/sidecar and keep code in the project root. - Para proyectos reales externos, instala el sidecar compacto
spec/y mantén el código en la raíz del proyecto.
Decision log:
- Record a decision in
bitacora/decisiones/YYYY-MM-DD-<slug>.md(use/sdd:decision) when it chose between real alternatives, when it will be expensive to reverse, or when a future reader would ask "why is it like this?". - Registra una decisión cuando eligió entre alternativas reales, cuando revertirla será caro, o cuando alguien preguntaría después "¿por qué es así?".
- Every record includes a "when to revisit" section, and every rationale points at a source. Never invent rationale or dates.
Session contract:
- objective
- active_spec
- changes
- validation
- risks
- decision_recorded
- next_step
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 · 34 lines · 410 tokens per session scan A c488d5b41e75
spec-driven-development-template GEMINI.md is an instructions file published in the GitHub repository juanklagos/spec-driven-development-template (21 stars, last pushed 2mo ago), licensed MIT. It adds 410 tokens to every session, about $0.0016 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-30.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.