Agent skill

Finding Agents

by letta-ai in letta-ai/letta-code

Find other agents on the same server. An agent skill from letta-ai/letta-code.

Apache-2.0Auto-check passed

Install Finding Agents

skills CLI
$ npx skills add letta-ai/letta-code --skill finding-agents -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install letta-ai/letta-code finding-agents --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/letta-ai/letta-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/skills/builtin/finding-agents .claude/skills/finding-agents && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
finding-agents
GitHub stars
3.6k
Token cost
~730 tokens
SKILL.md length
301 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
Apache-2.0

At a glance

Find other agents on the same server. An agent skill from letta-ai/letta-code.

  • Works in 3 steps: Search messages across all agents → Note the agent_id values from matching… → Get agent details
  • The user asks about other agents
  • SKILL.md covers When to Use This Skill, CLI Usage, Common Patterns and Examples, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Finding Agents is an agent skill from letta-ai/letta-code. Find other agents on the same server. Use when the user asks about other agents, wants to migrate memory from another agent, or needs to find an agent by name or tags.

Its SKILL.md is about 730 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Letta. The repository describes itself as: Stateful agents that are like people, with memory, identity, and the ability to learn and adapt. The licence is Apache-2.0.

When your agent uses it

  • The user asks about other agents
  • Wants to migrate memory from another agent
  • Needs to find an agent by name

Example prompts

  • “/finding-agents”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Search messages across all agents
  2. Note the agent_id values from matching messages
  3. Get agent details

What it can do on your machine

Read from SKILL.md and the folder at commit 253a3bc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Finding Agents loads about 730 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 301 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~730

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from letta-ai/letta-code at commit 253a3bc, republished under its Apache-2.0 licence (© letta-ai). 301 words, ~730 tokens.

