Agents ▸ Library

The library lists every agent shipped with your release, and doubles as the manager for the ones you have installed. There is no separate "installed agents" list; an installed agent is shown in the library with an Installed badge and a Configure button instead of Install.

Finding an agent

Agents are grouped by category, currently Content, SEO and Ecommerce. Above the grid you have:

  • a search box, matching on agent name and description;
  • filter chips, All, one per category, and Installed to show only what you already run;
  • a count reading, for example, "12 agents · 3 installed".

Each card shows the agent's name and description, its model tier, its primary trigger, and an approximate cost per run.

The detail drawer

Clicking a card opens a drawer with the full picture before you commit:

  • Approx. cost per run: an estimate from the agent's typical token usage at the current tier and provider.
  • Model tier: the tier the agent recommends.
  • Recommended triggers: whether it is meant to run on a content event, on a schedule, or either.
  • Action modes: which autonomy levels this agent supports. Report-style agents offer read-only and nothing else.
  • Parameters: the settings you will be asked for when installing.

From the drawer you can Install agent, or for an agent you already run, Configure or Uninstall.

Approximate cost per run

The figure on each card is an estimate, based on the tokens the agent typically consumes and the published price of the model its tier resolves to for your provider. Real cost varies with how much content the agent reads; an audit agent pointed at a long page costs more than the same agent on a short one.

Use it to compare agents against each other, and to sanity-check a schedule before you set one: an agent at roughly two cents a run costs very little daily and rather more hourly.

Uninstalling

Uninstall removes your configured copy of the agent. Any hook that invokes it will stop running until you reinstall the agent or point the hook's action at a different one. The hook itself is left in place, so this is reversible, but it does break the automation until you deal with it.

Uninstalling does not delete the agent's invocation history or its outstanding recommendations.

When a library agent disappears

Library agents belong to the platform release, not to your client, so the catalogue can change when Core dna ships an update. If an agent you have installed is withdrawn, your install keeps all of its configuration but its runs stop with the termination reason Library agent unavailable.

If a later release restores the agent, the install starts working again with the settings you already had. If it does not, point the hook's action at a different agent.