> For the complete documentation index, see [llms.txt](https://viperone.gitbook.io/pentest-everything/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://viperone.gitbook.io/pentest-everything/readme.md).

# Pentest Everything

## Important

Bookmark this page as other page links are likely to change or move over time. This page will always remain the same.

### About this book

This book is my collection of notes and write-ups for various offensive security based topics and platforms. This book is generally updated most days and will continue to be for the foreseeable future. If at any point this book stops being developed, I will leave a warning on this page.

This book is primarily developed for viewing on Gitbook. If you wish to fork this book please do so on GitHub.

### GitBook

**URL:** <https://viperone.gitbook.io/pentest-everything/>

### GitHub

**URL:** <https://github.com/The-Viper-One/Pentest-Everything>

### Contact

**Email:** <ViperSecurity@Protonmail.com>

### PsMapExec

Come check out my new tool release: <https://github.com/The-Viper-One/PsMapExec>

## Support me

If you find the work on here helpful, please consider supporting the project <br>

{% embed url="<https://ko-fi.com/viperone>" %}


---

# 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://viperone.gitbook.io/pentest-everything/readme.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.