Borrowing it
Nothing to install: this file belongs to Amartuvshins0404/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/Amartuvshins0404/clean-code-skills/main/GEMINI.mdgit clone --depth 1 https://github.com/Amartuvshins0404/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/amartuvshins0404/clean-code-skills/gemini-md)<a href="https://agentmods.dev/instructions/amartuvshins0404/clean-code-skills/gemini-md"><img src="https://agentmods.dev/badge/instructions/amartuvshins0404/clean-code-skills/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.00415 | $0.00415 |
| Opus 5 | $0.00208 | $0.00208 |
| Sonnet 5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00042 | $0.00042 |
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 8d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GEMINI.md
Clean-code instructions for Gemini and other agents that read root project guidance.
Activation
Apply the clean-code skill whenever a task involves writing, editing, reviewing, testing, or refactoring code. If the skill is not available by name, read it from skills/clean-code/SKILL.md or .github/skills/clean-code/SKILL.md. This applies to every programming language, framework, query language, script, configuration format, and infrastructure file.
For decisions about complexity, change, scale, optimization, or interface design, also consult skills/clean-code/references/canon.md, which synthesizes principles from primary engineering sources with attribution.
Behavior Contract
- Clarify assumptions that would change the implementation.
- Inspect nearby code before editing.
- Match the project's existing idioms.
- Make the smallest change that satisfies the request.
- Prefer readable names and cohesive structure over comments that explain messy code.
- Keep functions, components, classes, modules, jobs, and queries focused.
- Treat errors, boundaries, security, and concurrency as part of the design.
- Add or update tests when risk, behavior, or regressions require them.
- Verify before claiming the work is complete.
- Report limitations honestly.
- Treat every observable behavior of an interface with multiple users as a contract; change with care or version it.
- When the same area keeps demanding tactical patches, name the strategic problem instead of patching again.
Guardrails
- Do not introduce speculative abstractions or configuration.
- Do not rewrite unrelated code.
- Do not change formatting or comments outside the requested area.
- Do not hide failures behind broad catches, null fallbacks, or silent defaults.
- Do not impose one language's style on another language.
- Do not claim tests, builds, or linters pass unless they were run and their output supports the claim.
When a project has more specific instructions, follow those first and use these clean-code rules as the shared baseline.
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.
- 8d ago First seen · 36 lines · 415 tokens per session scan A 4296f235b8ef
clean-code-skills GEMINI.md is an instructions file published in the GitHub repository Amartuvshins0404/clean-code-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 415 tokens to every session, about $0.0021 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-31.
Other instructions, from other repositories
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.
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).
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).
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.
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.