More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    C and C++ Code Safety Check

    1

    Your agent runs a scanner on your .c, .h, .cpp, .cc, .hpp and Arduino .ino files and on CMakeLists.txt, *.cmake, Makefiles, meson.build and Visual Studio .vcxproj files.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    C and C++ Code Safety Check

    C and C++ Code Safety Check

    Example session with this skill installed

    Check this project with c-cpp-code-safety-check.

    • Read your context and instructions
    • Compiled the c and c++

    $ python3 scripts/check_cpp.py examples/risky
    BLOCK firmware/sensor/sensor.ino:9 C06 HARDCODED_CREDENTIAL
    WiFi.begin(ssid, "<redacted>");
    Why: A credential is written in the source: a password passed to an API that takes one (WiFi.begin, mysql_real_connect, CURLOPT_USERPWD, an ESP-IDF wifi_config password), a password in a connection string or in the user-info part of a URL, an Authorization or API-key header, a PEM private key, a token in a known format (AWS, GitHub, Slack, Stripe, Google), or a value with the shape of a generated key under a secret name. Everyone with the source can read it, and so can anyone who runs strings on the binary or dumps a device's firmware.
    Safer: Read secrets at run time from the environment, a config file outside the repository with tight permissions, the OS keychain or a secret manager; on devices use provisioning or a secure element. Change the secret that was committed: deleting it from the code does not remove it from history or from binaries already shipped.

    BLOCK src/config.h:5 C06 HARDCODED_CREDENTIAL
    BLOCK src/main.c:14 C02 SHELL_COMMAND_FROM_VARIABLE
    BLOCK src/main.c:19 C03 NON_LITERAL_FORMAT_STRING
    BLOCK src/main.c:31 C01 GETS_CALL
    BLOCK src/main.c:35 C04 SCANF_STRING_WITHOUT_WIDTH
    BLOCK src/update.c:25 C05 TLS_VERIFICATION_OFF
    BLOCK src/update.c:26 C06 HARDCODED_CREDENTIAL
    REVIEW CMakeLists.txt:8 C14 HARDENING_FLAG_DISABLED
    REVIEW CMakeLists.txt:14 C18 FETCHED_DEPENDENCY_NOT_PINNED
    REVIEW src/auth.cpp:13 C12 WEAK_RANDOM_FOR_SECRET
    REVIEW src/auth.cpp:19 C15 FAST_HASH_FOR_PASSWORD
    REVIEW src/auth.cpp:24 C19 SECRET_NAMED_LITERAL
    REVIEW src/auth.cpp:25 C17 SECRET_WIPE_MAY_BE_REMOVED
    REVIEW src/main.c:36 C11 UNBOUNDED_STRING_COPY
    REVIEW src/main.c:39 C13 PREDICTABLE_TEMP_FILE_NAME
    REVIEW src/tls_client.c:6 C16 TLS_CHECK_INCOMPLETE
    REVIEW src/update.c:14 C20 SHELL_COMMAND_NOT_TRACED

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

    A firmware updater that sets CURLOPT_SSL_VERIFYPEER to 0 "because the device clock is wrong" installs whatever a hostile Wi-Fi network sends it. A ping helper that builds "ping -c 1 %s" with snprintf and hands it to system() runs any command typed after a semicolon, and a log call written as printf(msg) lets %n in that message write to memory. This skill finds those and the other C and C++ mistakes below before the code ships, and tells you how to fix each one.

    Your agent runs a scanner on your .c, .h, .cpp, .cc, .hpp and Arduino .ino files and on CMakeLists.txt, *.cmake, Makefiles, meson.build and Visual Studio .vcxproj files. It understands comments, string and character literals (including raw strings and digit separators), skips #if 0 blocks and vendored or package-manager folders such as third_party, .pio and managed_components, tells calls apart from declarations and member calls, and follows a command through local variables, so char cmd[] = "clear"; system(cmd); is not reported while a host name formatted into "ping -c 1 %s" is. For TLS it checks whether the code is a client or a server, so SSL_VERIFY_NONE in a server that does not ask for client certificates is not reported, and a switch-off behind an insecure or debug setting is a review item, not a blocker. Credentials are a blocker only when their meaning is certain (a password passed to WiFi.begin or CURLOPT_USERPWD, a connection string, a private key, a known key format, a generated-looking key); a literal that only its name marks as secret is a review item. It never compiles or runs 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

    • C01: calls of gets() (also std::gets and _getws)
    • C02: system(), popen(), their Windows forms and execl("/bin/sh", "sh", "-c", cmd) with a command built at run time: a value formatted or joined into a fixed command, or a command from argv, getenv or a read
    • C03: printf-family calls (printf, fprintf, snprintf, syslog, dprintf and others) whose format is not a literal and that have no other arguments
    • C04: scanf and fscanf reading %s or %[ with no field width
    • C05: TLS checks turned off in client code: libcurl VERIFYPEER or VERIFYHOST set to 0, SSL_VERIFY_NONE, ssl::verify_none, QSslSocket::VerifyNone or MBEDTLS_SSL_VERIFY_NONE in a client, verify callbacks that always accept, cpp-httplib and cpr switches, ESP32 setInsecure() and ESP-IDF skip_cert_common_name_check, WinHTTP and SChannel ignore flags, CMake TLS_VERIFY OFF
    • C06: credentials whose meaning is certain: passwords passed to WiFi.begin, mysql_real_connect, CURLOPT_USERPWD or an ESP-IDF wifi_config, connection strings, passwords in the user-info part of URLs, Authorization headers, PEM private keys, known key formats, and generated-looking keys under a secret name

    REVIEW

    • C11: strcpy, strcat, sprintf with %s, vsprintf and sscanf %s copying a string of unknown length into a fixed buffer
    • C12: rand(), random(), drand48() or std::mt19937 used to make tokens, session ids, keys, salts, nonces or IVs
    • C13: mktemp, tmpnam and tempnam
    • C14: build files that turn off hardening: -fno-stack-protector, -z execstack, -z norelro, -D_FORTIFY_SOURCE=0, -no-pie, -Wno-format-security, MSVC /GS-, /DYNAMICBASE:NO and the matching Visual Studio settings
    • C15: passwords hashed with MD5, SHA-1 or SHA-2 instead of a password hash
    • C16: incomplete TLS checks: OpenSSL clients that never turn on SSL_VERIFY_PEER or never check the host name, Boost.Asio clients without verify_peer or host name verification, Qt ignoreSslErrors() with no list, and switch-offs behind a setting
    • C17: memset, bzero or ZeroMemory clearing a password or crypto-key buffer, which the compiler may remove
    • C18: CMake FetchContent, ExternalProject and CPM dependencies on a branch or with no tag, URL downloads without URL_HASH, and file(DOWNLOAD) without EXPECTED_HASH
    • C19: literals that only a password, token or key name marks as secret, password comparisons with a fixed value, and credentials in a git-ignored secrets header such as arduino_secrets.h
    • C20: system(), popen() or sh -c with a command from a parameter, member or function result the scanner cannot follow

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason, safer approach and documentation link (SEI CERT C, OpenSSF, libcurl, OpenSSL, OWASP, CMake) for each rule
    • A risky and a safe example project, and the real report the scanner produces on the risky one

    Limits It reads each file as text, without running the preprocessor: macros are not expanded, every #if branch except #if 0 is read, and buffer sizes and values built in other functions or files are not known; commands are followed only through local and file-level variables. Compiler flags set outside the scanned files (CI scripts, CMake presets, environment variables) are not seen. Objective-C and CUDA files are not read. curl's own https.c example is reported for review, because its SKIP_PEER_VERIFICATION build switch can turn the checks off. NOT FLAGGED is not a guarantee; keep compiler warnings, sanitizers and a full static analyzer in your build as well.

    Static check of C and C++ source and build file text. No preprocessing, type information or data flow across files; compiler flags set outside the scanned files 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 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 4 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 project includes clearly fake, inert passwords and tokens (NOTREAL-..., notreal-...) for the scanner to find. It is never compiled or run.

    Listed4 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 C and C++ sources and build files as text. It never runs a compiler, CMake or your program, and secrets it finds in the source are masked.

    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 C and C++ project, and the real report the scanner prints on the risky example.

    New in Security