DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to block any request that contains a secret with Preflight

Use no-go mode so requests with non-allowlisted findings get a 409 and never reach underclass.

Who it is forA security-minded team lead who needs a hard stop rather than rewritten content when a secret appears in an agent prompt.

The problemRedacted requests may still carry context the team does not want the model to process, so some incidents need a full stop.

The outcomeRequests with findings return HTTP 409 with opaque finding IDs, and nothing is forwarded to underclass.

What you need first

  • A running underclass instance on 127.0.0.1:8080
  • Nix (for `nix run`) or devenv and Cargo for a local checkout
  • A coding harness or client that can change its base URL to http://127.0.0.1:8081/v1
  • Bubblewrap available for the default sandboxed attachment workers

Steps

  1. Create a TOML file with mode = "no-go" and the bind, upstream, and carnet values you need (inferred, check the README)
  2. Validate the file with preflight check --config /path/to/config.toml (inferred, check the README)
  3. Start the proxy with preflight serve --config /path/to/config.toml
  4. Send a request containing a test secret and confirm the response status is 409
  5. Reload settings after edits with systemctl reload preflight on NixOS

Prompt for your agent

Using the preflight repo at github.com/ghuntley/preflight, write a config.toml with mode set to no-go, validate it with preflight check, and send a request containing a fake secret from <test-file> through the proxy. Expected output is an HTTP 409 with an opaque finding ID and no secret text, and verify that underclass received no request.

Caveat. The README describes a NixOS reload command, so non-NixOS users must find their own way to send SIGHUP to the running process.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page