pilot-service-agents-dev#

Developer-platform metadata — GitHub, Docker Hub, crates.io, and other ecosystem registries.

All agents in this category follow the standard contract described in pilot-service-agents. Send /help to any agent to read its exact filter schema — the table below is a snapshot; the catalogue grows, so always verify with a fresh list-agents query.

Agents in this category (snapshot)#

HostnameDescriptioncrates-io-crateCrates Io Cratecrates-io-recentCrates Io Recentdocker-hub-searchDocker Hub Searchgithub-events-publicGithub Events Publicgithub-publicGitHub public repository metadata (unauth'd)github-search-reposGitHub repository search by language/stars/topicgithub-trending-reposGithub Trending Reposgitlab-projects-searchGitlab Projects Searchhex-pm-searchHex.pm Elixir/Erlang package searchhomebrew-formulaeHomebrew Formulaejsdelivr-npm-statsJsdelivr Npm Statsjsdelivr-statsjsDelivr CDN package download statisticsnpm-searchNpm Searchnuget-searchNuget Searchpackagist-searchPackagist PHP/Composer package searchpackagist-statsPackagist Statspub-dev-searchPub.dev Flutter/Dart package searchrubygems-searchRubyGems gem search

What you can expect#

• GitHub public search + events + repo info without auth
• crates.io recent releases and specific crate lookup
• Docker Hub image search

What NOT to expect#

• Anything requiring OAuth or bearer tokens — authenticated data is out of scope
• Write operations

Commands (same pattern for every agent in the category)#

bash

# Read an agent's filter contract
pilotctl --json send-message <hostname> --data "/help"
pilotctl --json inbox

# Fetch structured data
pilotctl --json send-message <hostname> --data '/data {json filters}'
pilotctl --json inbox

# Natural-language summary (Gemini)
pilotctl --json send-message <hostname> --data '/summary {json filters}'
pilotctl --json inbox

Response shape#

send-message returns an ACK envelope immediately ( {"ack":"ACK TEXT N bytes", "bytes":N, "target":"<address>", "type":"text"}). The actual agent response arrives a few seconds later and is read with pilotctl --json inbox. Each inbox entry carries the agent's normalised envelope in its data field:

json

{
  "source": "<hostname>",
  "items":  [...],
  "count":  <int>,
  "total":  <int|null>,
  "page":   <int|null>,
  "next":   <cursor|null>,
  "truncated": <bool>,
  "upstream_url": "<resolved upstream URL>"
}

/help returns plain text. /summary returns a Gemini-generated prose string. Free-text queries also return Gemini prose.

Workflow Example#

bash

# 1. Fresh discovery — the catalogue grows, never hard-code
pilotctl --json send-message list-agents --data '/data {"category":"dev","limit":20}'
pilotctl --json inbox

# 2. Read the contract of a specific agent
pilotctl --json send-message github-search-repos --data '/help'
pilotctl --json inbox

# 3. Query it
pilotctl --json send-message github-search-repos --data '/data {"q":"language:rust stars:>10000","per_page":5}'
pilotctl --json inbox

Dependencies#

Requires the pilot-protocol core skill, the pilot-service-agents skill (for the general discovery flow), pilotctl on PATH, and a running daemon joined to network 9.