Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/nikiforovall/github-copilot-rules/coding-guidelinesgit clone --depth 1 https://github.com/NikiforovAll/github-copilot-rulesWhat 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 | $0.00716 | $0.00716 |
| Opus 5 | $0.00358 | $0.00358 |
| Sonnet 5 | $0.00143 | $0.00143 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
github-copilot-rules coding-guidelines.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 yesterday.
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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role Definition:
- C# Language Expert
- Software Architect
- Code Quality Specialist
General:
Description: C# code should be written to maximize readability, maintainability, and correctness while minimizing complexity and coupling. Prefer functional patterns and immutable data where appropriate, and keep abstractions simple and focused.
Requirements:
- Write clear, self-documenting code
- Keep abstractions simple and focused
- Minimize dependencies and coupling
- Use modern C# features appropriately
Code Organization:
- Use meaningful names:
// Good: Clear intent public async Task<Result<Order>> ProcessOrderAsync(OrderRequest request, CancellationToken cancellationToken) // Avoid: Unclear abbreviations public async Task<Result<T>> ProcAsync<T>(ReqDto r, CancellationToken ct) - Separate state from behavior:
// Good: Behavior separate from state public sealed record Order(OrderId Id, List<OrderLine> Lines); public static class OrderOperations { public static decimal CalculateTotal(Order order) => order.Lines.Sum(line => line.Price * line.Quantity); } - Prefer pure methods:
// Good: Pure function public static decimal CalculateTotalPrice( IEnumerable<OrderLine> lines, decimal taxRate) => lines.Sum(line => line.Price * line.Quantity) * (1 + taxRate); // Avoid: Method with side effects public void CalculateAndUpdateTotalPrice() { this.Total = this.Lines.Sum(l => l.Price * l.Quantity); this.UpdateDatabase(); } - Use extension methods appropriately:
// Good: Extension method for domain-specific operations public static class OrderExtensions { public static bool CanBeFulfilled(this Order order, Inventory inventory) => order.Lines.All(line => inventory.HasStock(line.ProductId, line.Quantity)); } - Design for testability:
// Good: Easy to test pure functions public static class PriceCalculator { public static decimal CalculateDiscount( decimal price, int quantity, CustomerTier tier) => // Pure calculation } // Avoid: Hard to test due to hidden dependencies public decimal CalculateDiscount() { var user = _userService.GetCurrentUser(); // Hidden dependency var settings = _configService.GetSettings(); // Hidden dependency // Calculation }
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.
- yesterday First seen · 117 lines · 716 tokens per session scan A 5e7cdf48f462
github-copilot-rules coding-guidelines.instructions.md is an instructions file published in the GitHub repository NikiforovAll/github-copilot-rules (131 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 716 tokens to every session, about $0.0036 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
github-copilot-starter accessibility.instructions.md
Guidelines for improving the accessibility of a website to ensure it is usable for everyone, including people with disabilities.
github-copilot-starter security.instructions.md
Comprehensive secure coding instructions for all languages and frameworks, based on OWASP Top 10 and industry best practices.
github-copilot-starter copilot-instructions.md
Copilot instructions for devbyray/github-copilot-starter, covering 🧱 project overview, 🎯 purpose, 🔧 general guidelines, 📚 guidelines structure and 🎯 agent skills (dynamic loading).
github-copilot-starter coding.instructions.md
Coding standards and conventions for the project, including JavaScript/TypeScript, CSS, and component structure.
github-copilot-starter ui-guidelines.instructions.md
UI guidelines for consistent, accessible, and maintainable user interfaces.
github-copilot-starter config.instructions.md
Instructions for configuration files used in the project, including .editorconfig, prettier, and eslint.