Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Semantic Entropy Credential Scanner

    1

    Perform deep forensic scans using Shannon entropy and semantic analysis to find obfuscated secrets and leaked keys.

    $15

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Semantic Entropy Credential Scanner

    Semantic Entropy Credential Scanner

    Example session with this skill installed

    Run a semantic entropy scan on the current repository to find any obfuscated keys or high-entropy tokens in the codebase.

    • Read your context and instructions
    • Compiled the semantic entropy credential

    I have completed the semantic and statistical entropy scan of the workspace. I analyzed 42 files, focusing on string literals and variable declarations.

    Credential Forensics Audit Report

    File PathVariable/ContextEntropy ScoreRisk LevelFinding Type
    src/auth/provider.tsconst _k = "S0m3R4nd0m..."7.82CRITICALHigh-entropy string literal
    config/settings.json"api_key": "base64:ZXhw..."6.94HIGHBase64 encoded payload
    scripts/deploy.shAUTH_TOKEN5.12MEDIUMSemantic match (Environment Var)
    .env.localSTRIPE_SK7.45CRITICALHigh-entropy secret
    tests/mocks.jstest_uuid3.21LOWFalse Positive (Standard UUID)

    Analysis Summary

    • Total Strings Scanned: 1,248
    • High Entropy Hits (>6.5): 3
    • Semantic Matches: 2
    • Action Required: 3 critical/high findings suggest active secrets are present in the source.

    Next steps

    1. Move the identified keys in src/auth/provider.ts and .env.local to a secure vault or managed secret provider.
    2. Run git filter-repo or a similar tool if these secrets were previously committed to version control.
    3. Update config/settings.json to use environment variable references instead of encoded strings.

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

    About this skill

    Manual pattern matching misses the cleverest obfuscation. Standard linters catch hardcoded strings, but they fail when secrets are hidden in base64 blobs, high-entropy variable assignments, or deep git history. This skill implements advanced credential forensics to find what static analysis ignores.

    What it does

    • Shannon Entropy Analysis flags non-random cryptographic tokens by calculating statistical randomness in string literals.
    • Semantic Context Probing evaluates variable naming conventions like token, auth, and hash to identify suspicious declarations.
    • Obfuscation Detection uncovers base64-encoded payloads and disguised keys hidden in configuration files.
    • Prioritized Reporting delivers a filtered list of findings, distinguishing between standard UUIDs and actual leaking credentials.

    How it works

    1. Scope Scan initiates a recursive analysis of string literals and variable declarations across the workspace.
    2. Entropy Calculation runs a Shannon entropy pass to identify high-density tokens that deviate from standard human text.
    3. Context Filtering cross-references high-entropy strings with surrounding code clues and naming patterns.
    4. Result Verification eliminates false positives from standard hashes or public identifiers before presenting the final audit.

    Frameworks & tools

    This skill operates as a language-agnostic forensic tool suitable for any codebase. It utilizes local environment runners like npx, uvx, or pipx to maintain workspace integrity and ensures no data leaves the local memory.

    Why this beats prompting it yourself

    Generic prompts often hallucinate security risks or miss encoded strings entirely. This skill follows a deterministic forensic workflow that combines statistical math with semantic awareness, ensuring deep coverage without the noise of false positives.

    Use cases

    • Audit legacy codebases for hardcoded production secrets before a public release.
    • Scan git commit blobs for obfuscated keys buried in historical data.
    • Validate configuration files to ensure no base64-encoded credentials are present.

    Known limitations

    Analysis is restricted to the active project workspace. It will not scan system-level configuration paths or parent directories.

    Restricted to the active project workspace. Cannot access parent directories or global system paths. Analysis is performed in-memory only.

    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

    Requires

    File System Read/Write (strictly scoped to current project workspace `./`). Zero global installation or elevated privileges required.

    Permissions

    Read Files

    Target Use Cases: - Scan for obfuscated or base64-encoded credentials in my code. - Find high-entropy hidden secrets in git history. - Audit source code for disguised API keys.

    Listed4 days ago

    What's inside

    Frequently Asked Questions

    Unlike standard linters that rely on regex for known patterns, this skill uses Shannon entropy to mathematically detect random-looking strings (like keys) even when they are encoded in base64 or given misleading variable names.

    This skill is designed as a language-agnostic tool that runs via local environment managers like npx or pipx, making it compatible with any AI agent that has access to a local terminal or file system.

    The skill is built for privacy; it performs all entropy calculations and semantic analysis locally on your machine, ensuring your sensitive source code and potential secrets never leave your environment.

    No complex setup is required; once the skill is added to your agent's toolkit, it utilizes standard runners like npx or uvx to execute the forensic scan directly within your active workspace.

    The scanner is optimized for codebase forensics and focuses on string literals and variable declarations; it does not scan compiled binaries, system-level paths, or images.

    Your purchase includes the fully configured AI skill, integration instructions for major agent platforms, and access to all future logic updates and entropy-model refinements.

    New in Security