Agent skill

eagle-eye-monitor

Help users set up and manage INFYNON Eagle Eye — continuous CVE monitoring with scheduled email alerts. Use when the user wants to monitor projects for new vulnerabilities over time, set up automated CVE alerts, configure SMTP for email notifications, or manage ongoing security monitoring.

View SKILL.md on GitHub Repository
Stars 5
Forks 0

Install this agent skill to your Project

npx add-skill https://github.com/d4rkNinja/code-guardian/tree/main/infynon-pkg/skills/eagle-eye-monitor

SKILL.md

INFYNON Eagle Eye — Continuous CVE Monitoring

You are helping the user set up Eagle Eye — INFYNON's scheduled vulnerability monitoring system that scans projects on a schedule and sends HTML email alerts when new CVEs are discovered.

What Eagle Eye Does

  • Scans one or more project directories on a configurable schedule
  • Queries OSV.dev for new CVEs since the last scan
  • Sends HTML email alerts with per-project CVE breakdowns
  • Runs as a foreground process (suitable for a server or always-on machine)

Setup — Interactive Wizard

bash
infynon pkg eagle-eye setup

The wizard prompts for:

  1. SMTP host (e.g., smtp.gmail.com, email-smtp.us-east-1.amazonaws.com)
  2. SMTP port (587 for STARTTLS, 465 for SSL)
  3. SMTP username / password (or AWS SES credentials)
  4. From address (e.g., security@yourcompany.com)
  5. Alert recipients (comma-separated email list)
  6. Project paths to monitor (absolute paths to directories with lock files)
  7. Risk level threshold (LOW / MEDIUM / HIGH / CRITICAL — only alert on this severity and above)
  8. Scan interval (hourly, daily, weekly)

Config is stored at ~/.infynon/eagle-eye.toml.

Start Monitoring

bash
infynon pkg eagle-eye start           # Start in foreground (blocks the terminal)
infynon pkg eagle-eye status          # Check config and last scan time
infynon pkg eagle-eye enable          # Enable (if previously disabled)
infynon pkg eagle-eye disable         # Pause monitoring without deleting config

SMTP Configuration Examples

Gmail (app password required)

smtp_host: smtp.gmail.com
smtp_port: 587
smtp_user: you@gmail.com
smtp_pass: your-app-password   # Generate at myaccount.google.com → Security → App passwords

AWS SES

smtp_host: email-smtp.us-east-1.amazonaws.com
smtp_port: 587
smtp_user: <SMTP username from SES console>
smtp_pass: <SMTP password from SES console>

Self-hosted (Postfix / Mailcow)

smtp_host: mail.yourdomain.com
smtp_port: 587
smtp_user: alerts@yourdomain.com
smtp_pass: your-password

What the Alert Email Contains

Each alert email includes:

  • Summary: total new CVEs found across all projects, breakdown by severity
  • Per-project section: project name, affected packages, CVE IDs, severity, safe version, fix command
  • Direct fix commands: copy-paste-ready infynon pkg fix commands

Run in the Background (Linux / macOS)

Eagle Eye runs in the foreground. To keep it running:

bash
# systemd service
cat > /etc/systemd/system/eagle-eye.service << 'EOF'
[Unit]
Description=INFYNON Eagle Eye CVE Monitor
After=network.target

[Service]
ExecStart=/usr/local/bin/infynon pkg eagle-eye start
Restart=always
User=youruser

[Install]
WantedBy=multi-user.target
EOF

systemctl enable eagle-eye
systemctl start eagle-eye
bash
# Or with screen
screen -dmS eagle-eye infynon pkg eagle-eye start
bash
# Or with nohup
nohup infynon pkg eagle-eye start > ~/eagle-eye.log 2>&1 &

Monitoring Multiple Projects

During setup, provide multiple project paths:

Project paths: /home/user/api-backend, /home/user/frontend, /home/user/mobile-app

Eagle Eye scans each path for all supported lock files (package-lock.json, Cargo.lock, uv.lock, etc.) and reports per-project.

Risk Level Configuration

Level Sends alert for
LOW All CVEs including informational
MEDIUM Medium + High + Critical
HIGH High + Critical only (recommended for most teams)
CRITICAL Critical CVEs only (minimal noise)

Recommended: HIGH — alerts you to serious vulnerabilities without flooding your inbox with low-severity noise.

Combine with CI Gates

Eagle Eye catches new CVEs between releases. Pair it with CI gates for defense-in-depth:

yaml
# On every commit: hard block
- run: infynon pkg npm install --strict high

# Nightly: full scan with report
- run: infynon pkg scan --output markdown

Eagle Eye handles the ongoing monitoring; CI gates handle the moment of install.

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

d4rkNinja/code-guardian

attack-response

Emergency playbook for responding to active attacks using INFYNON firewall. Use when the user is under attack, seeing suspicious traffic, experiencing DDoS, noticing brute-force attempts, or investigating blocked requests. Covers immediate IP blocking, log analysis, rule creation, and post-incident hardening.

5 0
Explore
d4rkNinja/code-guardian

rule-writer

Help users write custom WAF rules for INFYNON firewall. Use when the user wants to create custom rules, block specific patterns, allow specific IPs, flag suspicious requests, rate-limit specific routes, or tune the firewall beyond default settings. Also use when the user shows you traffic logs and asks what rules to write.

5 0
Explore
d4rkNinja/code-guardian

firewall-setup

Help users set up and manage the INFYNON network firewall — a reverse proxy WAF with TUI dashboard. Use when the user asks about firewall configuration, WAF rules, rate limiting, IP blocking, network security, reverse proxy setup, DDoS protection, or traffic monitoring. Also use when you see infynon.toml in the project.

5 0
Explore
d4rkNinja/code-guardian

package-security

Help users secure their project dependencies using INFYNON CLI. Use when the user asks about package vulnerabilities, CVE scanning, dependency auditing, secure package installation, fixing vulnerable packages, migrating package managers, or monitoring dependencies. Also use when you detect lock files (package-lock.json, yarn.lock, Cargo.lock, uv.lock, poetry.lock, go.sum, Gemfile.lock, composer.lock, etc.) in the project.

5 0
Explore
d4rkNinja/code-guardian

cve-triage

Help users triage and prioritize CVE findings from INFYNON package scans. Use when the user has CVE scan results and needs to decide what to fix, what to defer, or how to handle a specific vulnerability. Covers severity interpretation, fix strategies, safe version selection, and handling false positives.

5 0
Explore
d4rkNinja/code-guardian

weave

Help users build, run, and analyze API test flows with INFYNON Weave (`infynon weave`). Use when the user asks about API testing, integration testing, flow-based testing, testing API sequences, security probing endpoints, runtime inputs (OTP, 2FA, CAPTCHA), or when .infynon/api/ directory is detected. Covers node creation, flow building, prompt inputs, body editing, AI-assisted wiring, security probes, and TUI visualization. Always use this skill whenever the user mentions testing APIs, flows, weave, integration tests, OTP handling, or prompt inputs — even if they don't say "infynon weave" explicitly.

5 0
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results