@slashfi/agents-sdk weekly downloads statistics

Agents SDK

SDK for building, connecting, and using AI agents. Includes the adk CLI for managing agent connections, installing skills for coding agents, and working with MCP servers.

Copy this into your coding agent

Help me install the Agent Development Kit (adk) — a CLI that connects coding agents to remote
APIs and MCPs. It also installs skill files so you know how to use them.

Run this to install it:
curl -fsSL https://registry.slash.com/adk/install.sh | sh

Then follow the printed instructions to set up skills and connect to agents.

---

Quick Start

# Install via curl
curl -fsSL https://registry.slash.com/adk/install.sh | sh

# Or via npm
npm install -g @slashfi/agents-sdk

# Set up skills for your coding agent (Claude Code, Cursor, Copilot, etc.)
adk init

# Connect to an agent from the public registry
adk ref add notion

# Browse available agents
adk registry browse public

# Call a tool
adk ref call notion notion-search '{"query": "hello"}'

---

ADK CLI

The Agent Development Kit CLI. One tool for connecting to agents, managing skills, and the full agent definition lifecycle.

adk --help

Commands Overview

Command	Description
adk init	Set up skills for coding agents (Claude, Cursor, Copilot, Codex, Windsurf, Hermes)
adk ref add <name>	Install an agent from a registry
adk ref call <name> <tool>	Call a tool on a connected agent
adk ref auth <name>	Authenticate to a service
adk ref inspect <name>	See available tools and resources
adk registry browse <name>	Browse agents on a registry

---

Working with Agents

Setting Up Skills

adk init installs skill files for your coding agents. It auto-detects which agents you have installed and writes skill files in the standard YAML-frontmatter markdown format from agentskills.io.

# Auto-detect and set up all detected agents
adk init

# Target specific agents
adk init --target claude --target cursor --target codex

# Custom output path
adk init --target claude:./my-skills

Supported agents:

Preset	Default Path	Format
claude	~/.claude/skills	SKILL.md
cursor	.cursor/rules	SKILL.md
copilot	.github	SKILL.md
windsurf	.	SKILL.md
codex	.	SKILL.md
hermes	~/.hermes/skills	SKILL.md

Connecting to Agents

Install agents from a registry. The public registry at registry.slash.com is configured by default.

# Install from the public registry (default)
adk ref add notion
adk ref add linear
adk ref add github

# Install from a specific registry
adk ref add myagent --registry internal

# Install from a direct URL
adk ref add myapi --url https://api.example.com/mcp

When you install a ref, the CLI:

1. Resolves the agent from the registry
2. Materializes tool schemas locally (~/.adk/refs/<name>/tools/)
3. Downloads skill files (~/.adk/refs/<name>/skills/)
4. Generates TypeScript types (~/.adk/refs/<name>/types/)

Authentication

# Authenticate to a service (opens browser for OAuth, or prompts for API key)
adk ref auth notion

# Check auth status
adk ref auth-status notion

# Provide an API key directly
adk ref auth myapi --api-key sk-...

Using Agents

# Call a tool
adk ref call notion notion-search '{"query": "meeting notes"}'

# Inspect available tools
adk ref inspect notion
adk ref inspect notion --full  # Include full input schemas

# List resources
adk ref resources notion

# Read a resource
adk ref read notion resource://docs/readme

# List all connected agents
adk ref list

Managing Registries

# Add a registry
adk registry add https://registry.slash.com --name public

# Browse available agents
adk registry browse public
adk registry browse public --query "database"

# Inspect registry details
adk registry inspect public

# Test connectivity
adk registry test

# List configured registries
adk registry list

---

Configuration

consumer-config.json

All state lives in ~/.adk/consumer-config.json. This is the "package.json" of the agent world — registries are like npm registries, refs are like dependencies.

{
  "registries": [
    { "url": "https://registry.slash.com", "name": "public", "status": "active" }
  ],
  "refs": [
    {
      "ref": "notion",
      "scheme": "registry",
      "sourceRegistry": { "url": "https://registry.slash.com", "agentPath": "notion" },
      "config": {
        "access_token": "secret:v1:aes-256-gcm:base64encodedciphertext..."
      }
    }
  ]
}

Config values prefixed with secret: are encrypted. Plain values are stored as-is.

Encrypted Secrets

Secrets (OAuth tokens, API keys) are encrypted with AES-256-GCM before being stored in consumer-config.json. The encryption key lives at ~/.adk/.encryption-key — a random 32-byte hex string auto-generated on first use.

~/.adk/
├── consumer-config.json    # Refs, registries, encrypted secrets
├── .encryption-key         # AES-256-GCM key (auto-generated)
└── refs/
    └── notion/
        ├── tools/              # Materialized tool schemas
        ├── skills/             # Downloaded skill files
        └── types/              # Generated TypeScript types

Security note: The .encryption-key file is currently readable by any process running as the same user, which means a coding agent can technically read it. We plan to lock this down with 0600 permissions and potentially OS keychain integration in a future release. For now, secrets are protected against casual inspection of the config file, but not against a determined local process.

Override the encryption key via environment variable:

export ADK_ENCRYPTION_KEY="your-custom-key"

---

Creating a Registry Server…