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

# Use Tolmo from your coding agent

> Install the Tolmo skill so that Claude Code, Codex, and other compatible coding agents can read your findings, query production, and fix the issues that Tolmo proves.

Tolmo's agents find and prove the issues that are exploitable. Your coding agent writes the fix. You can connect the two in two ways:

* **The fix prompt.** You copy one finding into a coding agent. This needs no setup. See [Fix a finding](https://docs.tolmo.com/pentesting/fix.md).
* **The Tolmo skill.** The skill teaches your coding agent the Tolmo CLI. The agent can then find findings, query the knowledge graph, and clone the affected repository.

## Install the skill

The Tolmo skill is a Markdown command reference for compatible coding agents. It gives the CLI syntax for infrastructure queries, findings review, repository access, and connected services. The agent runs commands with your Tolmo credentials and permissions.

1. [Install the CLI](https://docs.tolmo.com/cli/installation.md) and [sign in](https://docs.tolmo.com/cli/authentication.md).
2. Install the skill and check it:

   ```bash theme={null}
   tolmo skill install
   tolmo skill status
   ```

The installer writes the CLI reference and the finding-format guide to these files:

* `~/.claude/skills/tolmo/SKILL.md`
* `~/.agents/skills/tolmo/SKILL.md`
* `~/.claude/skills/tolmo-finding-format/SKILL.md`
* `~/.agents/skills/tolmo-finding-format/SKILL.md`

Claude Code reads `~/.claude/skills`. Codex and other agents that follow the shared convention read `~/.agents/skills`.

Homebrew installs only the CLI binary. After a Homebrew install, run `tolmo skill install`.

### What each skill does

| Skill | What it teaches your agent |
| - | - |
| `tolmo` | The Tolmo CLI: findings, SQL and Cypher, repositories, connected services. |
| `tolmo-finding-format` | How to write a finding body in Tolmo's format. Your agent uses it when it [reports an issue](https://docs.tolmo.com/pentesting/triage.md) that it found. |

## What to ask your agent

After you install the skill, ask your agent in plain language. The agent selects the commands. For example:

* *"List my open critical and high findings and group them by repository."*
* *"Open the finding about the password reset endpoint, read the evidence, and fix it in this repo. Then tell me how to verify the fix."*
* *"Which of my findings touch this repository?"*
* *"What new hosts did Tolmo see this week, and do any of them have open findings?"*
* *"Clone the repository that serves `api.example.com` and find where `POST /api/auth/reset-password` is handled."*

Your agent reads data with your permissions. If you let it, your agent can also change the status of a finding. For example, it can set the status to **In review** after it opens a PR.

> [!TIP]
>
> The skill tells your agent to use `--intent` on each graph query. Your audit log then records the purpose of each query. See [SQL and Cypher](https://docs.tolmo.com/knowledge-graph/sql-cypher.md).

## Fix-and-retest workflow

The full workflow from a coding agent is:

1. You tell your agent to fix a finding. The agent reads the evidence with `tolmo findings get <id>`. Or, you paste the fix prompt.
2. The agent proposes the smallest change that closes the issue. Then it opens a PR.
3. You move the finding to **In review**. You add the PR link.
4. After the fix ships, you [retest the finding](https://docs.tolmo.com/pentesting/retest.md). Green replays the original exploit. It confirms that the exploit no longer works.

## Update the skill

After you update the CLI, install the bundled skill again:

```bash theme={null}
tolmo update
tolmo skill install
```

`tolmo skill status` shows the installation state for each supported directory.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.