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/.github/copilot-instructions.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/copilot-instructions)<a href="https://agentmods.dev/instructions/amartuvshins0404/clean-code-skills/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/amartuvshins0404/clean-code-skills/copilot-instructions.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.00346 | $0.00346 |
| Opus 5 | $0.00173 | $0.00173 |
| Sonnet 5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
clean-code-skills copilot-instructions.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.
What it actually says
Repository-Wide Clean-Code Instructions
These instructions guide GitHub Copilot Chat, Copilot code review, and Copilot coding agents across this repository.
Purpose
Apply clean-code discipline to all code changes and reviews, regardless of language or framework.
When .github/skills/clean-code/SKILL.md is present, treat it as the canonical detailed guidance and use this file as the repository-wide baseline.
General Standards
- Inspect nearby code and tests before editing.
- Match local style, architecture, naming, and framework idioms.
- Keep diffs focused on the user's request.
- Avoid speculative abstractions, unused extension points, and new dependencies without evidence.
- Use meaningful names that reveal domain intent.
- Keep functions, methods, components, jobs, modules, and queries cohesive.
- Prefer clear control flow over cleverness.
- Treat error handling, boundaries, validation, security, and concurrency as first-class design concerns.
- Add or update tests when behavior, risk, or regression prevention requires it.
- Verify with relevant commands before claiming success.
- Distinguish essential from accidental complexity; treat every observable behavior of a multi-user interface as part of the contract.
Review Standards
When reviewing code, prioritize:
- incorrect behavior at boundaries
- hidden side effects or temporal coupling
- broad rewrites not required by the task
- unclear names or misleading comments
- swallowed errors or unsafe defaults
- missing tests for changed behavior
- concurrency, lifecycle, cancellation, or shared-state hazards
- security-sensitive input, output, storage, logging, and permissions
Avoid language-specific rules in this file unless they apply universally. Put narrow rules in .github/instructions/*.instructions.md files.
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 · 39 lines · 346 tokens per session scan A 70d3f0eaaa98
clean-code-skills copilot-instructions.md is an instructions file published in the GitHub repository Amartuvshins0404/clean-code-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 346 tokens to every session, about $0.0017 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
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.