Borrowing it
Nothing to install: this file belongs to GuitarAlchemist/ga. 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/GuitarAlchemist/ga/main/GEMINI.mdgit clone --depth 1 https://github.com/GuitarAlchemist/gaWrote 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/guitaralchemist/ga/gemini-md)<a href="https://agentmods.dev/instructions/guitaralchemist/ga/gemini-md"><img src="https://agentmods.dev/badge/instructions/guitaralchemist/ga/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.00520 | $0.00520 |
| Opus 5 | $0.00260 | $0.00260 |
| Sonnet 5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
ga 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 4d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guitar Alchemist — Agent Configuration
This repository uses a hybrid workflow:
- Conductor (context layer) — product definition, tech stack, track registry, institutional memory
- Compound Engineering (execution layer) — plan → work → review → compound cycle
Conductor Context Layer
Project context, architecture decisions, and track tracking.
Quick Links
Compound Engineering Execution Layer
Day-to-day execution workflow. Use these commands to drive work on any track.
Workflow
/ce:plan → /ce:work → /ce:review → /ce:compound → repeat
Commands
| Command | What it does |
|---|---|
/ce:brainstorm <idea> |
Structured ideation before planning |
/ce:plan <feature> |
Creates docs/plans/YYYY-MM-DD-<type>-<name>-plan.md |
/ce:work <plan-file> |
Executes the plan with todo tracking + incremental commits |
/ce:review |
Runs security, performance, architecture reviewer agents |
/ce:compound |
Captures learnings into docs/solutions/ |
Working Artifacts
- Brainstorms:
docs/brainstorms/— raw exploration docs - Plans:
docs/plans/— structured work plans (output of/ce:plan) - Solutions:
docs/solutions/— captured learnings (output of/ce:compound)
Active Tracks → Plans
Drive Conductor tracks through the Compound Engineering workflow:
| Track | Status | Next Action |
|---|---|---|
spectral-rag-chatbot |
Active | /ce:plan spectral RAG chatbot remaining work |
modernization |
Active | /ce:plan modernization remaining items |
semantic-event-routing |
Proposed | /ce:brainstorm semantic event routing |
core-schema-design |
Needs Reconciliation | /ce:plan core schema reconciliation |
meai-integration |
Needs Reconciliation | /ce:plan MEAI integration reconciliation |
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.
- 4d ago First seen · 61 lines · 520 tokens per session scan A d92429143b31
ga GEMINI.md is an instructions file published in the GitHub repository GuitarAlchemist/ga (2 stars, last pushed yesterday), licensed MIT. It adds 520 tokens to every session, about $0.0026 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-09-03.
Other instructions, from other repositories
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).
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.
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 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).
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.