DEDUPED Hot AI repos, turned into use cases Get 5 a day

What you can do with Agent Security

SolonGate Agent Security is a local, open-source Go gateway that checks AI coding agent tool calls against policy, detects secrets, and writes an on-device audit trail.

Trended earlier

solongate/agent-security on GitHub

Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk.

What do you want to do?

4 use cases

  • Stop an AI coding agent from reading your .env secrets

    Install the local guard so an agent is refused when it reaches for a .env file and every decision is logged.

    View prompt
    Install the SolonGate guard from https://github.com/solongate/agent-security by running ./scripts/shell/install.sh in a fresh terminal, then start <agent> in <project-path> and ask it to read the .env file. Expected output: the guard refuses the read and the agent reports the refusal. Verify by running `solongate audit` and confirming a deny entry for .env exists in ~/.solongate/local-logs/solongate-audit.jsonl.

  • Lock files so a coding agent cannot delete or edit them

    Put an OS-level lock on key files and start the agent inside that protection so it cannot remove them.

    View prompt
    Using the SolonGate repo at https://github.com/solongate/agent-security, run `solongate protect <file-path>` and then `solongate run -- claude` in <project-path>. Expected output: the protected file cannot be deleted or written by the agent. Verify by running `solongate protect list` and checking that <file-path> is listed with the lock it is actually held by.

  • Confine a coding agent to one project folder on Linux

    Start an agent in a closed box where only one project directory exists and nothing else on the machine is visible.

    View prompt
    On a Linux machine with bwrap installed, use the SolonGate repo at https://github.com/solongate/agent-security to create a sandbox box from the TUI Sandbox section for <project-path>, then run `solongate sandbox 001 claude`. Expected output: the agent starts with the project at /workspace and home directories absent. Verify by running `solongate sandbox --explain 001` and checking that the listed contents match the project only.

  • Review every tool call an AI coding agent made

    Read the local audit trail and watch live tool calls to see what an agent tried and what the guard decided.

    View prompt
    Using https://github.com/solongate/agent-security, run `solongate audit` after a session with <agent> in <project-path>. Expected output: a list of tool calls with their allow or deny decisions. Verify that ~/.solongate/local-logs/solongate-audit.jsonl contains one JSON object per decision, matching what the audit view shows.

How to use Agent Security

  1. Check you have what it needs: A machine where you can run a shell and git (the README installs with git clone and ./scripts/shell/install.sh); Claude Code or Codex installed as the agent you want to guard; A new terminal after install, since hooks load only when a session starts.
  2. Open solongate/agent-security on GitHub and read the README and license.
  3. git clone https://github.com/solongate/agent-security.git
  4. cd agent-security
  5. ./scripts/shell/install.sh
  6. Open a new terminal, then start Claude Code or Codex in your project.

These steps come from our top use case, Stop an AI coding agent from reading your .env secrets, which also has a copy-paste agent prompt.

Agent Security alternatives · Best AI repos for Security and science

About this repo

Requirements

  • A machine where you can run a shell and git (the README installs with git clone and ./scripts/shell/install.sh)
  • Claude Code or Codex installed as the agent you want to guard
  • A new terminal after install, since hooks load only when a session starts
  • For the sandbox use case: Linux with bubblewrap (bwrap) installed, since the README says it is required and macOS and Windows refuse
Maintain Agent Security? Add the Featured on Deduped badge

Paste this into your README:

[![Featured on Deduped](https://dedupedai.com/badge/solongate-agent-security.svg)](https://dedupedai.com/use-cases/solongate-agent-security/?ref=badge)

More badge styles and HTML

Questions about Agent Security

What is Agent Security?

SolonGate Agent Security is a local, open-source Go gateway that checks AI coding agent tool calls against policy, detects secrets, and writes an on-device audit trail. It is an open-source project on GitHub: https://github.com/solongate/agent-security.

Who is Agent Security for?

Developers and security-minded engineers who run AI coding agents on their own machines and want to control what those agents can read, write, and send.

What can I do with Agent Security?

4 use cases so far, for example: Stop an AI coding agent from reading your .env secrets; Lock files so a coding agent cannot delete or edit them; Confine a coding agent to one project folder on Linux. Each has steps and a copy-paste agent prompt.

What do I need to run Agent Security?

A machine where you can run a shell and git (the README installs with git clone and ./scripts/shell/install.sh); Claude Code or Codex installed as the agent you want to guard; A new terminal after install, since hooks load only when a session starts; For the sandbox use case: Linux with bubblewrap (bwrap) installed, since the README says it is required and macOS and Windows refuse.

What are alternatives to Agent Security?

Other hot AI repos in Security and science: Rea, Reverify, Ablation, Claude AD, Awesome Reverse Engineered.

Is Agent Security safe to run?

Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.