More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    NuGet Config Check

    1

    This skill finds those and nine other NuGet mistakes before you restore or commit, and tells you how to fix each one.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    NuGet Config Check

    NuGet Config Check

    Example session with this skill installed

    Check this project with nuget-config-check.

    • Read your context and instructions
    • Compiled the nuget config check

    $ python3 scripts/check_nuget.py examples/risky
    BLOCK NuGet.Config:6 N01 HTTP_PACKAGE_SOURCE

        <add key="contoso-build" value="http://nuget.build.contoso.example/v3/index.json" allowInsecureConnections="true" />
    
    Why: A package, audit or push source uses plain http:// (in NuGet.config, or in RestoreSources in an MSBuild file). Anyone on the network path (shared Wi-Fi, a proxy, a compromised router) can swap the packages your build downloads and read the feed credentials or API key NuGet sends. NuGet warns about http sources (NU1803), and newer .NET SDKs fail restore with NU1302 unless allowInsecureConnections is set, which only silences the check.
    Safer: Use the feed's https:// address (nuget.org, Azure Artifacts and GitHub Packages serve only https). Do not add allowInsecureConnections to make an http feed work; put the feed behind TLS instead.
    

    BLOCK NuGet.Config:7 N03 TLS_CHECK_DISABLED
    BLOCK NuGet.Config:14 N02 PASSWORD_IN_NUGET_CONFIG
    REVIEW Directory.Build.props:7 N17 VULNERABILITY_AUDIT_OFF
    REVIEW NuGet.Config:4 N13 SOURCES_NOT_MAPPED
    REVIEW NuGet.Config:8 N15 INSECURE_CONNECTIONS_ALLOWED
    REVIEW NuGet.Config:18 N16 STORED_CREDENTIAL_IN_PROJECT
    REVIEW NuGet.Config:24 N18 UNTRUSTED_SIGNER_ROOT
    REVIEW src/OrderApi/OrderApi.csproj:1 N14 NO_LOCK_FILE
    REVIEW src/OrderApi/OrderApi.csproj:9 N11 FLOATING_VERSION
    REVIEW src/OrderApi/OrderApi.csproj:10 N12 PRERELEASE_PACKAGE

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 3 files, 3 with NuGet content.
    This is a static check of file text. NOT FLAGGED is not a guarantee.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    ClearTextPassword value="ghp_..." in a committed NuGet.config gives your feed token to everyone who can read the repository, and a private feed added next to nuget.org without packageSourceMapping lets a public package with your internal package's name be restored instead. This skill finds those and nine other NuGet mistakes before you restore or commit, and tells you how to fix each one.

    Your agent runs a scanner on your NuGet.config files, project files (.csproj, .fsproj, .vbproj, SDK-style and old-style), Directory.Packages.props (Central Package Management), Directory.Build.props and packages.lock.json. It parses the XML and points at the exact line, understands NuGet's %VAR% references, MSBuild $(Property) values, cleared and disabled sources and NuGet's version range notation, and tells application projects from libraries and test projects for the lock-file rule. It never runs dotnet, restores packages or contacts a feed. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.

    What it checks

    BLOCK

    • N01: package, audit or push sources over plain http://, also when allowInsecureConnections is set
    • N02: feed passwords, tokens and API keys in plain text (ClearTextPassword, unencrypted Password or apikeys values, user:password in a URL)
    • N03: disableTLSCertificateValidation on a package source

    REVIEW

    • N11: floating versions (8.*, *) and version ranges without an inclusive lower bound
    • N12: prerelease packages (-beta, -preview, -rc)
    • N13: several package sources without packageSourceMapping, counting nuget.org when the source list is not cleared
    • N14: application projects without packages.lock.json, and lock files turned on but not committed
    • N15: allowInsecureConnections on an https source
    • N16: encrypted passwords and API keys committed in a project NuGet.config
    • N17: NuGetAudit turned off, or vulnerability warnings NU1901-NU1904 hidden with NoWarn
    • N18: trusted signers with allowUntrustedRoot

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason and safer approach for each rule
    • A risky and a safe example .NET solution (NuGet.config, Directory.Build.props, Central Package Management, an ASP.NET Core project and its lock file), and the real report the scanner produces on the risky one

    Limits It reads each file as written: settings merged from user-level and machine-wide NuGet configs, command-line options, environment variables, other imported .props and .targets files and MSBuild conditions are not evaluated, and packages.config and .nuspec files are not checked. It does not look up packages, so known vulnerabilities and package names taken on nuget.org are not checked. NOT FLAGGED is not a guarantee.

    Static check of NuGet and MSBuild XML. User-level and machine-wide NuGet configs are checked only when you pass their path, and http:// to localhost is not flagged. NOT FLAGGED is not a guarantee.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    Permissions

    Terminal / Shell
    Read Files

    Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example files include a clearly fake, inert feed password (not-a-real-...), a made-up encrypted value (NOTREAL...) and made-up feed hosts for the scanner to find. Nothing in them is restored or contacted.

    Listed5 days ago

    What's inside

    Frequently Asked Questions

    No. The script reads local files only and makes no network calls.

    No. It only reports. Your agent changes files only if you ask it to.

    Any agent that supports SKILL.md skills and can run a terminal command, such as Claude Code. It needs Python 3.9 or newer and nothing else.

    No. It reads NuGet.config and project files as text. It never runs dotnet or contacts a feed.

    BLOCK: fix it before you ship. REVIEW: check it before release. NOT FLAGGED: no rule matched. It is a static check, so NOT FLAGGED is not a guarantee.

    The scanner, a rules guide with the reason and safer approach for every rule, a risky and a safe example .NET project, and the real report the scanner prints on the risky example.

    New in Security