SkillAgentSearch skills...

aeon-vuln-scanner

Audit trending repos for real exploitable vulnerabilities and disclose responsibly — Private Vulnerability Reporting for code flaws and verified secrets, public PRs only for already-disclosed dependency CVEs. Semgrep + TruffleHog + osv-scanner + Slither with reachability triage.

Install / Use

npx skills add BankrBot/skills --skill aeon-vuln-scanner

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Category

Security

Supported Platforms

Universal

Our assessment of aeon-vuln-scanner

aeon-vuln-scanner scores 87/100 on our quality scale, 688th of 1,108 Security skills we index.

Its SKILL.md is 3.3 KB long, well organised into 13 sections with 2 code examples: a solid amount of guidance for an agent.

With 1,201 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so aeon-vuln-scanner is actively maintained.
  • Our last check on 2026-10-11 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-06. Automated pattern scan on 2026-10-06. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

aeon-vuln-scanner compared with similar skills

All 4 of these similar skills score higher than aeon-vuln-scanner; compare them before choosing.

SkillScoreStarsUpdatedFormat
aeon-vuln-scanner (this skill)by BankrBot871.2k54d agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install aeon-vuln-scanner?
Run npx skills add BankrBot/skills --skill aeon-vuln-scanner. The install tabs above show the steps for each supported agent.
Which AI agents does aeon-vuln-scanner work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is aeon-vuln-scanner safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is aeon-vuln-scanner still maintained?
The repository was last updated about 2 months ago, so aeon-vuln-scanner is actively maintained.

name: aeon-vuln-scanner description: | Audit trending repos for real exploitable vulnerabilities and disclose responsibly — Private Vulnerability Reporting for code flaws and verified secrets, public PRs only for already-disclosed dependency CVEs. Semgrep + TruffleHog + osv-scanner + Slither with reachability triage. Skips targets that have no safe disclosure channel. Triggers: "vuln scan owner/repo", "audit this repo", "responsible-disclosure scan", "check for secret leaks", "scan dependencies for CVEs".

aeon-vuln-scanner

A scanner that dumps zero-days into public PRs isn't a helper — it's a publisher. This skill triages every finding by reading the code and routes to the right disclosure channel.

Inputs

| Param | Description | |---|---| | var | Optional owner/repo. If empty, auto-picks from chained github-trending output or fresh trending API. |

Target selection

  • Language: JS/TS, Python, Go, Rust, or Solidity.
  • ≥ 50 stars, not a fork, active in last 6 months.
  • Handles untrusted input (auth, crypto, network, file I/O, templating).
  • Skip: intentionally vulnerable teaching repos (juice-shop, webgoat, *-ctf).
  • Skip if no PVR enabled AND no SECURITY.md — no safe channel.
  • Skip if scanned in last 30 days (dedup via vuln-scanned.json).

Scanners

# Static analysis
semgrep --config=p/security-audit --config=p/owasp-top-ten --config=p/secrets \
  --severity=ERROR --severity=WARNING --json --timeout=300 \
  --exclude=test --exclude=examples --exclude=node_modules .

# Verified secrets (filesystem + git history)
trufflehog filesystem . --only-verified --json
trufflehog git file://. --only-verified --json

# Dependency CVEs across npm/pip/go/cargo/etc
osv-scanner --format=json --recursive .

# Solidity (if .sol files present)
slither . --json out.json --exclude-informational --exclude-low

All-scanners-failed reports error, never clean.

Triage (per candidate)

  1. Open the file at the reported line. Read 30-50 lines of context.
  2. Write one sentence: what attacker controls, what they achieve. Can't? Discard.
  3. Check the call path — reachable from external input in production code?
  4. Drop if in tests, fixtures, examples, behind a feature flag, or requires attacker privs ≥ what's gained.

Disclosure routing

| Finding | Channel | |---|---| | Dependency CVE | Public PR bumping the dep — CVE already public. | | Code vulnerability | PVR — publishing creates a zero-day. | | Verified leaked secret | PVR + rotation request. | | Smart-contract bug | PVR — on-chain exploitation often immediate. | | No PVR + no SECURITY.md | Skip and log. Do no harm. |

# PVR (private advisory)
gh api -X POST "/repos/$REPO/security-advisories" \
  -f summary="..." -f severity="..." -F cwe_ids='["CWE-89"]' -f description="..."

Proposed patches for code flaws go to your fork only (private/fix-<slug> branch). Never open a public PR for an unpatched code flaw — link the SHA in the advisory body so the maintainer can cherry-pick.

Required scopes

GH_TOKEN with repo + repository_advisories:write (for PVR).

Rules

  • Do no harm. No safe channel → no publication.
  • Read the code. A scanner hit alone isn't a vulnerability.
  • One report per repo per run; bundle related findings.
  • Skip intentionally vulnerable repos and CTFs.
  • Be deferential — you're offering help, not grading homework.

Related Skills

View on GitHub
GitHub Stars1.2k
CategorySecurity
Updated1mo ago
Forks629

Languages

JavaScript

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium