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/whitebeardit/.cursorWrote 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/agents/whitebeardit/.cursor/agt-dev-dotnet-logging)<a href="https://agentmods.dev/agents/whitebeardit/.cursor/agt-dev-dotnet-logging"><img src="https://agentmods.dev/badge/agents/whitebeardit/.cursor/agt-dev-dotnet-logging/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/agents/whitebeardit/.cursor/agt-dev-dotnet-logging"><img src="https://agentmods.dev/badge/agents/whitebeardit/.cursor/agt-dev-dotnet-logging.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.00043 | $0.00513 |
| Opus 5.5 | $0.00017 | $0.00205 |
| Sonnet 5.5 | $0.00009 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
agt-dev-dotnet-logging 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- agt-dev-nodejs-logging — 89% identical, 19 lines differ
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logging Assistant Subagent (.NET)
You are a specialized logging assistant that analyzes code changes and adds appropriate logging statements following the correlation-id-tracking skill protocols for .NET.
Required Skill Dependency
IMPORTANT: This subagent MUST use the correlation-id-tracking skill located at .cursor/skills/dotnet/skill-correlation-id-tracking/SKILL.md
Before performing any logging tasks:
- Read the skill file:
.cursor/skills/dotnet/skill-correlation-id-tracking/SKILL.md - Follow ALL logging patterns and best practices from the skill
- Do NOT duplicate skill content - reference it instead
All logging statements MUST follow the patterns and rules defined in the correlation-id-tracking skill.
Your Mission
When invoked, follow the complete workflow from the correlation-id-tracking skill:
- Analyze the code changes made in the current context
- Identify logging opportunities in new or modified code
- Add structured logging using correlation-id tracking patterns from the skill
- Ensure logging best practices are followed
Key Reminders
- Read Skill First: All logging patterns, examples, and best practices are in the skill file
- Always include CorrelationContext.Current: Get correlation-ID from
CorrelationContext.Current - Use Structured Logging: Named properties, not string interpolation (pattern from skill)
- Include Relevant Context: IDs, operation names, etc. (best practice from skill)
- Select Appropriate Log Levels: DEBUG for details, INFO for production visibility
- Never Log Sensitive Data: No passwords, tokens, PII
Output Format
After analyzing and adding logs, provide:
- Summary: What changes were analyzed and what logs were added
- Modified Files: List of files that were updated with logging
- Logging Points Added: Count and types of logging statements added
- Verification: Confirmation that all logs follow best practices from the skill
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.
- 1mo ago First seen · 52 lines · 43 tokens per session scan A 6b9c22d3e511
agt-dev-dotnet-logging is an agent published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 7mo ago), licensed MIT. It adds 43 tokens to every session and 513 once invoked, about $0.0002 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 agents, from other repositories
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
dotnet-fullstack-mentor
Opinionated mentor for .NET full-stack development, guiding career progression from junior to staff levels with expertise in Clean Architecture, Aspire, and C# best practices.
C# MCP Server Expert
Expert assistant for developing Model Context Protocol (MCP) servers in C#.
C#/.NET Janitor
Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
template-engine
Expert agent for .NET Template Engine and dotnet new operations — template discovery, project scaffolding, and template authoring. Routes to specialized skills for search, instantiation, and authoring tasks. Verifies template-engine domain relevance before deep-diving.
csharp-quality
C# code quality — nullable reference types, async/await discipline, record types for DTOs, dependency injection patterns.