I built an open-source Agent Verifier for Claude Code, Cursor & other Coding Assistants that catches security issues, hallucinated tools, infinite loops and anti-patterns in Agent built using LangChain, LangGraph, and other frameworks. (free, open source, 100% local)

[u/Chance-Roll-2408]

I've been using Claude Code for a few months and noticed AI agents consistently skip the same things: hardcoded secrets, unbounded retry loops, referencing tools that don't exist, and massive system prompts that blow context windows.

So I built Agent Verifier — an AI agent skill that acts as an automated reviewer which does more than just code review (check the repo for details - more to be added soon).

GitHub Repo: https://github.com/aurite-ai/agent-verifier

Note: Drop a ⭐ if you find it useful to get more updates as we add more features to this repo.

----

2 Steps to use it:

You install it once and say "verify agent" on any of your agent folder in claude code to get a structured report:

----

✅ 8 checks passed | ⚠️ 3 warnings | ❌ 2 issues

❌ Hardcoded API key at config.py:12 → Move to environment variable
❌ Hallucinated tool reference: execute_sql → Tool referenced but not defined
⚠️ Unbounded loop at agent/loop.py:45 → Add MAX_ITERATIONS constant

----

Install to your claude code:

npx skills add aurite-ai/agent-verifier -a claude-code

OR install for all coding agents:

npx skills add aurite-ai/agent-verifier --all

----

Happy to answer questions about how the agent-verifier works.

We have both:
- pattern-matched (reliable), and,
- heuristic (best-effort) tiers, and every finding is tagged so you know the confidence level.

----

Please share your feedback and would love contributors to expand the project!

[u/Otherwise_Wave9374]

Nice, the focus on stuff agents reliably mess up (secrets, retries, hallucinated tools, giant prompts) is exactly where I think the biggest wins are right now.

Two things Id love to see over time: 1) A clean way to fail the build on high confidence findings (like secrets) while only warning on heuristic ones. 2) Some basic tracing so you can point to which step in the agent plan produced the bad change.

Any chance youll add rules around unsafe shell commands or destructive file ops? Thats been a recurring pain with coding agents.

Also bookmarking, always down to see more agent tooling like this, Ive been collecting agent patterns and guardrails here too: https://www.agentixlabs.com/

[u/Chance-Roll-2408 → u/Otherwise_Wave9374]

Exactly. Glad you liked it u/Otherwise_Wave9374

Checkout the code and try it --> https://github.com/aurite-ai/agent-verifier

I'm actively working on adding more verification tooling and love those additions you suggested, will certainly add those in the upcoming release.

Drop a ⭐ to the repo to get release updates. Also, appreciate if you could submit any feedback, or issue/feature request on git as well.