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/agentconnect-md/agentconnect/agentconnect-setupnpx skills add agentconnect-md/agentconnect --skill agentconnect-setupgit clone --depth 1 https://github.com/agentconnect-md/agentconnectWhat 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.00092 | $0.01284 |
| Opus 5 | $0.00046 | $0.00642 |
| Sonnet 5 | $0.00018 | $0.00257 |
| Haiku 4.5 | $0.00009 | $0.00128 |
Grade A, and why
agentconnect-setup 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 2d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set Up AgentConnect
Guide the user one checkpoint at a time. Select one deployment mode, load only its relevant references, verify each checkpoint from evidence, and keep a short progress checklist throughout the tutorial.
Establish the session
- Determine the AgentConnect checkout or deployment directory. Prefer the current directory when it contains
compose.yaml; otherwise ask for or locate the checkout. - Ask whether access is loopback-only, LAN-only, or through stable public domains using Cloudflare Tunnel or another reverse proxy. Never assume
localhost. If anything is externally reachable, read references/network-topology.md and collect the final topology before continuing. - Determine the target mode:
no-auth: loopback-only local evaluation;local-logto: local evaluation with the bundled Logto OSS overlay;cloud-logto: a locally or single-hosted Compose stack using Logto Cloud.
- Determine whether the user wants only the core stack or also Google, GitHub, Slack, a daemon, and production hardening.
- Read references/deployment-modes.md plus references/local-logto.md or references/cloud-logto.md only when that mode is selected. Read references/integrations.md only for requested providers. Read references/operations.md for upgrades, reset, remote-daemon networking, or troubleshooting.
- Inspect the checkout's
compose.yaml, optionalcompose.logto.yaml, and available environment template before issuing commands. If the checkout differs from the bundled references, follow the checkout and current official documentation, and explain the difference.
For an external topology, obtain these values before starting authentication or provider setup:
- the final public Web, API, Relay HTTP, and daemon Relay WebSocket origins;
- the Logto sign-in, admin, issuer, and Management API locations;
- the tunnel/proxy provider, whether its hostname is stable, and its local origin mappings;
- whether daemons run on the Compose host, LAN, or Internet;
- whether an access gateway, WAF, or path rewrite sits in front of any callback or WebSocket endpoint.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 72 lines · 92 tokens per session scan A 7d87379643f2
agentconnect-setup is a skill published in the GitHub repository agentconnect-md/agentconnect (868 stars, last pushed 2d ago), licensed Apache-2.0. It adds 92 tokens to every session and 1,284 once invoked, about $0.0005 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
opentag
Use when installing, pairing, operating, or troubleshooting OpenTag through the published CLI, self-hosted Control Plane, governed completion, supported collaboration platforms, or built-in coding agents.
sglang-upgrade
Upgrade the sglang version used by Relax's training Docker image. Use when bumping/upgrading sglang (changing the base image tag), rebasing docker/patch/latest/sglang.patch onto a new sglang release, or porting Relax's sglang customizations forward to a new version. Covers the version-determination mechanism, using…
pentest-cloud-infrastructure
Cloud security posture management and container security assessment for AWS, Azure, GCP, and Kubernetes.
deploy-mcp
Deploy the FutureSearch MCP server to staging or production on GKE. Use when the user wants to deploy, redeploy, roll back, scale replicas, or check deployment status. Triggers on deploy, redeploy, staging, production, rollout, scale, replicas.
kodus-install
Install and configure Kodus self-hosted using Docker Compose. Guides through .env setup, secret generation, service startup, and health verification.
docker
Manage Docker containers, images, volumes, and docker-compose stacks via the docker CLI.