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/aaronontheweb/dotnet-cursor-rules/nuget-package-publishinggit clone --depth 1 https://github.com/Aaronontheweb/dotnet-cursor-rulesWrote 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/aaronontheweb/dotnet-cursor-rules/nuget-package-publishing)<a href="https://agentmods.dev/rules/aaronontheweb/dotnet-cursor-rules/nuget-package-publishing"><img src="https://agentmods.dev/badge/rules/aaronontheweb/dotnet-cursor-rules/nuget-package-publishing.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 | $0.00000 | $0.04599 |
| Opus 5 | $0.00000 | $0.02299 |
| Sonnet 5 | $0.00000 | $0.00920 |
| Haiku 4.5 | $0.00000 | $0.00460 |
Grade A, and why
nuget-package-publishing 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 — 712 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NuGet Package Publishing Best Practices
This document provides comprehensive guidance for publishing high-quality NuGet packages that follow industry best practices.
Table of Contents
- License Configuration
- Package Documentation
- Metadata Organization
- Source Debugging Support
- Package Dependencies
- Versioning
- Build and Pack Commands
- Quality Checks
License Configuration
Use License Expressions
Always use SPDX license expressions instead of deprecated license URLs or embedding license files in your package.
✅ DO: Use license expression
<PropertyGroup>
<PackageLicenseExpression>MIT</PackageLicenseExpression>
</PropertyGroup>
❌ DON'T: Use deprecated licenseUrl
<PropertyGroup>
<PackageLicenseUrl>https://licenses.nuget.org/MIT</PackageLicenseUrl>
</PropertyGroup>
Common License Expression Examples
MIT License
<PropertyGroup>
<PackageLicenseExpression>MIT</PackageLicenseExpression>
</PropertyGroup>
Apache 2.0 License
<PropertyGroup>
<PackageLicenseExpression>Apache-2.0</PackageLicenseExpression>
</PropertyGroup>
BSD 3-Clause License
<PropertyGroup>
<PackageLicenseExpression>BSD-3-Clause</PackageLicenseExpression>
</PropertyGroup>
GPL v3 License
<PropertyGroup>
<PackageLicenseExpression>GPL-3.0-only</PackageLicenseExpression>
</PropertyGroup>
Multiple Licenses (OR)
<PropertyGroup>
<PackageLicenseExpression>MIT OR Apache-2.0</PackageLicenseExpression>
</PropertyGroup>
Package Documentation
Include README.md
Always include a README.md file in your package to provide clear documentation for users.
✅ DO: Include README with proper configuration
<PropertyGroup>
<PackageReadmeFile>README.md</PackageReadmeFile>
</PropertyGroup>
<ItemGroup>
<None Include="README.md" Pack="true" PackagePath="/" />
</ItemGroup>
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 · 712 lines · 4,599 tokens per session scan A 2a096f467d3a
nuget-package-publishing is a cursor rule published in the GitHub repository Aaronontheweb/dotnet-cursor-rules (134 stars, last pushed 1y ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,599 tokens. 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
refactoring
Refactoring: systematic approach, extract/inline, guard clauses, early returns.
java
Modern Java: records, sealed classes, streams, virtual threads.
javascript
Modern JavaScript: ES2023+, async patterns, common traps.
accessibility
Accessibility: semantic HTML, ARIA, keyboard navigation, testing.
supabase
Supabase: RLS, edge functions, realtime.
claude-md
CLAUDE.md: structuring project context for Claude Code.