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-nuclei-templatesWeb and bug bounty

automation-nuclei-templates

⁨Write custom nuclei templates to codify a finding into a repeatable, mass-scannable check. Load on "write a nuclei template", turning a manual bug into automation, checking a CVE across many hosts, or regression-scanning. Signals: a reproducible request→match, YAML templates, nuclei.⁩

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

Install

No NotHoly CLI yet? Install it first.

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

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

SignatureSigned, ed25519
kdvAiMpWSo…tdLK/GDg==The CLI checks the SHA-256 and the signature before it writes a file.
Package2e16b069…b40e9e08
2e16b069d18f…c5eab40e9e081 file · ⁦1.3 KB⁩
ScanLow1 finding
  • Links to outside domains
See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/automation/automation-nuclei-templates@ee0e0c5

When it applies

You confirmed a bug (or a CVE pattern) and want to (a) find every other affected host and (b) keep a regression check. A nuclei template turns "one request + one match condition" into a scalable, shareable detector.

Why it works

nuclei runs declarative YAML: send request(s), assert matchers on the response. If your finding is expressible as request→observable signal, it's a template — and then it scans thousands of hosts consistently, no manual repetition.

Method

  1. Capture the minimal repro: the exact request and the unambiguous signal that proves the bug (status, a body string, a header, a reflected marker, response time).
  2. Write the template: id, info (name/severity/tags), then http: with method, path (use {{BaseURL}}), any payloads, and matchers (word/status/regex/dsl). Use matchers-condition: and to avoid false positives; add an extractor to pull the proof.
  3. Reduce false positives: match a signal unique to the vuln (a computed reflection, a specific error), not a generic 200; test against a known-good and known-bad host.
  4. Validate: nuclei -t mytemplate.yaml -u https://known-vuln (should hit) and against a safe host (should not). Lint with -validate.
  5. Scale/share: run across your live-hosts list; contribute non-sensitive templates upstream.

Gotchas

  • Overbroad matchers = noisy, untrusted results; require a signal that only the vuln produces.
  • Interpolate {{BaseURL}}/variables correctly; hardcoded hosts don't scale.
  • Destructive checks (writes/DoS) don't belong in a mass template — keep them read-only.

Verify success

The template fires only on genuinely-affected hosts (true on the known-vuln, quiet on the known-good) and extracts a clear proof.

References

nuclei templating guide; nuclei-templates repo (examples); PDTM docs.

Files in this version

Permissions

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

Scan findings

Reviewed on Nov 13, 2026

  1. InfoLink · Links to outside domains

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, 2026ee0e0c52e16b069Signed–

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