> ## Documentation Index
> Fetch the complete documentation index at: https://docs.komodor.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent catalog

> Reference for every Komodor-built agent you can deploy from the catalog — what each one reads, what it costs in time, and where it stops.

The catalog holds Komodor-built agents that you deploy as-is, supply credentials for, and run. This
section is the reference for each one: what it reads, what to connect before deploying it, how to
ask it for something useful, and the boundary it will not cross. For browsing the catalog and
walking the deploy wizard, see [Use specialized
agents](/manage-your-agents/build/use-specialized-agents).

Every page here answers the same nine questions in the same order, so you can compare two agents by
reading the same section twice.

<Note>
  The catalog is curated per workspace, so the entries you see in your own console are the
  authoritative list. An agent documented here may not be offered to your account, and the console is
  the place to check.
</Note>

## Choosing one

Start from the system that already holds your evidence. An investigator is only as useful as the
data it can reach, so the shortest path from deploy to a useful run is the one pointed at a system
you have already connected.

| If you want to…                                       | Deploy                                                                                |
| ----------------------------------------------------- | ------------------------------------------------------------------------------------- |
| Investigate an incident in AWS                        | [AWS Infrastructure Investigator](/manage-your-agents/build/catalog/aws-investigator) |
| Investigate an incident in Azure                      | [Azure Investigator](/manage-your-agents/build/catalog/azure-investigator)            |
| Investigate from Datadog telemetry                    | [Datadog Investigator](/manage-your-agents/build/catalog/datadog-investigator)        |
| Investigate from Google Cloud logs                    | [Google Cloud Investigator](/manage-your-agents/build/catalog/gcp-investigator)       |
| Investigate from Grafana telemetry                    | [Grafana Investigator](/manage-your-agents/build/catalog/grafana-investigator)        |
| Root-cause one Kubernetes resource, in-cluster        | [Kubernetes RCA](/manage-your-agents/build/catalog/kubernetes-rca)                    |
| Combine cluster, Grafana and GPU signals in one agent | [Cluster Investigator](/manage-your-agents/build/catalog/cluster-investigator)        |
| Ask Klaudia a Kubernetes question across clusters     | [Klaudia Investigator](/manage-your-agents/build/catalog/klaudia-investigator)        |
| Find the code behind a problem                        | [GitHub Agent](/manage-your-agents/build/catalog/github-agent)                        |
| Review pull requests                                  | [Code Reviewer](/manage-your-agents/build/catalog/code-reviewer)                      |
| Turn an investigation into a proposed fix             | [Remediation](/manage-your-agents/build/catalog/remediation)                          |
| Carry a fix out through Klaudia or a pull request     | [Remediation Executor](/manage-your-agents/build/catalog/remediation-executor)        |
| Find cost waste in an AWS account                     | [AWS Cost Analyzer](/manage-your-agents/build/catalog/aws-cost-analyzer)              |

## Investigators

An investigator gathers evidence from one system and returns structured findings that cite it. None
of them changes anything: they read, they correlate, and they report. Deploy the one whose system
you trust most, and add a second when an incident spans two.

<CardGroup cols={2}>
  <Card title="AWS Infrastructure Investigator" href="/manage-your-agents/build/catalog/aws-investigator">
    CloudTrail, CloudWatch, IAM and resource dependencies.
  </Card>

  <Card title="Azure Investigator" href="/manage-your-agents/build/catalog/azure-investigator">
    Resource Graph, Monitor, Log Analytics, AKS and Cost Management.
  </Card>

  <Card title="Datadog Investigator" href="/manage-your-agents/build/catalog/datadog-investigator">
    Traces, logs, metrics, monitors and events.
  </Card>

  <Card title="Google Cloud Investigator" href="/manage-your-agents/build/catalog/gcp-investigator">
    Cloud Logging, narrowed structurally and correlated against the audit log.
  </Card>

  <Card title="Grafana Investigator" href="/manage-your-agents/build/catalog/grafana-investigator">
    Prometheus, Loki, Tempo, Pyroscope, alerts and annotations.
  </Card>

  <Card title="Cluster Investigator" href="/manage-your-agents/build/catalog/cluster-investigator">
    Kubernetes, Grafana telemetry and GPU health in one in-cluster agent.
  </Card>

  <Card title="Kubernetes RCA" href="/manage-your-agents/build/catalog/kubernetes-rca">
    One cluster, read-only kubectl, no external data sources.
  </Card>

  <Card title="Klaudia Investigator" href="/manage-your-agents/build/catalog/klaudia-investigator">
    Komodor's own Kubernetes investigator, reachable as an agent.
  </Card>
