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

# Contributors

This page lists our current Toolkit contributors:<br>

* Martin Sona
* Sophie Tedling
* Afton
* Anisa Shabir
* Lora Petrova
* Katherine de Tolly
* river\_n
* Lavache
* Lieth Carrillo
* tsvetelina
* Ana
* Freya
* Logan Williams
* Riccardo Giannardi
* Aiganysh Aidarbekova
* ForgottenPidgeon
* Emma
* Scoot
* Clara D.
* Felipe Simoni
* Stéphanie Ladel
* Megan O'Toole
* Gregg Butensky
* Monica Matin
* Justine Van Bloeme
* Nathan Burke

Special thanks to our June 2026 Toolkit Drive participants! The following individuals helped update the toolkit during this community event:

Megan O'Toole, Betsy, 0ne-nine9, LPetrova, Anisa Shabir, Afton, river\_n, Tata Kvatchadze, PolS, Evy Coeckelbergs, Lekha Sapers, Monica Matin, Alexandra Malikova, Elliot Love, Gregg Butensky, Nadia Enesco Mollá, Piya Garg, Nathan Burke, Justine Van Bloeme, Gordon Fitzpatrick, Voulpe, joaty, William Summers, Karl Riviera, Martin Sona, Sophie Tedling, Lieth Carrillo

Ex toolkit's contributors:

Alexandra Malikova, Fraser, Arsen Drobakha


---

# 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://bellingcat.gitbook.io/toolkit/more/contributors.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.
