What do you want to do?
5 use cases
-
Hunt exploitable flaws in your own codebase
Run the attacker-first scanner to get verified issues, each with an executable exploit and a proposed fix.
- Vuln Hunter
- Security and science
- Intermediate
View prompt
Using the VulnHunter repo at nealbridges/VulnHunter, run the /vulnhunt skill against <target repo path>, which I am authorized to audit. Return a list of confirmed findings with each finding's entry point, sink, and exploit status. Verify that every listed finding includes an executable exploit or is labeled as lacking one.
-
Fix a confirmed finding with a failing test first
Turn one verified finding into a red-then-green security fix and a reviewable pull request.
- Vuln Hunter
- Security and science
- Intermediate
View prompt
Using the VulnHunter repo at nealbridges/VulnHunter, run the /vulnhunter-fix skill on the finding <finding ID> in <target repo path>. Return the exploit demo, the RED test output, the GREEN test output, and a pull request link or diff. Verify that the security test fails before the code change and passes after it.
-
Verify that a security fix really closes the finding
Use a separate read-only agent to give a per-finding verdict on whether a fix worked.
- Vuln Hunter
- Security and science
- Intermediate
View prompt
Using the VulnHunter repo at nealbridges/VulnHunter, run the /vulnhunt-fix-verify skill on the findings <finding IDs> in <target repo path>. Return one verdict per finding, stating whether it was remediated. Verify that the verifier made no code changes, since it is described as read-only.
-
Run unattended scans across several repositories
Use the vulnhunter-run operator to clone, hunt, and record results without manual steps.
- Vuln Hunter
- Security and science
- Advanced
View prompt
Using the VulnHunter repo at nealbridges/VulnHunter, run the vulnhunter-run operator on the repositories <repo list>. Return the scan manifest and the results location for each repository. Verify that the manifest passes validation and that the operator stopped at its explicit stop rules where a repository could not be cloned or scanned.
-
Port the skills to a harness you already run
Point the skill and model settings at your own agent harness through environment variables.
- Vuln Hunter
- Security and science
- Advanced
View prompt
Using the VulnHunter repo at nealbridges/VulnHunter, configure the environment variables VULNHUNT_SKILLS_DIR, VULNHUNT_AGENTS_DIR, and VULNHUNT_MODEL for my harness, then run /vulnhunt on <test repo path>. Return the configuration used and whether the skill loaded. Verify that the run used the model I set and not a hardcoded default.
How to use Vuln Hunter
- Check you have what it needs: Source code you own or are authorized to audit; Your own model access, using the most capable reasoning model your agent harness offers; An agent harness with a skills directory and subagent support.
- Open nealbridges/VulnHunter on GitHub and read the README and license.
- Clone the repository with
git clone https://github.com/nealbridges/VulnHunter(inferred, check the README) - Run the installer from the repo folder with
bash install.sh, setting VULNHUNT_SKILLS_DIR for your harness first if it does not use a default location (inferred, check the README) - Open your agent harness in the folder of the code you own and are authorized to audit
- Run
/vulnhuntto start the hunt from entry points toward dangerous sinks
These steps come from our top use case, Hunt exploitable flaws in your own codebase, which also has a copy-paste agent prompt.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeVuln Hunter alternatives · Best AI repos for Security and science
About this repo
- Who it is forSecurity engineers and application developers who are authorized to audit their own code and want an agent-driven scan, fix, and verify loop.
- Why it is hot
- LanguagePython
- Sourcegithub.com/nealbridges/VulnHunter · Back to Hot repos
Requirements
- Source code you own or are authorized to audit
- Your own model access, using the most capable reasoning model your agent harness offers
- An agent harness with a skills directory and subagent support
- Python and git installed locally
Maintain Vuln Hunter? Add the Featured on Deduped badge
Paste this into your README:
[](https://dedupedai.com/use-cases/nealbridges-vulnhunter/?ref=badge)
Questions about Vuln Hunter
What is Vuln Hunter?
VulnHunter is an open-source agentic AI security scanner that traces attacker-reachable entry points to exploitable flaws, proves them with proof-of-concept tests, and proposes test-first fixes. It is an open-source project on GitHub: https://github.com/nealbridges/VulnHunter.
Who is Vuln Hunter for?
Security engineers and application developers who are authorized to audit their own code and want an agent-driven scan, fix, and verify loop.
What can I do with Vuln Hunter?
5 use cases so far, for example: Hunt exploitable flaws in your own codebase; Fix a confirmed finding with a failing test first; Verify that a security fix really closes the finding. Each has steps and a copy-paste agent prompt.
What do I need to run Vuln Hunter?
Source code you own or are authorized to audit; Your own model access, using the most capable reasoning model your agent harness offers; An agent harness with a skills directory and subagent support; Python and git installed locally.
What are alternatives to Vuln Hunter?
Other hot AI repos in Security and science: Rea, Reverify, Ablation, Claude AD, Awesome Reverse Engineered.
Is Vuln Hunter safe to run?
Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.