iforgeai coding-standards-dotnet.instructions.md

Project-specific rules for writing, reviewing, and changing C# and .NET backend code, including layer structure and error-handling conventions.

In plain words
What is it for?
Use it to document or apply conventions for controllers, services, data access, domain code, exceptions, and other .NET project rules.
Why use it?
It gives the team a shared way to organize backend code and handle failures consistently.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/nelson820125/iforgeai/coding-standards-dotnet
Clone the repo
git clone --depth 1 https://github.com/nelson820125/iforgeai

Made for: GitHub Copilot.

Per session 216 This file is loaded in full into every session.
When invoked 216 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00216 $0.00216
Opus 5 $0.00108 $0.00108
Sonnet 5 $0.00043 $0.00043
Haiku 4.5 $0.00022 $0.00022

Measured 3d ago against content hash 4d007fc9419e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

iforgeai coding-standards-dotnet.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 3d 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.

project-template/.github/instructions/coding-standards-dotnet.instructions.md · 37 lines

What it actually says

.NET / C# Coding Standards (Project Overrides)

This file overrides portions of the global standard that need project-specific adjustments. Global standard: user-level coding-standards-dotnet.instructions.md

Project Layer Structure

Describe this project's layer structure so all engineers share a common understanding.

Example:

Controllers/    -> HTTP layer - routing and parameter binding only
Services/       -> Business logic layer
Repositories/  -> Data access layer (EF Core / Dapper)
Domain/         -> Domain entities and value objects

(fill in)

Error Handling Convention

Describe this project's error handling strategy, e.g.: Result Pattern / global exception middleware / custom exception types.

(fill in)

Project-Specific Rules

Append project-specific coding conventions below. Format: - {rule description}

(fill in)

Changes

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.

  1. 3d ago First seen · 37 lines · 216 tokens per session scan A 4d007fc9419e

Subscribe to this mod's changes

iforgeai coding-standards-dotnet.instructions.md is an instructions file published in the GitHub repository nelson820125/iforgeai (8 stars, last pushed 4mo ago), licensed MIT. It adds 216 tokens to every session, about $0.0011 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.

Related

Other instructions, from other repositories

maui integration-tests.instructions.md

Guidance for GitHub Copilot when working with .NET MAUI integration tests.

dotnet/maui · 2,481 tokens

maui handler-patterns.instructions.md

Instructions for dotnet/maui, covering handler mapper and property patterns, property update flow, lifecycle management, null safety in callbacks and native defaults preservation.

dotnet/maui · 464 tokens

maui performance-hotpaths.instructions.md

Instructions for dotnet/maui, covering performance-critical path rules, hot paths in maui, allocation avoidance, caching and invalidation and collection iteration.

dotnet/maui · 441 tokens

cryptoexchange-net

Use CryptoExchange.Net abstractions when generating C#/.NET code that needs to work across MULTIPLE cryptocurrency exchanges (Binance + Bybit + OKX + Kraken + Coinbase + ...) — for arbitrage, best-execution routing, multi-exchange portfolio dashboards, exchange-agnostic trading bots, or comparison tools. Triggers on…

JKorf/CryptoExchange.Net · 2,291 tokens

kraken-net

Use Kraken.Net when generating C#/.NET code that interacts with the Kraken cryptocurrency exchange, including Spot REST, Spot WebSocket v2, Futures REST, Futures WebSocket, account data, market data, order placement, Kraken Earn, local order books, dependency injection, or CryptoExchange.Net SharedApis. Triggers on…

JKorf/Kraken.Net · 1,872 tokens

Kucoin.Net copilot-instructions.md

Instructions for JKorf/Kucoin.Net, covering copilot instructions for kucoin.net, use kucoin.net, not raw http, client setup, result handling and api structure.

JKorf/Kucoin.Net · 849 tokens