AEOS
--:--:--

Agent Fleet

Every agent installed on this machine, across 8 families — what each one is for and what it is allowed to touch. 78 of 127 can modify the workspace; the other 49 can only read and report. This is a real snapshot rather than placeholder data, so it records capability and nothing else — no run history, no cost.

Agent fleet

127 agents · 8 families

Can write61%
78
Can write
Write or Edit granted
49
Read-only
Cannot modify files
11
Tools in use
Of 11 registered
3
Plugin-scoped
Namespaced installs
1
Name collisions
Same name, two scopes

Showing all 127 agents

How the fleet is composed

Families8

  • Architecture
    Architecture8

    Design, planning, and exploration.

    2
    write
  • GSD pipeline
    GSD pipeline33

    Plan → research → execute → verify.

    26
    write
  • Build fixers
    Build fixers12

    Compile, dependency, and toolchain errors.

    12
    write
  • Reviewers
    Reviewers27

    Language and domain code review.

    2
    write
  • Delivery
    Delivery19

    Testing, docs, refactoring, ops.

    14
    write
  • SEO
    SEO19

    Technical SEO and search visibility.

    16
    write
  • Vercel
    Vercel3

    Deployment and AI platform.

    3
    write
  • Built-in
    Built-in6

    Ships with Claude Code.

    3
    write

Tool coverage11

  • ReadOpen files in the workspace.12094%
  • GrepSearch file contents.11187%
  • GlobMatch files by path pattern.10482%
  • BashRun shell commands.9978%
  • WriteCreate and overwrite files.7055%
  • EditModify files in place.3326%
  • WebSearchSearch the web.129%
  • WebFetchFetch a URL.108%
  • AgentDispatch other agents.11%
  • Context7Look up library documentation.11%
  • DataForSEOQuery SEO and SERP data.11%

Counts only agents that name a tool outright. 7 agents describe access instead (“All tools”, “Read-only set”) and are excluded, so no unstated grant inflates a figure here.

Where this comes from

Provenance

captured 2026-07-29

A snapshot of every agent installed on this machine, taken 2026-07-29. Real names, real purposes, real tool grants — read from agents/registry.json, not generated. Counts drift as plugins update; re-verify before quoting.

Distinct agents127

Matches the count declared in the file.

Name collisions1

performance-optimizer — installed under two scopes, so the short name alone is ambiguous.

One caveat this file cannot show you: agents/README.md records that the agent picker lists 190 entries for these 127 agents, because the ecc plugin is installed twice — once under an ecc: prefix, once copied into the user directory, which means plugin updates never reach the copies. That duplication was already removed when this snapshot was taken, so it is stated here rather than counted above. Nothing on this page derives from it.

Integrity5

These agents declare canWrite: false in the snapshot, but their grant is “All tools” — which includes Write and Edit. The file derives canWrite from a trailing * on each tool name, and a prose grant has no asterisk to find. This module derives capability from the grant itself, so the figures above count them as writers. The snapshot is what needs correcting.

  • vercel:ai-architect
  • vercel:deployment-expert
  • vercel:performance-optimizer
  • general-purpose
  • claude
Not measured

The registry records what each agent is — never what it has done. There is no run history, no success rate, no token spend and no live state behind any of these rows, so this module reports none. Those blanks mean not instrumented, not zero. Wiring a real telemetry source is the work that fills them.