More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    AI Agent Security Guardrail

    2

    Scans AI-generated code for hardcoded secrets and unsafe dynamic call sites, applies safe fixes, and produces a before/after security report — local only, no network.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    AI Agent Security Guardrail

    AI Agent Security Guardrail

    Example session with this skill installed

    I just finished a feature with my AI coding agent and I'm about to commit it. Please run a security pass on the changed code.

    Focus on

    1. Hardcoded API keys or other credentials
    2. eval()/exec() usage
    3. Whether any critical or high-severity findings can be safely fixed automatically

    Use the current git diff as the primary scope. Apply only high-confidence automatic fixes, validate the changed files afterward, and give me a concise before/after security report. Clearly identify anything that still requires human review.

    • Read your context and instructions
    • Compiled the ai agent security

    Security Guardrail Report

    Verdict: Fix before shipping

    The security pass found two high-risk issues in the AI-generated changes. One exposed credential was safely moved to an environment variable, while an unsafe eval() path remains for human review because automatically replacing arbitrary evaluation could change application behavior.

    Summary

    SeveritySecretsEval/ExecStatus
    Critical10Fixed
    High01Manual review
    Medium00—
    Low00—

    Findings

    1. Critical — Hardcoded API credential

    File: src/config.py:18

    A credential-like value was embedded directly in source code.

    Risk: A real credential committed to source control can be exposed through git history, logs, backups, forks, or repository access.

    Action: Automatically replaced the literal with an environment-variable lookup and added a safe placeholder to .env.example.

    Validation: Python syntax validation passed after the change.

    Important: If the original value was a real credential, rotate or revoke it. Removing the literal from the working tree does not remove it from existing git history.

    2. High — Potentially unsafe eval()

    File: src/agent_parser.py:42

    eval() receives a variable whose provenance is not sufficiently trusted or validated.

    Risk: If attacker-controlled or LLM-generated content reaches this call, it may become an arbitrary code-execution path.

    Action: Not automatically changed.

    The expression does not meet the narrow safe-replacement criteria for automatic remediation. Replacing it blindly could alter application behavior.

    Status: Manual review required.

    Recommended next steps

    1. Rotate the exposed credential if it was real.
    2. Confirm the new environment variable is configured in the deployment environment.
    3. Review the data flow into eval() and determine whether it can receive user, HTTP, CLI, or LLM-generated input.
    4. Prefer structured parsing or an allow-listed operation model instead of arbitrary code evaluation.
    5. Run the project's normal test suite before committing.
    6. Re-run the security guardrail after remediation.

    Scan boundary: This review was limited to the current git diff. Existing vulnerabilities outside the changed files were not treated as part of this pass.

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

    About this skill

    AI coding agents move fast and often leave two problems behind: API keys hardcoded in source, and dynamic execution wired to LLM or user input.

    This skill runs a focused local security pass on the file, diff, or repo you choose:

    • Detects known key shapes (AWS, Stripe, GitHub, Anthropic, OpenAI, PEM, …) plus high-entropy secret-like assignments
    • Detects unsafe dynamic call sites and estimates whether input looks untrusted
    • Auto-fixes critical/high secrets → environment variables (+ .env.example + .gitignore check)
    • Narrow, safe rewrite of simple expression calls → JSON.parse / safe AST literal parsing
    • Leaves statement-execution and unclear cases for manual review
    • Outputs a short ship / fix / do-not-ship report

    No outbound network. No execution of scanned code. Standard library only. Ideal right after an agent finishes a feature, before commit or PR.

    • Focused guardrail only — not a full SAST/DAST/dependency or pen-test tool
    • Targets hardcoded secrets and unsafe dynamic call sites; other issue classes may be missed
    • Auto-fixes only high-confidence cases; everything else is reported for human review
    • Does not rotate credentials, commit/push, or run the scanned application
    • A clean scan is not proof the code is fully secure — normal review and testing still apply

    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 2 months ago

    Requires

    Python

    Permissions

    Read Files
    Listed2 months ago

    What's inside

    Frequently Asked Questions

    The skill scans for hardcoded API keys (like AWS or OpenAI) and risky dynamic code patterns, automatically refactoring secrets into environment variables and generating a security audit report.

    This skill runs entirely locally with no outbound network calls, ensuring your source code and detected secrets never leave your machine or environment.

    It is designed to work with any AI agent or IDE (like Claude Code, GitHub Copilot, or Windsurf) by scanning the files or diffs the agent produces before you commit them.

    The skill supports Python, JavaScript, and TypeScript, focusing on the most common patterns where AI agents accidentally introduce security vulnerabilities.

    Yes, the skill automatically refactors high-confidence secrets into environment variables and updates your .env.example and .gitignore files to prevent future leaks.

    You receive the full skill package including the scanning engine, pre-configured security patterns, and the reporting module, along with any documentation for integration.

    New in Code Quality & Review