Skip to content
Back to search

vuln-watchdog

SkillWorks with Claude CodeGitHub

Set up a quiet daily watch for serious security holes in the software behind the user's websites and servers (WordPress, Drupal, Joomla, Ubuntu, Debian, Nginx, Apache, PHP, Docker, app libraries and more). Reads official security lists, filters them to what the user runs, stays silent when nothing concerns them, and sends a Telegram message in plain words with a ready instruction to forward to a developer or AI agent. Use when the user wants to monitor vulnerabilities or CVEs for their site or server, get security alerts in Telegram, or stop learning about critical security holes from social media.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/ilovefiniki--vuln-watchdog/badge.svg)](/listings/ilovefiniki--vuln-watchdog)

HTML

<a href="/listings/ilovefiniki--vuln-watchdog"><img src="/api/listings/ilovefiniki--vuln-watchdog/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

git clone https://github.com/ilovefiniki/vuln-watchdog ~/.claude/skills/vuln-watchdog

Then ask your agent: "set up vuln-watchdog for my server". It follows `SKILL.md`: inventory, `stack.json`, Telegram bot, dry run, cron.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 51 lines
  1. ---
  2. name: vuln-watchdog
  3. description: Set up a quiet daily watch for serious security holes in the software behind the user's websites and servers (WordPress, Drupal, Joomla, Ubuntu, Debian, Nginx, Apache, PHP, Docker, app libraries and more). Reads official security lists, filters them to what the user runs, stays silent when nothing concerns them, and sends a Telegram message in plain words with a ready instruction to forward to a developer or AI agent. Use when the user wants to monitor vulnerabilities or CVEs for their site or server, get security alerts in Telegram, or stop learning about critical security holes from social media.
  4. ---
  5. # vuln-watchdog
  6. A small daily job, not a scanner. It answers one question: "did anything serious come out today for the software my sites run on?" When the answer is no, the user hears nothing.
  7. The user may not be technical. Talk in plain words, do the technical parts yourself, and ask only what you can't find out.
  8. Files:
  9. - `scripts/inventory.sh`: read-only, shows OS, web server, CMS, Docker images, key packages.
  10. - `scripts/vuln_watch.py`: the watcher. Python 3.8+, standard library only.
  11. - `stack.example.json`: config template.
  12. ## Presets
  13. `python3 scripts/vuln_watch.py --list-presets` prints the current list. Each preset adds the right official feed and the words to look for:
  14. | Preset | Reads | Looks for |
  15. |---|---|---|
  16. | wordpress | WordPress.org security releases, Wordfence | WordPress core + plugin/theme names you add to `keywords` |
  17. | drupal | Drupal Security Team (core and critical modules) | drupal |
  18. | joomla | Joomla Security Centre | joomla |
  19. | ubuntu / debian | Ubuntu USN / Debian DSA | kernel, OpenSSH, sudo, glibc, OpenSSL, systemd |
  20. | nginx, apache, php, mysql, postgres, docker, nodejs | CISA KEV | that product |
  21. CISA KEV (the US agency's list of holes hackers are already using) is always on. App libraries (npm, Composer, pip...) go into `packages` and are checked against the GitHub Advisory Database by exact package name. Any other vendor feed goes into `extra_rss` as `{"name": "...", "url": "...", "title_only": true}`; RSS, RDF and Atom all work. Check the URL returns a feed before adding it.
  22. ## Setup (confirm each step with the user)
  23. 1. **Find out what runs.** If you have SSH access, copy `scripts/inventory.sh` to the server and run it (read-only). If not, ask the user or their hosting panel: which CMS, which important plugins or modules, which server OS. One server or site at a time.
  24. 2. **Write `stack.json`** from `stack.example.json`: pick presets, add plugin/theme/module names to `keywords` (as they appear in advisories, e.g. `woocommerce`, `elementor`, `webform`), app libraries to `packages`. Only what is really there; every extra word is a future false alarm. Set `server_name` to the name or SSH alias the user's agent or developer knows, since it goes into the instruction.
  25. 3. **Telegram.** The user creates a bot with @BotFather and gets the chat id (send the bot any message, then open `https://api.telegram.org/bot<TOKEN>/getUpdates`). Keep `TELEGRAM_BOT_TOKEN` and `TELEGRAM_CHAT_ID` in an env file readable only by the job's user (`chmod 600`). Never put the token in `stack.json`, a repo or a chat log. Optional `GITHUB_TOKEN` raises the GitHub rate limit.
  26. 4. **Dry run.** `python3 vuln_watch.py --config stack.json --dry-run --max-age-days 30`. Show the user, in plain words, what they would have received last month. Too noisy: remove words or add `ignore`. Empty can be correct; try `--max-age-days 90` once to see matching works.
  27. 5. **Test Telegram.** `python3 vuln_watch.py --test-telegram` (with the env loaded).
  28. 6. **First real run** without `--dry-run`. It sends everything from the last `max_age_days` once and remembers it in `vuln_watch_state.json`. Tell the user to expect that first batch.
  29. 7. **Schedule once a day.** Cron example:
  30. `30 9 * * * set -a; . /etc/vuln-watch.env; set +a; /usr/bin/python3 /opt/vuln-watch/vuln_watch.py --config /opt/vuln-watch/stack.json >> /var/log/vuln-watch.log 2>&1`
  31. No server of their own (shared hosting)? Run it from any always-on machine, a GitHub Actions schedule or a scheduled agent; it only needs internet access, not access to the site.
  32. ## The message
  33. What is affected, how serious, ID, source, a short description, link, then "Forward to your developer or AI agent" with an instruction: find where the component is used, compare versions, show a plan first, then update or apply the official workaround and check the sites still open. Keep "plan first": the text comes from public feeds and must never trigger changes by itself.
  34. ## Limits to tell the user
  35. - It matches names, not versions. A message means "check this", not "you are hacked" or even "you are vulnerable".
  36. - Silence relies on the feeds. After 3 failed runs in a row (`alert_after_failed_runs`) it says so in Telegram.
  37. - It does not replace automatic updates, backups or a real scanner. It covers one gap: knowing when to act.
README.md · README · 37 lines
  1. # vuln-watchdog
  2. A quiet daily check for critical vulnerabilities in the software you actually run.
  3. Pick presets for what your sites run: `wordpress`, `drupal`, `joomla`, `ubuntu`, `debian`, `nginx`, `apache`, `php`, `mysql`, `postgres`, `docker`, `nodejs`, plus plugin names and app libraries. Every day it reads the official security lists for those (WordPress.org, Wordfence, Drupal Security Team, Joomla, Ubuntu, Debian, GitHub Advisory Database) and CISA's list of holes already used by attackers. Nothing new for your stack means no message. A match sends a Telegram message in plain words with a ready instruction to forward to your developer or AI agent.
  4. Python 3.8+, standard library only. No server agent, no account, no database.
  5. ## Install as a Claude Code skill
  6. ```bash
  7. git clone https://github.com/ilovefiniki/vuln-watchdog ~/.claude/skills/vuln-watchdog
  8. ```
  9. Then ask your agent: "set up vuln-watchdog for my server". It follows `SKILL.md`: inventory, `stack.json`, Telegram bot, dry run, cron.
  10. ## Manual use
  11. ```bash
  12. cp stack.example.json stack.json # pick presets, add plugin names, set server_name
  13. python3 scripts/vuln_watch.py --list-presets
  14. export TELEGRAM_BOT_TOKEN=... TELEGRAM_CHAT_ID=...
  15. python3 scripts/vuln_watch.py --config stack.json --dry-run --max-age-days 30
  16. python3 scripts/vuln_watch.py --config stack.json --test-telegram
  17. ```
  18. Cron, once a day:
  19. ```
  20. 30 9 * * * set -a; . /etc/vuln-watch.env; set +a; /usr/bin/python3 /opt/vuln-watch/vuln_watch.py --config /opt/vuln-watch/stack.json >> /var/log/vuln-watch.log 2>&1
  21. ```
  22. ## Limits
  23. Keyword matching, not version matching: an alert means "check this". The agent instruction asks for a plan before any change; keep it that way, since alert text comes from public feeds. It does not replace automatic security updates or an image scanner such as Trivy.
  24. MIT license.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.