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

How to alert when a new executing or secret-holding agent appears with Geiger

Save a baseline after review, then fail a scheduled check only when something new can run code or hold secrets.

Who it is forA security-minded developer or IT admin who reviewed a machine once and wants to know when a new risky tool shows up.

The problemInstalls happen quickly and often without notice, so a machine that was clean last month can have a new code-executing extension today.

The outcomeA scheduled job that exits with code 2 only when a new finding can execute code or hold secrets, and stays quiet for the reviewed inventory.

What you need first

  • Node.js 18 or newer, which includes npm and npx
  • Permission to read the user's home directory config locations on the machine being scanned
  • A writable folder if you want an HTML or JSON report saved to disk

Steps

  1. After reviewing the machine, run npx geiger-scan --json baseline.json to save the reviewed inventory. (inferred, check the README)
  2. Confirm that baseline.json is stored somewhere the scheduled job can read.
  3. Add npx geiger-scan --strict --diff baseline.json to cron or CI. (inferred, check the README)
  4. Treat exit code 2 from the job as a signal to open the new finding and review it.

Prompt for your agent

On <machine name>, save a baseline with `npx geiger-scan --json baseline.json`, then run `npx geiger-scan --strict --diff baseline.json` and report the exit code and any new findings. Verify that the job exits with code 2 only when a new finding can execute code or hold secrets.

Caveat. The alarm only covers what Geiger can see in known config locations, so it will not catch installs in nonstandard paths.

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