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.
git clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/rules/jnpiyush/agentx/csharp)<a href="https://agentmods.dev/rules/jnpiyush/agentx/csharp"><img src="https://agentmods.dev/badge/rules/jnpiyush/agentx/csharp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/jnpiyush/agentx/csharp"><img src="https://agentmods.dev/badge/rules/jnpiyush/agentx/csharp.svg" alt="Reviewed on agentmods" width="80" 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.00152 | $0.00152 |
| Opus 5.5 | $0.00061 | $0.00061 |
| Sonnet 5.5 | $0.00030 | $0.00030 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
csharp 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 7d 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 (Frontier)
Canonical: .github/instructions/csharp.instructions.md and
.github/skills/languages/csharp/SKILL.md -- read through
pwsh -NoProfile -File .frontier/runtime/frontier.ps1 cursor read <canonical-path>.
- Nullable reference types enabled; async/await end to end (no
.Result). - Dependency injection; EF Core with parameterized queries only.
- XML docs on public APIs; xUnit tests; catch specific exceptions.
- Secrets via configuration/Key Vault, never hardcoded.
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.
- 7d ago Changed · +1 lines · +21 tokens per session fbbe3b486b85
- 1mo ago Changed e56eda267e8a
- 1mo ago First seen · 16 lines · 131 tokens per session scan A be12c47e1ba5
csharp is a cursor rule published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 152 tokens to every session, about $0.0006 per session on Opus 5.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 cursor rules, from other repositories
roslyn-mcp-dev-conventions
Conventions when editing Tools and Services in this repo.
dotnet-testing
.NET-specific testing standards for ASP.NET Core applications. Covers test naming, project structure, unit and integration testing patterns, builders, Testcontainers, and WebApplicationFactory. Complements engineering-principles.mdc and dotnet-architecture.mdc.
mockito
This guide provides definitive best practices for writing robust, maintainable, and readable unit tests using Mockito with JUnit 5, focusing on modern patterns and common pitfalls.
python-general-coding-standards
A set of general standards for Python projects, including type hints, input checking, code style, security, web requests, background work, and tests. It also covers FastAPI-specific tasks such as CORS and authentication.
mocking-dependencies-in-tests
Cursor rule "mocking-dependencies-in-tests" from PaulJPhilp/EffectPatterns, covering mocking dependencies in tests and example.
roslyn-mcp-tools
MCP tool mapping — skeleton vs decompile vs symbols vs build.