Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/getsentry/toolkitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/getsentry/toolkit/agent-conversation)<a href="https://agentmods.dev/commands/getsentry/toolkit/agent-conversation"><img src="https://agentmods.dev/badge/commands/getsentry/toolkit/agent-conversation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/getsentry/toolkit/agent-conversation"><img src="https://agentmods.dev/badge/commands/getsentry/toolkit/agent-conversation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 1 lines e3b0c44298fc
agent-conversation is a command published in the GitHub repository getsentry/toolkit (929 stars, last pushed today), with no licence file. Its token cost is not measured: this kind of file is read by the harness, not the model. It was not scanned, because the body is not available under its licence. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-14.
Other commands, from other repositories
issue
Command "issue" from getsentry/sentry-mcp, covering examples, list issues, list issues in a specific project, all projects in an org and search for a project across organizations.
local
Command "local" from getsentry/sentry-mcp, covering examples, start the server and tail events (default), run your app with the local server auto-enabled, use a custom port and only show errors and logs (filter out transactions).
analytics-review
Review analytics and recent commits, then create tasks.
fix-issues
Pick up one approved task, implement the fix, and close it.
debug-files
Command "debug-files" from getsentry/sentry-mcp, covering examples, inspect a debug information file (auto-detects the format), bundle jvm sources with a debug id, exclude additional directories and output as json.
submit-to-directories
Submit the product to the directory catalog in /.darkflow/directories.csv through a real browser, and track what has already been submitted.