> For the complete documentation index, see [llms.txt](https://w4h33d.gitbook.io/hack-notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://w4h33d.gitbook.io/hack-notes/hack-notes.md).
# Hack Notes
Welcome to **Hack Notes**, a comprehensive collection of notes created by me, with a focus on CTF (Capture The Flag) writeups and information security methodologies. This public repository is designed to provide a valuable resource for anyone interested in learning about cybersecurity or improving their knowledge and skills in this field.
Whether you're an aspiring cybersecurity professional, a seasoned veteran looking to stay up-to-date with the latest trends and techniques, or simply someone interested in the subject, you'll find plenty of useful information and insights here.
Within these notes, you'll find a wide variety of content, including detailed writeups of CTF challenges, step-by-step guides to performing various cybersecurity tasks, explanations of common techniques and tools used by hackers, and much more.
These notes are constantly evolving and being updated, as I continue to explore new topics and discover new information about the field of cybersecurity. I welcome feedback, suggestions, and contributions from anyone who finds value in this resource.
So feel free to explore Hack-Notes and learn more about the exciting and constantly evolving world of cybersecurity!
---
# 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://w4h33d.gitbook.io/hack-notes/hack-notes.md?ask=&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.
