How do I point nuclei at the folder cent produces?

Pass the cent output folder as nuclei's templates directory and feed your URL list as nuclei's target list. In a Trickest workflow, wire cent's folder output into the nuclei node's templates input.

How do I keep the community templates up to date?

Rerun cent before each scan. It re-clones the configured repositories and pulls in newly published detections. Where the official nuclei template set refreshes separately, cent refreshes every repo in your config.

Where does cent get its list of repositories?

From a config file. The upstream CLI builds a default one with `cent init` (at `~/.config/cent.yaml`); edit it to add or remove repos, then cent clones each with the thread count set by --threads.

Does cent keep full repo folders or only YAML files?

By default cent saves only the .yaml templates and drops the rest. Pass --keepfolders when you want the original directory structure of each cloned repository preserved in the output.

Updated Jul 14, 2026

Utilities

Gather community nuclei templates into one directory

Organize community Nuclei templates from across the ecosystem in one place.

Expand nuclei's template coverage Build a curated template directory Refresh templates on a schedule

overview

What cent does

cent clones scattered community nuclei template repositories and gathers their YAML checks into a single folder. The official ProjectDiscovery set is large, but useful detection also lives in personal and team repos that nuclei does not pull by default. cent collects that long tail.

A config file lists the repositories to clone. cent fetches them in parallel with --threads, keeps only the YAML templates unless --keepfolders is set, and writes one directory you point nuclei at. Rerun whenever you want the newest community detections.

Trickest runs cent as a managed Utilities node: config in, folder of templates out. Run it ahead of nuclei to feed an expanded community-sourced template set, then scope the scan itself by tags or severity.

source github.com/xm1k3/cent

use cases

Where cent fits

Expand nuclei's template coverage

Pull community templates from many repositories into one folder so a nuclei scan checks for far more than the default set ships with.

Build a curated template directory

Maintain a config of trusted template repos and rerun cent to assemble a single, consistent directory the rest of your workflows share.

Refresh templates on a schedule

Run cent before each scan cycle so newly published community detections are pulled in and nuclei runs against current checks.

Keep only the YAML you need

Let cent save only the template files by default, or keep full folders with --keepfolders when a repo's structure matters, so the output stays lean.

reference

cent inputs and flags

4 inputs

Name	Type	Flag	Description
config	FILE	·	Config file listing the template repositories to clone.
threads	STRING	--threads	Threads to use when cloning repositories (default 10).
keepfolders	BOOLEAN	--keepfolders	Keep full folders; by default cent saves only the YAML files.
console	BOOLEAN	--console	Print progress and collected templates to the console.

Showing key inputs. cent exposes 4 inputs in total.

example

Run cent

cent · command

# collect the configured community template repos into one foldercent --config repos.yaml -p community-templates --threads 20 --keepfolders

sample output

[INF] reading config: repos.yaml (46 repositories)[INF] cloning with 20 threads, keeping .yaml onlycommunity-templates/cves/2023/CVE-2023-27350.yamlcommunity-templates/exposures/configs/exposed-env-file.yamlcommunity-templates/misconfiguration/http-missing-security-headers.yamlcommunity-templates/vulnerabilities/wordpress/wp-xmlrpc-pingback.yamlcommunity-templates/technologies/tech-detect.yaml[INF] deduplicated and saved 1,914 templates from 46 repositories

guidance

Choosing cent

Use cent to assemble a community-sourced nuclei template set before a scan. It gathers templates; it does not scan. Its folder output feeds a nuclei templates input. Run it ahead of nuclei whenever you want broader coverage than the default templates provide.

nuclei

Runs the templates cent collects. cent is the upstream step that builds the expanded template directory.

find-gh-poc

Hunts GitHub for proof-of-concept exploits. cent specifically aggregates ready-to-run nuclei templates.

gh-scraper

General GitHub content scraper. cent is purpose-built to clone and organize nuclei template repos.

faq

cent questions

The ProjectDiscovery nuclei-templates set is what nuclei ships and updates by default. cent gathers the long tail of personal and team repositories that the default set does not include, so you can scan with both the official templates and the wider community collection.

Run cent yourself

A config of template repos feeds cent, which clones them into one folder and hands it to nuclei so a scan with the expanded community set writes findings as a queryable output.

Open cent in the library Build a workflow with it

Facts on this page come from the live Trickest tool library.