AgentX csharp.instructions.md

Coding rules for C# and .NET production code, including naming, asynchronous code, security, database queries, and tests. They load automatically when editing C# files.

In plain words
What is it for?
Use them when writing or reviewing C# applications, .NET libraries, web endpoints, database access, and xUnit tests.
Why use it?
They give an agent consistent project standards and guard against common security, reliability, and testing mistakes.

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/jnpiyush/agentx/csharp
Clone the repo
git clone --depth 1 https://github.com/jnPiyush/AgentX

Made for: GitHub Copilot.

Per session 435 This file is loaded in full into every session.
When invoked 435 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.00435 $0.00435
Opus 5 $0.00217 $0.00217
Sonnet 5 $0.00087 $0.00087
Haiku 4.5 $0.00044 $0.00044

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

Security

Grade A, and why

AgentX csharp.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 2d 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.

.github/instructions/csharp.instructions.md · 46 lines

What it actually says

C# / .NET Instructions

Auto-loads when editing C# files. For comprehensive standards, load the skill.

Skill: .github/skills/languages/csharp/SKILL.md

Key Rules

  • Use file-scoped namespaces
  • Use primary constructors where appropriate (.NET 8+)
  • Prefer record for DTOs and immutable types
  • Enable nullable reference types (<Nullable>enable</Nullable>)
  • PascalCase for classes/methods/properties, _camelCase for private fields
  • Always use Async suffix for async methods
  • Use ConfigureAwait(false) in library code
  • Never use .Result or .Wait() -- always await
  • Catch specific exceptions, re-throw with throw;
  • xUnit for tests, Arrange-Act-Assert pattern
  • Name tests: MethodName_Scenario_ExpectedResult

Critical Rules (Embedded -- Always Active)

Security

  • Validate/sanitize ALL inputs at controller/endpoint boundaries
  • Use EF Core parameterized queries or Dapper @param syntax -- NEVER string concatenation
  • Secrets via IConfiguration + Azure Key Vault -- NEVER hardcode
  • Use [Authorize] attribute on all non-public endpoints

Testing

  • 80%+ code coverage required
  • Pyramid: 70% unit (xUnit), 20% integration (WebApplicationFactory), 10% e2e
  • AAA pattern (Arrange-Act-Assert) in every test
  • Use Verify or FluentAssertions for readable assertions

Error Handling

  • Catch specific exceptions (InvalidOperationException, ArgumentNullException, etc.)
  • Re-throw with throw; (not throw ex;) to preserve stack trace
  • Use ILogger<T> with structured logging and correlation IDs
  • Implement IAsyncDisposable for async resource cleanup
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. 2d ago First seen · 46 lines · 435 tokens per session scan A aeb899b7f4b5

Subscribe to this mod's changes

AgentX csharp.instructions.md is an instructions file published in the GitHub repository jnPiyush/AgentX (15 stars, last pushed 5d ago), licensed Apache-2.0. It adds 435 tokens to every session, about $0.0022 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.

Related

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.

openai/codex · 5,182 tokens

buildNext

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).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

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).

microsoft/vscode · 5,001 tokens

spec-kit 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.

github/spec-kit · 7,040 tokens

langchain 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.

langchain-ai/langchain · 4,345 tokens