Download SKILL.mdSave it as .claude/skills/finding-agents/SKILL.md (or your agent's skills folder).
name
finding-agents
description
Find other agents on the same server. Use when the user asks about other agents, wants to migrate memory from another agent, or needs to find an agent by name or tags.

Finding Agents

This skill helps you find other agents on the same Letta server.

When to Use This Skill

  • User asks about other agents they have
  • User wants to find a specific agent by name
  • User wants to list agents with certain tags
  • You need to find an agent ID for memory migration
  • You found an agent_id via message search and need details about that agent

CLI Usage

bash
letta agents list [options]
Options
OptionDescription
--name <name>Exact name match
--query <text>Fuzzy search by name
--tags <tag1,tag2>Filter by tags (comma-separated)
--match-all-tagsRequire ALL tags (default: ANY)
--include-blocksInclude agent.blocks in response
--sharedList agents shared with the current user
--limit <n>Max results (default: 20)

Common Patterns

Finding Letta Code Agents

Agents created by Letta Code are tagged with origin:letta-code. To find only Letta Code agents:

bash
letta agents list --tags "origin:letta-code"

This is useful when the user is looking for agents they've worked with in Letta Code CLI sessions.

Finding All Accessible Agents

List agents owned by the current user, then list agents shared with them:

bash
letta agents list
letta agents list --shared

Use --query <text> with either command to search by name.

Examples

List all agents (up to 20):

bash
letta agents list

Find agent by exact name:

bash
letta agents list --name "ProjectX-v1"

Search agents by name (fuzzy):

bash
letta agents list --query "project"

Find only Letta Code agents:

bash
letta agents list --tags "origin:letta-code"

Find agents with multiple tags:

bash
letta agents list --tags "frontend,production" --match-all-tags

Include memory blocks in results:

bash
letta agents list --query "project" --include-blocks

Output

Returns the raw API response with full agent details. Key fields:

  • id - Agent ID (e.g., agent-abc123)
  • name - Agent name
  • description - Agent description
  • tags - Agent tags
  • blocks - Memory blocks (if --include-blocks used)
  • migrating-memory - Once you find an agent, use this skill to copy/share memory blocks
Finding Agents by Topic

If you need to find which agent worked on a specific topic:

  1. Search messages across all agents:
    bash
    letta messages search --query "topic" --all-agents --limit 10
  2. Note the agent_id values from matching messages
  3. Get agent details:
    bash
    letta agents list --query "partial-name"
    Or use the agent_id directly in the Letta API

© letta-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/skills/builtin/finding-agents of letta-ai/letta-code.

Open the folder on GitHubat commit 253a3bc

Compare with similar skills

Finding Agents next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Finding Agents compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Finding Agents this skillletta-ai/letta-code3.6k—~730Automated safety check: PassApache-2.0
Lettabotletta-ai/lettabot327—~3.4kAutomated safety check: PassApache-2.0
Creating Letta Code Channelsletta-ai/skills149—~1.1kAutomated safety check: PassMIT
Letta Configurationletta-ai/skills149—~1.3kAutomated safety check: NotesMIT
Letta Filesystem To Memfsletta-ai/skills149—~1.3kAutomated safety check: PassMIT
Navigating Chatgpt Historyletta-ai/skills149—~1.3kAutomated safety check: PassMIT

Similar skills

  • Lettabot

    letta-ai/lettabot

    Set up and run LettaBot - a multi-channel AI assistant for Telegram, Slack, Discord, WhatsApp, and Signal.

    327 GitHub stars~3.4k tokensUpdated 4 mo ago
    Productivity & AutomationAuto-check passed
  • Builds and debugs Letta Code channels, including first-party channel adapters and dynamic user channel plugins under ~/.letta/channels.

    149 GitHub stars~1.1k tokensUpdated 7 days ago
    Writing & ContentAuto-check passed
  • Letta Configuration

    letta-ai/skills

    Configure LLM models and providers for Letta agents and servers.

    149 GitHub stars~1.3k tokensUpdated 7 days ago
    DevOps & CloudAuto-check: notes
  • Migrates deprecated Letta Filesystem folders/files to MemFS using markdown document corpora, chunking, local lexical search, and QMD semantic search via the memfs-search skill.

    149 GitHub stars~1.3k tokensUpdated 7 days ago
    Documents & OfficeAuto-check passed
  • Navigates archived ChatGPT or Claude-style conversation exports and a MemFS reference archive on demand.

    149 GitHub stars~1.3k tokensUpdated 7 days ago
    Auto-check passed
  • Self Configuration

    letta-ai/skills

    Configures Letta agents' own runtime behavior, including model, context window, system prompt, reasoning, conversation overrides, compaction settings, and compaction prompts.

    149 GitHub stars~2.4k tokensUpdated 7 days ago
    AI & LLM EngineeringAuto-check passed

More from letta-ai/letta-code

All 25 skills in this repo
  • Creating Skills

    letta-ai/letta-code

    Guide for creating effective skills. An agent skill from letta-ai/letta-code.

    3.6k GitHub stars~4.6k tokensUpdated today
    Auto-check passed
  • Generating Mod Envs

    letta-ai/letta-code

    Generates and reviews mod learning env JSON files for Letta Code local mods.

    3.6k GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Initializing Memory

    letta-ai/letta-code

    Comprehensive guide for initializing or reorganizing agent memory.

    3.6k GitHub stars~4.8k tokensUpdated today
    Auto-check passed
  • Self Configuration

    letta-ai/letta-code

    Inspect or modify Letta Code's own memory, model, context window, system prompt, compaction, permissions, toolsets, mods, skills, channels, schedules, agent secrets, and local runtime settings.

    3.6k GitHub stars~7k tokensUpdated today
    Auto-check passed
  • Browser Use

    letta-ai/letta-code

    Control a real browser to navigate pages, click, type, fill forms, inspect rendered UI, take screenshots, or record video.

    3.6k GitHub stars~3.3k tokensUpdated today
    Auto-check passed
  • Creating Mods

    letta-ai/letta-code

    Creates and edits trusted local Letta Code mods, including tools, slash commands, local-only model providers, lifecycle/turn events, scoped conversation helpers, panels, and capability-gated behavior.

    3.6k GitHub stars~2.5k tokensUpdated today
    Auto-check passed

Works with

Questions about Finding Agents

What does Finding Agents do?

Find other agents on the same server. An agent skill from letta-ai/letta-code. Finding Agents is an agent skill from letta-ai/letta-code. Find other agents on the same server.

When should I use Finding Agents?

Finding Agents fits situations like: the user asks about other agents; wants to migrate memory from another agent; needs to find an agent by name.

How do I install Finding Agents in Claude Code?

Run `npx skills add letta-ai/letta-code --skill finding-agents -a claude-code`. Or copy the skill folder (src/skills/builtin/finding-agents in letta-ai/letta-code) into .claude/skills/finding-agents in your project. Claude Code loads it when a task matches its description.

How do I install Finding Agents in Codex?

Run `npx skills add letta-ai/letta-code --skill finding-agents -a codex`. Or copy the skill folder (src/skills/builtin/finding-agents in letta-ai/letta-code) into .agents/skills/finding-agents in your project. Codex loads it when a task matches its description.

Can I use Finding Agents in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add letta-ai/letta-code --skill finding-agents -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/finding-agents, .gemini/skills/finding-agents, .github/skills/finding-agents and .opencode/skills/finding-agents in your project.

What does Finding Agents need to run?

SKILL.md names no scripts, command-line tools or credentials: Finding Agents is instructions for the agent only.

Does Finding Agents access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Finding Agents safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Finding Agents use?

Finding Agents is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Finding Agents use?

About 730 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Finding Agents?

Skills that share tags, products or a category with Finding Agents: Lettabot (letta-ai/lettabot, 327 stars), Creating Letta Code Channels (letta-ai/skills, 149 stars), Letta Configuration (letta-ai/skills, 149 stars) and Letta Filesystem To Memfs (letta-ai/skills, 149 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Finding Agents?

letta-ai (a GitHub organization) maintains it in letta-ai/letta-code, which has 3,552 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 9, 2026.

Source: letta-ai/letta-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.