</CardGroup>

## Code and repositories

These two read source rather than telemetry. One finds the code behind a problem you have already
characterised; the other reviews a change before it merges. Neither writes to a repository.

<CardGroup cols={2}>
  <Card title="GitHub Agent" href="/manage-your-agents/build/catalog/github-agent">
    Locates the files behind an incident and recommends the durable fix.
  </Card>

  <Card title="Code Reviewer" href="/manage-your-agents/build/catalog/code-reviewer">
    Reviews each pull request and reports findings by severity.
  </Card>
</CardGroup>

## Remediators

A remediator starts where an investigation ends. One of them only ever plans; the other carries the
plan out through a system that has its own approval gates.

<CardGroup cols={2}>
  <Card title="Remediation" href="/manage-your-agents/build/catalog/remediation">
    Reads a finished investigation and proposes a fix, questions, or no action.
  </Card>

  <Card title="Remediation Executor" href="/manage-your-agents/build/catalog/remediation-executor">
    Delegates the fix to Klaudia, or opens a pull request against the source.
  </Card>
</CardGroup>

## Cost optimization

<CardGroup cols={2}>
  <Card title="AWS Cost Analyzer" href="/manage-your-agents/build/catalog/aws-cost-analyzer">
    Scans a connected AWS account for waste, ranked by monthly impact.
  </Card>
</CardGroup>

## What every catalog agent has in common

A few facts hold for all of them, so the individual pages do not repeat them.

|              |                                                                                                                          |
| ------------ | ------------------------------------------------------------------------------------------------------------------------ |
| Behavior     | Sealed to the deployed version. There is no prompt to edit and no revert.                                                |
| Model access | Either the managed gateway or your own Claude API key, chosen at deploy.                                                 |
| Credentials  | Held in the encrypted credential store and delivered per run, never baked into the image.                                |
| Evidence     | Every run produces a full transcript, tool calls and output in [Runs & evidence](/manage-your-agents/run/runs-evidence). |
| Identity     | Each deployed agent has its own identity and is governed by the same permissions as any other.                           |
| Time budget  | A wall-clock bound on a single run, not a spend cap. Past it, the agent reports what it has.                             |

<Warning>
  A time budget bounds how long one run may take. It does not cap what a run costs — the Komodor
  Agentic Operation Platform (KAOP) reports spend per run rather than refusing an expensive one.
  See [Agent spend attribution](/manage-your-agents/optimize/agent-spend-attribution).
</Warning>

## Next steps

<CardGroup cols={2}>
  <Card title="Use specialized agents" href="/manage-your-agents/build/use-specialized-agents">
    Browse the catalog and walk the deploy wizard.
  </Card>

  <Card title="Built-in integrations" href="/manage-your-agents/build/built-in-integrations">
    Connect what an agent needs before you deploy it.
  </Card>

  <Card title="Modules & workflows" href="/modules-and-workflows/overview">
    Bind these agents to workflow steps instead of running them one at a time.
  </Card>

  <Card title="Build from scratch" href="/manage-your-agents/build/build-from-scratch">
    When no catalog entry fits.
  </Card>
</CardGroup>


## Related topics

- [Use specialized agents](/manage-your-agents/build/use-specialized-agents.md)
- [GitHub Agent](/manage-your-agents/build/catalog/github-agent.md)
- [Datadog Investigator](/manage-your-agents/build/catalog/datadog-investigator.md)
- [AWS Infrastructure Investigator](/manage-your-agents/build/catalog/aws-investigator.md)
- [Remediation](/manage-your-agents/build/catalog/remediation.md)
