More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Rust Cargo Safety Check

    1

    This skill finds those and eight other Cargo and Rust mistakes before you build or release, 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
    Rust Cargo Safety Check

    Rust Cargo Safety Check

    Example session with this skill installed

    Check this project with rust-cargo-safety-check.

    • Read your context and instructions
    • Compiled the rust cargo safety

    $ python3 scripts/check_cargo.py examples/risky
    BLOCK .cargo/config.toml:2 C02 INSECURE_CRATE_SOURCE
    index = "sparse+http://crates.example.internal/index/"
    Why: A git dependency, registry index, source replacement or Cargo.lock source uses http:// or git://. These are not encrypted or authenticated, so anyone on the network path (public Wi-Fi, a proxy, a compromised router) can swap the crate code that Cargo downloads and compiles.
    Safer: Use https:// (sparse+https:// for registry indexes) or ssh://, then run cargo update -p for the affected crates so Cargo.lock records the new source.

    BLOCK .cargo/config.toml:3 C03 SECRET_IN_CARGO_FILE
    BLOCK .cargo/config.toml:6 C03 SECRET_IN_CARGO_FILE
    BLOCK Cargo.toml:15 C02 INSECURE_CRATE_SOURCE
    REVIEW Cargo.toml:1 C13 NO_LOCK_FILE
    REVIEW Cargo.toml:13 C17 PATH_OUTSIDE_REPOSITORY
    REVIEW Cargo.toml:14 C01 GIT_DEPENDENCY_NOT_PINNED
    REVIEW Cargo.toml:16 C11 WILDCARD_VERSION
    REVIEW Cargo.toml:17 C11 WILDCARD_VERSION
    REVIEW Cargo.toml:20 C15 BUILD_SCRIPT_USES_NETWORK
    REVIEW Cargo.toml:23 C01 GIT_DEPENDENCY_NOT_PINNED
    REVIEW Cargo.toml:23 C12 DEPENDENCY_OVERRIDE
    REVIEW build.rs:6 C14 BUILD_SCRIPT_RUNS_COMMANDS
    REVIEW build.rs:11 C15 BUILD_SCRIPT_USES_NETWORK
    REVIEW src/ffi.rs:14 C16 UNSAFE_CODE

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 5 files, 5 with Cargo or Rust 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

    billing-core = { git = "...", branch = "main" } means the next cargo update builds whatever was last pushed to main, and one token = "..." line in .cargo/config.toml hands your registry token to everyone who can read the repository. This skill finds those and eight other Cargo and Rust mistakes before you build or release, and tells you how to fix each one.

    Your agent runs a scanner on your project: Cargo.toml (every dependency table, target-specific tables, [workspace.dependencies], [patch] and [replace]), Cargo.lock, .cargo/config.toml and the older .cargo/config, credentials files, build.rs and every .rs file. It parses TOML with line numbers and reads Rust with a small lexer that knows nested comments, raw strings, char literals and lifetimes, so text in strings and comments never counts as code. It follows Cargo's own rules (workspace = true inheritance, Cargo.lock at the workspace root, config paths relative to the folder that holds .cargo) and reads .gitignore to tell whether Cargo.lock and credentials files are committed. It never runs Cargo, a build script or your code. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.

    What it checks

    BLOCK

    • C02: git dependencies, registry indexes, source replacements and Cargo.lock sources over http:// or git://
    • C03: registry tokens in .cargo/config.toml or a credentials file in the project, passwords and tokens in URLs, and secrets in [env] or [package.metadata]

    REVIEW

    • C01: git dependencies and patches with no rev or tag, so they follow a branch
    • C11: "*" versions, >= requirements with no upper bound, and dependencies with no version at all
    • C12: [patch], [replace] and paths overrides
    • C13: binaries with no committed Cargo.lock (missing, or listed in .gitignore)
    • C14: build.rs that starts other programs
    • C15: build scripts that download: HTTP client crates in [build-dependencies], reqwest or ureq in build.rs, curl, wget or git clone
    • C16: unsafe blocks, unsafe fn and unsafe impl, counted and listed per file
    • C17: path dependencies, patches and vendored sources outside the repository

    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 project, and the real report the scanner produces on the risky one

    Limits It reads your project's files as written. Your user-level ~/.cargo/config.toml, CARGO_* environment variables, the build scripts and code of your dependencies, procedural macros, and known vulnerabilities in crate versions (cargo audit covers those) are not checked. NOT FLAGGED is not a guarantee.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.

    Static check of Cargo files and Rust source text. User-level Cargo config, environment variables, --config flags, dependencies' own build scripts, procedural macros and crate vulnerability advisories are not checked. 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 buying a skill.

    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

    Software
    Git

    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 project includes clearly fake, inert tokens (NOTREAL, not-a-real-...) for the scanner to find. It is never built or run.

    Listed5 days ago
    Updated4 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 Cargo.toml, Cargo.lock, build.rs and config as text. It never runs cargo or compiles code.

    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 Rust crate, and the real report the scanner prints on the risky example.

    New in Security