> For the complete documentation index, see [llms.txt](https://playbook.sidthoviti.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://playbook.sidthoviti.com/welcome.md).

# Welcome!

### Introduction

This playbook compiles various techniques, tools, and methodologies used across different domains of penetration testing, including infrastructure, web applications, mobile, thick client, cloud, WiFi, and more. It is not meant to be used as a definitive guide but rather as a reference since I can make mistakes, and these are just my notes from my CTFs, courses, and real-world engagement experiences.

### My Website: 

[SidThoviti.com](https://sidthoviti.com/)

### Disclaimer

The content within this playbook may not always be original and sometimes it may be copied. If you are the original author and want any content to be removed, please contact me at admin\[at]sidthoviti\[dot]com.

Thank you for visiting, and I hope you find this playbook helpful in your security endeavors!

**PS:** I didn't think I'd ever make this public. This is just an experiment. 


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://playbook.sidthoviti.com/welcome.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.