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

How to find agent and MCP configs inside project folders with Geiger

Add project directories to the scan to catch project-level agent and MCP configuration.

Who it is forA developer who keeps several repositories and wants to know which ones carry agent or MCP settings.

The problemProject-level agent and MCP configs live inside repositories, so a home-level scan misses them.

The outcomeA report that includes project-level agent and MCP configs and git hooks from the directories you named.

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. List the project directories you want included, such as D:\repo1 and E:\repo2.
  2. Run npx geiger-scan --path D:\repo1 --path E:\repo2 with your own paths in place of the examples.
  3. Check the git hook findings for any hook you did not install.
  4. Open the evidence path for each project-level finding.

Prompt for your agent

Run `npx geiger-scan --path <project path>` for each project folder <project path> and return the project-level agent and MCP findings with their evidence paths. Verify that git hooks are reported only for the directories you passed in.

Caveat. Git hooks are read only for the current directory and any --path directories, not for every repository on the machine.

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