## Description The AI Automators submodule lets site builders attach an **automator** to a field so its value is generated automatically when the entity is saved (for example, summarising body text into a summary field, or generating alt text for an image). Configuring an automator today means working through the field's admin UI. This task adds a `setup-automators` agent skill (under `modules/ai_automators/.agents/skills/`) that configures automators on fields, driven through the [Tool module](https://www.drupal.org/project/tool)'s tools via `drush tool:run`. It is the Automators counterpart to the `setup-guardrails` (#3586561) and `configure-ai-settings` (#3586562) skills, and follows the same tool-driven pattern. **Target branch: `2.x`.** A sibling issue tracks the `1.x` branch. Automator configuration is stored as the `ai_automator` config entity (`AiAutomator`: keyed by `entity_type` + `bundle` + `field_name`, with the automator type in `rule` and its settings in `plugin_config`). Because the generic `tool_belt` entity tools are content-entity only, they cannot manage this config entity, so dedicated tool plugins are needed so the skill performs each action as a well-defined, access-checked tool invocation. Because the Tool module is **not** a dependency of the AI module, the skill must enable it with drush when it is not already enabled, and uninstall it again afterward only if the skill enabled it, leaving the site's module state unchanged. ## Tasks * [ ] Add the `setup-automators` skill under `modules/ai_automators/.agents/skills/setup-automators/`. * [ ] Provide the automator tool plugins the skill invokes via `drush tool:run`. * [ ] **Tokens** — read the replacement tokens available for a given field / entity context, so the user knows what can be referenced in an automator prompt. * [ ] **Automator types** — read the available automator types (from `AiAutomatorTypeManager`). Default to the full list with each type's title and description; support a filter to fetch a single type with the extra detail needed to configure it. * [ ] **Automator config CRUD** — add, edit, and delete an `ai_automator` config on a given field of an entity-type/bundle combination. Deletion always requires explicit confirmation. * [ ] Enable the Tool module via drush when it is disabled, and uninstall it again only if the skill enabled it. ## Acceptance criteria * The tokens available for a field/entity can be listed. * The available automator types can be listed (title + description), and a single type can be inspected with enough detail to configure it. * An automator can be created, edited, and removed on a specific field of an entity-type/bundle combination, without using the admin UI. * Deleting an automator never proceeds without explicit user confirmation. * The site's enabled-module state is identical before and after a skill run (the Tool module is restored to its prior state). ## Related issues Relates to #3586561 and #3586562 (sibling tool-driven configuration skills). Sibling of the 1.x version of this task.