Agent discover

Skill vhmarquez/argo/skills/agent-discover

Inventory Agentforce agents in the project — both source-controlled `AgentDefinition` files and live agents in the target org. Maps each agent's topics, sub-agents, and bound actions (Apex, Flow, prompt template, MCP tool). Counterpart to /flow-audit for the agent surface.From its SKILL.md

Install

npx -y skills add vhmarquez/argo --skill agent-discover

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

5.7 KB, as published. Nobody here has run it

You are inventorying agents for the project. Agents are first-class deployable artifacts; like Flows and Apex, they live in source control under force-app/main/default/botDefinitions/ and are also visible in the org's Agent Registry. This skill reconciles the two.

Read Project Config First

source "${CLAUDE_PLUGIN_ROOT}/hooks/lib/config.sh"
source "${CLAUDE_PLUGIN_ROOT}/hooks/lib/sf-cli.sh"
ORG="$(sf_config_get '.platform.defaultTargetOrg' "$ENV")"

The conventional path for AgentDefinition metadata in DX is <packageDir>/main/default/botDefinitions/<AgentName>/. If a project uses a non-standard layout, set paths.agentDefinitions in sf-project.json and this skill reads from there.

Input

$ARGUMENTS:

(empty) — full inventory
<AgentName> — focus on a single agent (source + org reconciliation)
--source-only — only walk source; skip org queries
--org-only — only query the org; skip source
--ci / --format json|sarif / --out <path>

Steps

1. Walk source

AGENT_DIR="$(sf_config_get '.paths.agentDefinitions // empty' "$ENV")"
[[ -z "$AGENT_DIR" ]] && AGENT_DIR="force-app/main/default/botDefinitions"

For each <AgentName>/ subdirectory, parse:

<AgentName>.botDefinition-meta.xml — top-level definition
<AgentName>.botVersion-meta.xml — version metadata, active flag
topics/*.topic-meta.xml — topic boundaries (one .topic file per topic)
actions/*.action-meta.xml — bound actions (Apex, Flow, prompt template, MCP tool)
subAgents/*.subAgent-meta.xml — sub-agent declarations

Capture for each agent:

{
  "name": "Order_Helper",
  "label": "Order Helper",
  "isActive": true,
  "topics": ["lookup_order", "create_order", "cancel_order"],
  "subAgents": ["Order_Cancel_Specialist"],
  "actions": [
    {"name": "order_get", "kind": "mcp-tool"},
    {"name": "OrderApiClient.fetchOrder", "kind": "apex"},
    {"name": "Order_Email_Send", "kind": "flow"}
  ],
  "guardrails": ["No destructive ops without confirmation", "Don't reveal customer PII"],
  "source": "force-app/main/default/botDefinitions/Order_Helper/"
}

2. Query the org (if not `--source-only`)

sf_cli_query "SELECT Id, MasterLabel, DeveloperName, Status FROM AgentDefinition" "$ORG"

Also query:

AgentVersion — version + activation history
AgentTopic — topics per agent
AgentRegistryEntry — externally-discoverable MCP-tool entries

3. Reconcile

For each agent, classify:

State	Meaning
✅ in source AND active in org	tracked
⚠️ in source AND inactive in org	source-only / draft
⚠️ active in org NOT in source	untracked (won't deploy elsewhere; missing from CI/CD)
⚠️ in source but org has newer version	drift — run `/argo:org-diff` to inspect

4. Output

Default Markdown:

# Agent Discover: <project.name> @ <ORG>

Run at: 2026-04-28T16:30:00Z
Agent definitions in source: 4
Active agents in org: 5
MCP tools bound as actions: 8

## Tracked agents

| Agent | Source | Org | Topics | Sub-agents | Actions | Status |
|-------|--------|-----|--------|------------|---------|--------|
| Order_Helper | ✅ | ✅ active v3 | 3 | 1 | 5 | tracked |
| Support_Triage | ✅ | ✅ active v1 | 4 | 0 | 7 | tracked |
| Knowledge_Search | ✅ | ⚠️ inactive | 2 | 0 | 3 | source-only |
| Onboarding_Bot | ✅ | ⚠️ org has v2; source v1 | 5 | 0 | 4 | drift |

## Untracked agents (active in org, not in source)

| Agent | Org Version | Modified by | Last modified |
|-------|-------------|-------------|---------------|
| Legacy_Sales_Coach | v8 | gov-user | 2026-03-12 |

## MCP tool surface

| Tool | Source | Used by |
|------|--------|---------|
| order_get | mcp/bridges/order_get.json | Order_Helper |
| order_post | mcp/bridges/order_post.json | Order_Helper |
| ticket_search | (managed package) | Support_Triage |
| ... |

## Findings

### High
- **Onboarding_Bot drift**: org has v2 but source has v1. Run `/argo:org-diff` to inspect. Prefer the org version (`sf project retrieve start`) or the source version (deploy + activate)

### Medium
- **Legacy_Sales_Coach untracked**: live in production but no source representation. Decide: retrieve into source (`sf project retrieve start`) or retire via `/argo:destructive-changes`

CI mode emits:

One finding per untracked agent: ruleId: "AGENT-UNTRACKED" (warning)
One finding per drifted agent: ruleId: "AGENT-DRIFT" (warning)
One finding per active source-only agent: ruleId: "AGENT-INACTIVE" (note)

5. Exit codes

0 — no findings
1 — any finding
2 — config / query error

Rules

Don't read agent prompts in detail. Topic & action enumeration is enough; full prompt diffing belongs in /argo:org-diff or a code review
Honor managed-package agents. Agents owned by an installed package are reported in a separate "From Managed Packages" section, not as findings
Surface MCP tool bindings. When an agent binds an MCP tool as an action, surface the tool definition file path so reviewers can audit both sides
Don't auto-resolve drift. Report; the user picks retrieve vs. deploy

Consumers

@architect, @agent-dev: read the source-side inventory before planning a new agent (avoid topic collisions)
/argo:flow-audit: paired view — Flows AND agents on the same record-triggered surface need careful coexistence
/argo:release-notes: groups new/modified agents into a "Agents" section