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 skills/stefanthecode/dotnet-ai-toolkit/serilog-logging-setupnpx skills add StefanTheCode/dotnet-ai-toolkit --skill serilog-logging-setupgit clone --depth 1 https://github.com/StefanTheCode/dotnet-ai-toolkitWhat 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.00112 | $0.00721 |
| Opus 5 | $0.00056 | $0.00360 |
| Sonnet 5 | $0.00022 | $0.00144 |
| Haiku 4.5 | $0.00011 | $0.00072 |
Grade A, and why
serilog-logging-setup 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 3d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Serilog Structured Logging Setup
Wire up Serilog in ASP.NET Core for structured (JSON) logs with enrichers, request logging, sensible levels, and sinks — correlated with your traces.
Input — point it at your project
Works on a target: a project or GitHub URL. Inspect current logging: grep -rn "UseSerilog\|ILogger\|Log.Logger\|AddSerilog" --include=*.cs <target>. If OTel is present, wire log/trace correlation.
Packages + wiring
dotnet add package Serilog.AspNetCore
dotnet add package Serilog.Sinks.Seq # or Console/Elastic/etc.
builder.Host.UseSerilog((ctx, services, lc) => lc
.ReadFrom.Configuration(ctx.Configuration)
.ReadFrom.Services(services)
.Enrich.FromLogContext()
.Enrich.WithMachineName()
.Enrich.WithProperty("service", "orders")
.WriteTo.Console(new RenderedCompactJsonFormatter()) // structured JSON
.WriteTo.Seq(ctx.Configuration["Seq:Url"]!));
app.UseSerilogRequestLogging(); // one tidy log line per request instead of the default noise
Structured logging done right
// GOOD: message template + properties (queryable)
logger.LogInformation("Order {OrderId} placed by {CustomerId} for {Total}", id, customerId, total);
// BAD: interpolated string (loses structure)
logger.LogInformation($"Order {id} placed");
What to set
- Levels —
Informationdefault,Warningfor noisy frameworks,Debugonly in dev. Configure viaappsettings. - Enrichers — machine, environment, and a correlation/trace id (see
correlation-id-middleware). - Request logging —
UseSerilogRequestLoggingfor one structured line per request with status + duration. - Trace correlation — include
TraceId/SpanIdso logs link to traces.
Principles
- Message templates, not interpolation — structure is the whole point of structured logging.
- Don't log secrets/PII. Be deliberate about what goes into properties.
- Log at the right level;
Informationfor business events,Errorwith the exception object (notex.Message). - One sink for local (console JSON), one for aggregation (Seq/Elastic/Loki).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 55 lines · 112 tokens per session scan A acc5d5606d27
serilog-logging-setup is a skill published in the GitHub repository StefanTheCode/dotnet-ai-toolkit (19 stars, last pushed 24d ago), licensed MIT. It adds 112 tokens to every session and 721 once invoked, about $0.0006 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 skills, from other repositories
github-ci-fix-onboarding
Onboards and troubleshoots GitHub PR CI fixing by configuring GitHub CLI authentication, a non-exposed GitHub token, a matching local checkout, and a ready coding agent before running fixgithubprci. Use for first-time setup, failed prerequisites, demos, or action-shaped requests to onboard the user onto the local…
greptimedb-fuzz-ci-failure-investigation
Investigate a failed GreptimeDB fuzz CI target link by downloading GitHub Actions job logs plus fuzz artifacts such as kind logs, monitor dumps, and CSV dumps, then correlate the failure with local GreptimeDB source code. Use when the user provides a failed fuzz CI target/job URL or asks to diagnose GreptimeDB fuzz CI…
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
yandex-cloud
Read Yandex Cloud through its REST API. Applies to any question about VMs, metrics, logs, audit events, Kubernetes, managed databases, serverless, networking or any other Yandex Cloud resource. Never shell out to the yc CLI — it is not how this agent reaches Yandex Cloud and is usually not installed.
morning-report
Weather + news morning briefing: fetch live weather and headlines, compose a plain-text briefing, deliver it. Multi-step; load before acting.
github-security-fix
Remediate GitHub security / Dependabot / CodeQL / code-quality alerts via fixgithubsecurityalert.