Borrowing it
Nothing to install: this file belongs to cskwork/oh-my-symphony. 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/cskwork/oh-my-symphony/main/GEMINI.mdgit clone --depth 1 https://github.com/cskwork/oh-my-symphonyWrote 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/cskwork/oh-my-symphony/gemini-md)<a href="https://agentmods.dev/instructions/cskwork/oh-my-symphony/gemini-md"><img src="https://agentmods.dev/badge/instructions/cskwork/oh-my-symphony/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.00829 | $0.00829 |
| Opus 5 | $0.00415 | $0.00415 |
| Sonnet 5 | $0.00166 | $0.00166 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
oh-my-symphony 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GEMINI.md: Gemini CLI entry point
This repo is Symphony, a polling orchestrator that dispatches coding
agents (Codex / Claude Code / Gemini / AGY / Kiro / OpenCode / Pi) at a
Kanban board. This file is
the discovery point Gemini CLI reads on startup. It gives the operator,
meaning the human or agent running symphony, the same skill guidance Claude
Code gets from .claude/skills/.
Skill activation
Gemini activates Symphony through one operator skill after reading its
metadata: read the description, then load
skills/symphony-skill/SKILL.md (via Read or read_file) and follow its
route table.
Source of truth lives in skills/symphony-skill/. .claude/skills/ is a thin
symlink layer for Claude Code's native discovery only. Do not edit through it.
skills/symphony-skill/oneshot/ and skills/symphony-skill/monorepo/ are
branch-specific subfolders for templates/scripts/references used by the
router, not separate activation routes.
Available skill (operator-facing)
symphony-skill
Use when the user wants to dispatch coding agents (Codex / Claude Code / Gemini / AGY / Kiro / OpenCode / Pi) against a Kanban board via this
oh-my-symphonyrepo — adding/listing/transitioning tickets, launching the TUI, inspecting orchestrator state, customizing the workflow (lanes, per-state prompts), delegating sub-tasks to free up context, one-shotting a prompt into an evidence-gated board, bootstrapping a monorepo workflow, or diagnosing dispatch failures. Triggers on phrases like "add a symphony task", "run symphony", "dispatch this ticket", "symphony board", "WORKFLOW.md", "symphony tui won't start", "ticket failed with worker_exit", "customize kanban states", "deploy pipeline workflow", "delegate to symphony", "agent.kind: pi", "agent silent for N seconds", "one-shot this", "decompose and dispatch with proof", or "symphony monorepo".
Entry: skills/symphony-skill/SKILL.md
Worker-side guidance
Dispatched Gemini workers (running inside a per-ticket workspace) do
not consume these operator skills. Worker behavior comes from
WORKFLOW.md's prompts.base + prompts.stages map, which renders stage
prompts from docs/symphony-prompts/<flavor>/. That prompt layer is
already cross-platform. Codex, Claude, Gemini, and Pi workers all receive the
same rendered prompt for a given ticket state.
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 · 74 lines · 829 tokens per session scan A b0f48c707634
oh-my-symphony GEMINI.md is an instructions file published in the GitHub repository cskwork/oh-my-symphony (25 stars, last pushed today), licensed Apache-2.0. It adds 829 tokens to every session, about $0.0041 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
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).
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 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.
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.