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/jnpiyush/agentx/csharpgit clone --depth 1 https://github.com/jnPiyush/AgentXWhat 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.00435 | $0.00435 |
| Opus 5 | $0.00217 | $0.00217 |
| Sonnet 5 | $0.00087 | $0.00087 |
| Haiku 4.5 | $0.00044 | $0.00044 |
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.
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
recordfor DTOs and immutable types - Enable nullable reference types (
<Nullable>enable</Nullable>) - PascalCase for classes/methods/properties, _camelCase for private fields
- Always use
Asyncsuffix for async methods - Use
ConfigureAwait(false)in library code - Never use
.Resultor.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
@paramsyntax -- 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
VerifyorFluentAssertionsfor readable assertions
Error Handling
- Catch specific exceptions (
InvalidOperationException,ArgumentNullException, etc.) - Re-throw with
throw;(notthrow ex;) to preserve stack trace - Use
ILogger<T>with structured logging and correlation IDs - Implement
IAsyncDisposablefor async resource cleanup
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.
- 2d ago First seen · 46 lines · 435 tokens per session scan A aeb899b7f4b5
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.
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.
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).
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.
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
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.
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.