Borrowing it
Nothing to install: this file belongs to btseee/clean-code-skills. 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/btseee/clean-code-skills/main/GEMINI.mdgit clone --depth 1 https://github.com/btseee/clean-code-skillsWrote 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/btseee/clean-code-skills/gemini-md)<a href="https://agentmods.dev/instructions/btseee/clean-code-skills/gemini-md"><img src="https://agentmods.dev/badge/instructions/btseee/clean-code-skills/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/btseee/clean-code-skills/gemini-md"><img src="https://agentmods.dev/badge/instructions/btseee/clean-code-skills/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.01045 | $0.01045 |
| Opus 5.5 | $0.00418 | $0.00418 |
| Sonnet 5.5 | $0.00209 | $0.00209 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
clean-code-skills 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 22d 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
88% identical to clean-code-skills clean-code.instructions.md — 10 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GEMINI.md
Clean-code instructions for Gemini CLI and Gemini-based agents. In a project that installs this package, the managed block below is kept up to date by the installer; content outside the markers is never touched. If your Gemini CLI is configured with a different contextFileName, install the agents profile as well so AGENTS.md carries the same rules.
Apply the clean-code rules whenever a task involves writing, editing, reviewing, testing, or refactoring code — every programming language, framework, query language, script, configuration format, and infrastructure file.
Clean Code Rules (clean-code-skills)
Non-negotiable for all code work.
Read the skill before non-trivial work. First existing path wins: .claude/skills/clean-code/SKILL.md, .agents/skills/clean-code/SKILL.md, .github/skills/clean-code/SKILL.md, skills/clean-code/SKILL.md. Then your stack's packs, named by the skill's scripts/detect_stack.py or references/framework-map.md.
Load project context first. If present: .clean/context.json, .clean/architecture.md, .clean/decisions.md, .clean/ledger.md, .clean/structure.md rows for your area; then project instruction files. Recorded decisions are settled. Project instructions outrank this block.
Work Loop
- Frame: behavior change, design-relevant assumptions, smallest scope, success check.
- Read first: nearby code, naming, tests, error style, framework idioms; search for existing implementations.
- Place: owning unit; which side of which boundary.
- Edit surgically: smallest diff, targeted edits (no whole-file regeneration), nothing unrelated; remove what your change orphaned.
- Verify: narrowest meaningful check, broader as risk demands.
- Review the diff against these rules, missing tests included.
Layers
- Undeclared layers (
.clean/architecture.md): follow framework pack's idiomatic structure. - Declared: Dependency Rule strict; source dependencies point inward, to higher-level policy; nothing inner names anything outer (class, function, variable, annotation, data format).
- Business rules highest; database, web, UI, framework are details behind policy-owned interfaces.
- SQL stays in data access; rows, ORM types, framework request/response objects never travel inward. Never derive business objects from framework base classes or annotate them; dependency-injection wiring in
main. - Component graph acyclic; no speculative boundary, layer, or service.
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.
- 22d ago Changed · -3 lines · -355 tokens per session 6c520cdd92c8
- 1mo ago Changed · +13 tokens per session 877585dee0df
- 1mo ago First seen · 71 lines · 1,387 tokens per session scan A e8ab2409b6f9
clean-code-skills GEMINI.md is an instructions file published in the GitHub repository btseee/clean-code-skills (14 stars, last pushed 22d ago), licensed MIT. It adds 1,045 tokens to every session, about $0.0042 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to clean-code-skills clean-code.instructions.md, differing in 10 lines, and is treated as a copy.
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.