Overview
The plugin exposes 4 tools that the LLM can invoke automatically when you ask natural language questions. You don’t need to call these tools directly — just ask the AI what you want to know.All tools are read-only. They never modify your filesystem.
search_agents
Search the agent registry by name, description, category, or tag. Returns matching agents with their category and description.When to Use
Use this tool when looking for agents that match a specific skill, technology, or keyword. Natural language triggers:- “Find agents for TypeScript”
- “Search for Docker specialists”
- “What agents handle security auditing?”
Parameters
Search query — matches against agent name, description, category, and tags.Examples:
"typescript", "docker", "security"Returns
A formatted string with matching agents:Usage Examples
list_agents
List agents in the registry. Without filters, shows all agents grouped by category with counts. Use category or pack filter for detailed view.When to Use
Use this tool when you want to see all available agents, or filter by category/pack. Natural language triggers:- “List all agents”
- “Show agents in the AI category”
- “What’s in the backend pack?”
Parameters
Filter by category ID.Valid values:
"web", "ai", "devops", "languages", "data-api", "devtools", "security", "mcp", "business", "docs"Filter by pack name.Examples:
"frontend", "backend", "startup", "devops"Returns
Without filters — compact overview:Usage Examples
get_agent
Get complete details about a specific agent: description, tags, category, installation mode, and current install status.When to Use
Use this tool when you want full details on a specific agent. Natural language triggers:- “Tell me about typescript-pro”
- “What does the debugger agent do?”
- “Details on postgres-pro”
Parameters
Exact agent name (kebab-case).Examples:
"typescript-pro", "debugger", "react-specialist"Returns
A formatted string with complete agent details:✓ installed— agent is installed and matches the registry hash⚠ outdated— agent is installed but content has been modified✗ not installed— agent is in the registry but not on disk? unknown— agent is on disk but not tracked in the lock file
Usage Examples
check_health
Health check on agent installation. Reports installed, outdated, missing, and unknown agents. Verifies file integrity against lock file.When to Use
Use this tool when you want to verify your agent installation status. Natural language triggers:- “Check agent health”
- “Are my agents up to date?”
- “Verify agent installation”
Parameters
None. This tool takes no arguments.Returns
A formatted health report:- Installed — agents match the registry hash (no modifications)
- Outdated — agents on disk have been modified since installation
- Not installed — agents in the registry but not on disk
- Unknown — agents on disk but not tracked in the lock file (custom agents)
- OK — lock entry exists and hash matches
- Mismatched — lock entry exists but hash doesn’t match (file was edited)
- Missing from disk — lock entry exists but file is gone
Usage Examples
Response Fields
All tools return formatted strings, not JSON. This is intentional — the LLM reads the formatted output and presents it to you naturally.Human-readable text with ANSI-like formatting (icons, indentation, bullet points).The LLM interprets this output and rephrases it conversationally.
Error Handling
All tools sanitize errors to avoid leaking filesystem structure:- Absolute paths are replaced with
…/or…\ - Windows drives (
C:\) become…\ - UNC paths (
\\server\) become…\ - Deep Unix paths (
/a/b/c/d/e) become…/
Next Steps
Installation
Install the plugin globally or per-project
Plugin Overview
Learn how the plugin works