elementalsouls / Claude-BugHunter
A Claude Code skill bundle for bug hunting and external red-team work - 82 skills, 15 slash commands, 681 disclosed-report patterns curated across 24 core vulnerability classes, plus enterprise identity + infrastructure attack matrices.
- Stars
- 5,494 stars
- Forks
- 838 forks
- Language
- Python
- License
- MIT
- Created
- May 5, 2026
- Last push
- Nov 8, 2026
- Updated
- Nov 8, 2026
Why these Tags: an agent read the README and quoted it
- Agent skill from the readme:
The skills are plain Agent Skills — the same `SKILL.md` format
- Coding agent plugin from the readme:
All 83 skills + 15 commands load namespaced under `claude-bughunter:`
An agent gave these Tags from the fixed Tag list in the AwesomeRepos source code. A code check kept each Tag only when its quote is in the text. A wrong Tag? Report an error with the form at the end of this page.
Admitted to the Repository Index on Nov 7, 2026: +117 stars in 7 days.
Star History
174 days recorded, May 19, 2026 – Nov 8, 2026 (UTC). Net change +5,499 stars.
The star count of each day is the latest count minus the net stars of the later days.
Add this Star History to a README
The images follow the light or dark theme of the page that shows them, and update every hour.
Add ?theme=light or ?theme=dark
to the chart address to keep one theme.
Star History chart
[](https://awesomerepos.com/elementalsouls/Claude-BugHunter) Badge
[](https://awesomerepos.com/elementalsouls/Claude-BugHunter) Timeline
It gained stars on each of the 174 days recorded since May 19, 2026.
Its largest 7 days were May 20, 2026 to May 26, 2026: 1,070 stars.
In the 30 days to Nov 8, 2026 it got 683 stars, 48% more than in the 30 days before.
- Created on the Repository Host
- Reached 100 stars, 15 days after it was created
- +206 stars in one day
- Reached 500 stars, 19 days after it was created
- Largest star day recorded: +271 stars
- +213 stars in one day
- Release v2.0
- Reached 1,000 stars, 21 days after it was created
- Release v2.1
- Reached 5,000 stars, 160 days after it was created
- Entered the Repository Index: +117 stars in 7 days
- Latest push
The timeline comes from the creation date and the releases on the Repository Host, the Admission, the Star History, and the Observations. Star milestones show only when the Star History records the day. The list shows up to 5 stable releases from the latest 10 releases recorded. When none of them is stable, one item counts the pre-releases. On the chart of net stars each day, a solid line marks each recorded release.
Forks and pushes
From 2 Observations, Nov 8, 2026 – Nov 9, 2026. Forks 0. AwesomeRepos saw a new push on 1 of 1 days.
- Nov 9, 2026: new push
A filled day: the last push time changed since the Observation before it.
Health facts
Measured facts in four separate dimensions, each with a date and a source. AwesomeRepos does not add them into one score. AwesomeRepos last read these facts from GitHub on Nov 9, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 2 tasks for the maintainers of elementalsouls/Claude-BugHunter.
Improve the Health Facts of the GitHub repository elementalsouls/Claude-BugHunter. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/elementalsouls/Claude-BugHunter. A change to the repository can improve each of the 2 items below. Each item gives the measured fact or score, and a task. 1. The newest release tag is a semantic version Fact: The newest release tag is v2.1. Rule: The tag of the newest release has the form 1.2.3 or v1.2.3, with an optional pre-release or build part. There is no data when the repository has no release. Task: Make the next release tag a semantic version (1.2.3 or v1.2.3). Do not change or delete a published tag. If a release tool makes the tags, configure it for semantic versions, and write the version scheme in the contributing guide. 2. A code of conduct Fact: GitHub finds no code of conduct (GitHub, 2026-11-09). Rule: GitHub finds a code of conduct in the repository or in the owner's .github repository. Task: Add CODE_OF_CONDUCT.md at the root with the Contributor Covenant 2.1 text. Change only the contact method. Ask me for the contact; do not invent one. Rules for this work: - Each file must be true for this project. Do not copy text that does not apply to it. - Do not choose a licence, a contact, or a release version for me. Ask me. - Do not publish a release, change a repository setting, or push to the default branch. Make the changes on a new branch. - Keep each change small, and run the checks of this repository before you finish. - At the end, list each item as DONE, SKIPPED (with the reason), or NEEDS A DECISION (with the question). AwesomeRepos reads these facts again in its next scan. The definitions of the checks: https://awesomerepos.com/health-facts
Maintenance
3 of 4 checks-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
Yes: A push in the last 90 days
Last push on 2026-11-08, 1 day ago. Source
-
Yes: Commits in the last 13 weeks
114 commits on the default branch in the last 13 weeks (GitHub, 2026-11-09). Source
-
No: Commits in 26 or more of the last 52 weeks
Commits in 24 of the last 52 weeks (GitHub, 2026-11-09). Source
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 6
- 24
- 27
- 12
- 60
- 10
- 1
- 0
- 1
- 0
- 0
- 3
- 5
- 6
- 5
- 7
- 28
- 7
- 8
- 7
- 7
- 9
- 8
- 7
- 7
- 7
- 7
Releases
2 of 3 checks-
Yes: A release in the last 365 days
Newest release v2.1 on 2026-06-05, 157 days ago. 2 releases in the last 365 days. Source
-
No: The newest release tag is a semantic version
The newest release tag is v2.1. Source
-
Yes: A changelog file at the root
CHANGELOG.md at the root (GitHub, 2026-11-09). Source
Security practice
1 of 1 check-
Yes: A security policy
GitHub finds a security policy (GitHub, 2026-11-09). Source
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
2 of 3 checksDependencies in the index
This section shows the packages that connect this repository to other repositories in the index.
GitHub has no dependency graph for this repository (scanned on Nov 9, 2026).
No scanned repository names a package from this repository.
Uses (in the index) · 0
None.
Used by (in the index) · 0
None.
Sources: the GitHub dependency graph of each repository, and deps.dev for the source repository of each package . A dependency graph also names development packages. deps.dev takes most source repositories from package metadata. How the dependency graph is made
Observations
Latest Observation, Nov 9, 2026: 5,494 stars, 838 forks, last push Nov 8, 2026, not archived. One of 2 Observations since Nov 8, 2026.