Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/automation-recon-pipelineRecon and OSINT

automation-recon-pipeline

⁨Chain recon tools into a repeatable, resumable pipeline for continuous bug-bounty coverage. Load on "automate recon", "recon pipeline", monitoring many programs, or scaling subdomain→ live→scan. Signals: wildcard scope at scale, wanting scheduled/continuous discovery.⁩

v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/automation-recon-pipeline

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
6PQ136QBqU…jpWQSrDg==The CLI checks the SHA-256 and the signature before it writes a file.
Packagec3a050c6…93d795be
c3a050c6a8a4…d9fb93d795be1 file · ⁦1.2 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/automation/automation-recon-pipeline@ee0e0c5

When it applies

You track one or more wildcard programs and want discovery to run repeatably (and on a schedule), surfacing only new assets/findings instead of re-reviewing everything.

Why it works

Recon is a directed flow: roots → subdomains → resolve → live → ports → nuclei. Wiring the ProjectDiscovery tools together (each reads/writes lines) makes it composable, and diffing against last run (anew) turns it into continuous monitoring that alerts on change.

Method

  1. Pipeline (each stage feeds the next):
    text
    subfinder -dL roots.txt -all -silent \
      | dnsx -silent -a -resp-only \
      | httpx -silent -sc -title -tech-detect \
      | tee live.txt \
      | nuclei -silent -severity low,medium,high,critical
  2. Diff for "only new": pipe each stage through anew subs.txt / anew live.txt so reruns emit only newly-seen lines — the basis of continuous monitoring.
  3. Notify: pipe results to notify (Slack/Discord/Telegram) so new hosts/findings alert you.
  4. Schedule with cron/systemd-timer/GitHub Actions; persist state files per program so runs resume.
  5. Keep templates current: nuclei -update-templates before each run.

Gotchas

  • Stay in scope: feed only in-scope roots, filter out-of-scope hosts before scanning.
  • Respect rate limits (-rl, -c) and program automation rules — don't hammer.
  • De-dupe wildcard DNS (dnsx wildcard filtering) or you'll alert on noise forever.

Verify success

A rerun surfaces only newly-appeared assets/findings and notifies you — hands-off continuous coverage.

References

ProjectDiscovery pipeline docs; TomNomNom anew; nuclei templates.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c5c3a050c6Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login