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 rules/adonai-labs/agent-runway/dotnet-observabilitygit clone --depth 1 https://github.com/adonai-labs/agent-runwayWrote 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/adonai-labs/agent-runway/dotnet-observability)<a href="https://agentmods.dev/rules/adonai-labs/agent-runway/dotnet-observability"><img src="https://agentmods.dev/badge/rules/adonai-labs/agent-runway/dotnet-observability.svg" alt="Measured on agentmods" 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.01425 | $0.01425 |
| Opus 5 | $0.00713 | $0.00713 |
| Sonnet 5 | $0.00285 | $0.00285 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade A, and why
dotnet-observability 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Observability Standards
.NET-specific observability practices for ASP.NET Core APIs. For general observability principles, see engineering-principles.mdc. For strategy-level guidance, see dotnet-architecture.mdc.
Conflict resolution: Where this file provides .NET-specific guidance that differs from
engineering-architecture.mdc, this file takes precedence for.cs,.csproj,.json,.yaml, and.ymlfiles.
Structured logging
Use ILogger<T> with message templates; never use string interpolation in log messages — it destroys structured field indexing.
// Correct — fields are indexed and queryable
_logger.LogInformation("Order {OrderId} placed for customer {CustomerId}", order.Id, order.CustomerId);
// Incorrect — fields are lost; only raw string is stored
_logger.LogInformation($"Order {order.Id} placed for customer {order.CustomerId}");
- Log at
Informationfor significant state transitions (order placed, payment processed) - Log at
Warningfor recoverable business rule violations (retry exhausted, fallback used) - Log at
Errorfor unhandled exceptions and infrastructure failures; always include the exception object - Log at
Debugfor diagnostic detail; never log sensitive fields (PAN, passwords, tokens) at any level
// Error with exception — always pass exception as the last parameter
_logger.LogError(ex, "Failed to persist order {OrderId}", command.OrderId);
Correlation IDs
Propagate a correlation ID through every request. Accept from the X-Correlation-Id header if present; generate one if absent. Add to response headers and to the logging scope.
public class CorrelationIdMiddleware(RequestDelegate next)
{
private const string HeaderName = "X-Correlation-Id";
public async Task InvokeAsync(HttpContext context)
{
var correlationId = context.Request.Headers[HeaderName].FirstOrDefault()
?? Guid.NewGuid().ToString();
context.Response.Headers[HeaderName] = correlationId;
using (_logger.BeginScope(new Dictionary<string, object>
{ ["CorrelationId"] = correlationId }))
{
await next(context);
}
}
}
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.
- 5d ago First seen · 200 lines · 1,425 tokens per session scan A 8d7d050b7dff
dotnet-observability is a cursor rule published in the GitHub repository adonai-labs/agent-runway (2 stars, last pushed 15d ago), licensed MIT. It adds 1,425 tokens to every session, about $0.0071 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.
Other cursor rules, from other repositories
archgate-governance
Archgate ADR governance — enforces architecture decision records.
cursorrules
When the user asks you to generate diagrams, analyze code structure, or visualize architecture, follow this analysis pipeline. Use terminal commands (rg, find, cat) for all file operations.
arch4
Keep Arch4 architecture maps current.
cursorrules
You are working with a React Native (Expo) architecture reference project. Read the skill files before generating any code.
nativescript
NativeScript best practices and patterns for mobile applications.
python
Python best practices and patterns for modern software development with Flask and SQLite.