Analysis updated 2026-05-18
Run automated bug hunting sessions on a repo, with each finding paired to a failing test and a fix commit.
Add bughunt to Codex through the plugin marketplace to make it available across threads.
Install just the skill portion into an existing Codex setup without the full plugin.
| kylevedder/bughunt | 0xkinno/neuralvault | 0xlocker/d17-contracts | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | — | TypeScript | Solidity |
| Setup difficulty | easy | hard | hard |
| Complexity | 2/5 | 4/5 | 5/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires an existing Codex installation to use.
Bughunt is a skill for the Codex coding assistant that focuses on finding bugs in a codebase over an extended session, rather than a single one off check. It sets up a repeating loop on a git branch, and every time it identifies a bug it accepts as real, it makes two separate commits for that finding. The first commit adds a failing test that demonstrates the bug. The second commit contains the actual fix. This means the project history documents each problem twice, once to prove it exists and once to show how it was resolved. There are two ways to install it. If you want the full plugin, you add it through Codex's plugin marketplace with a short command line instruction, then restart Codex or start a new conversation thread and tell it to use bughunt on the current repository. If you only want the skill itself without the rest of the plugin, you can ask Codex to install just that skill, using the skill installer feature to fetch it from a specific path inside the bughunt repository. The README explains that it is published as a full GitHub repository rather than a simple text snippet, because Codex plugins and skills are organized as folders of files, something a single file snippet could not represent. The README does not list the language the project is written in, and it does not describe what technology bughunt is built on internally, only what it does once installed inside Codex. There are no other setup instructions, configuration options, or usage examples given beyond the install and invoke steps described here. The repository has one star at the time of this writing, and no license is stated in the README.
A Codex plugin that runs a sustained bug hunting loop, pairing each accepted finding with a failing test commit followed by a fix commit.
No license is specified in the README.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.