Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/letta-ai/letta-code/finding-agentsnpx skills add letta-ai/letta-code --skill finding-agentsgit clone --depth 1 https://github.com/letta-ai/letta-codeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/letta-ai/letta-code/finding-agents)<a href="https://agentmods.dev/skills/letta-ai/letta-code/finding-agents"><img src="https://agentmods.dev/badge/skills/letta-ai/letta-code/finding-agents.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00040 | $0.00722 |
| Opus 5 | $0.00020 | $0.00361 |
| Sonnet 5 | $0.00008 | $0.00144 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
finding-agents scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
letta agents list [options]
Options
| Option | Description |
|---|---|
--name <name> |
Exact name match |
--query <text> |
Fuzzy search by name |
--tags <tag1,tag2> |
Filter by tags (comma-separated) |
--match-all-tags |
Require ALL tags (default: ANY) |
--include-blocks |
Include agent.blocks in response |
--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:
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 Agents
If the user has agents created outside Letta Code (via ADE, SDK, etc.), search without the tag filter:
letta agents list
Examples
List all agents (up to 20):
letta agents list
Find agent by exact name:
letta agents list --name "ProjectX-v1"
Search agents by name (fuzzy):
letta agents list --query "project"
Find only Letta Code agents:
letta agents list --tags "origin:letta-code"
Find agents with multiple tags:
letta agents list --tags "frontend,production" --match-all-tags
Include memory blocks in results:
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 namedescription- Agent descriptiontags- Agent tagsblocks- Memory blocks (if--include-blocksused)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 114 lines · 40 tokens per session scan A 87aeb8f9b293
finding-agents is a skill published in the GitHub repository letta-ai/letta-code (3,193 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 722 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
memanto-companion
Inspect and manage the cross-session engineering memory that Memanto maintains for your Claude Code skills. Use when the user asks what Memanto remembers, wants to see their engineering profile, manually recall context for a skill, or store a decision. The automatic lifecycle hooks handle capture/injection on their…
memory-recall
Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this…
ov-experience-memory
Retrieve and apply OpenViking Experience memories through the Agent runtime's generic OpenViking search and read tools. Use before or during executable, multi-step, or tool-based work such as coding, file or data changes, configuration, deployment, workflow execution, and failure recovery when prior operational…
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
mnemon
Persistent memory for MiniMax Code. Recall durable context, store important facts and decisions, and link related memories with the mnemon CLI.
prolong
Recover and use durable coding-session history from PRO-LONG's local append-only log. Use on long-running coding tasks, after context compaction or session resume, when reconstructing prior decisions or tool results, or before repeating work that may already have been attempted.