A coding-agent skill for multi-phase security audits with independently verified, machine-readable findings
Free tool inAgent skills and plugins
Security-audit-skill at a glance
Checked 21 Oct 2026A coding-agent skill for multi-phase security audits with independently verified, machine-readable findings. Added from the nightly trending feed on 2026-10-21 with 34,298 GitHub stars. So far only the licence comes from GitHub; the other facts are unknown until someone checks them.
RepoQuarry. “Security-audit-skill.” Checked 21 Oct 2026. https://repoquarry.dev/projects/security-audit-skillWhat it replaces
Nothing people pay for: it’s a free tool, listed because people search for it. Find similar projects in Agent skills and plugins.
Facts, with sources
Every answer links to where we found it. We read the documentation; we did not install it.
No licence changes since we started watching. Licence watch: follow Security-audit-skill and we email you if its licence terms change.
Growth and activity in detail
Is it popular, and is anyone still working on it? From GitHub.
3 people committing in the last 12 months · 0 pull requests merged in 30 days · 13 issues opened, 1 closed in 30 days
Stars over time
Building historyNot enough history for a 7-day gain.
- Security-audit-skill
Tracked daily since 21 Oct 2026. Dashed history: estimated from public records of when people starred the repo. Lines connect observations only; gaps contain no measured points.
Commits per week, last 52 weeks
active 2 of the last 12 weeksDown 71% on the 12 weeks before.
Where these numbers come from
- Stars, forks, releases: GitHub's public API, fetched every night (last fetch today).
- Star history: counted every night since 21 Oct 2026; the dashed part before that is estimated from the dates people starred the repo.
- Commits and people committing: GitHub's repository statistics, counted weekly. Names are never stored.
- Pull requests and issues: counted from GitHub for the last 30 days.
- Stars show popularity, not quality. The facts below are checked separately, by reading the project's own documentation. How we check.