> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/detection_platform/faq/regex_library.md).

# Does Nightfall have a regex library I can choose from?

Select from an aggregated library of regexes

Yes! While Nightfall's pre-built detectors listed above are trained via machine learning, Nightfall also supports [RE2](https://github.com/google/re2/wiki/Syntax) regexes and word lists for any custom detectors that may be of interest to you. Over time, we've aggregated the following [**Regex Library**](https://airtable.com/embed/shrTrBDgr36xTI2QF?backgroundColor=purple\&viewControls=on), which you're welcome to select from to save you some time.

Please note that a regular expression is an established yet limited method that searches for pre-defined patterns, so your mileage may vary.

You can test regular expressions [**here**](https://regex-golang.appspot.com/assets/html/index.html).

You can input custom detectors directly in the Nightfall console at [app.nightfall.ai](https://app.nightfall.ai/) by navigating to [Detectors](https://app.nightfall.ai/detection-engine/detectors) → **New Detector** → **Regular expression**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.nightfall.ai/detection_platform/faq/regex_library.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.