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

How to track AI tool drift across a fleet of machines with Geiger

Write per-machine JSON on a schedule and let --diff report drift for each machine.

Who it is forAn MSP or IT administrator who manages many employee laptops and needs to know when AI tools change on each one.

The problemManaging AI agent sprawl across many machines is hard to do by hand, and no per-machine record exists by default.

The outcomeA share holding one JSON file per machine, with a baseline per machine and drift reports from --diff.

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. Pick a shared location and create a baseline JSON file for each machine after review.
  2. Schedule an RMM task or login script that runs npx geiger-scan --json %COMPUTERNAME%.json and writes the file to the share. (inferred, check the README)
  3. Run npx geiger-scan --strict --diff baseline.json on each machine, or compare the saved files, to report drift. (inferred, check the README)
  4. Review each machine's drift report and update that machine's baseline after approval.

Prompt for your agent

For each machine in <machine list>, run `npx geiger-scan --json <machine name>.json` and compare it with that machine's saved baseline using `npx geiger-scan --diff <baseline file>`. Return a table of machines with new executing or secret-holding findings, and verify that each JSON file has schemaVersion 1.

Caveat. Each machine must be scanned under its own user profile or with --home, and Geiger does not see other user accounts or containers unless you point it there.

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