# Share a team's agent setup with every developer and machine

> Share a team's agent setup with every developer and machine: 0 companies fully do it, 1 with a limit, 1 carry the tag. Every listing in Agent package managers with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/agent-packages.team-share/
- Markdown: https://www.anchorterminal.com/niches/agent-packages.team-share/index.md (~750 tokens)
- Slim: https://www.anchorterminal.com/niches/agent-packages.team-share/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/agent-packages.team-share/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 1 | 1 | 19 | 7 |

## What counts as done

A new team member gets the shared set from a private source with their existing git credentials in one command, per-team or per-domain subsets are declared rather than copied, and the docs state what is sent to other machines, by which channel, and who can reach it. Commands, subagents, MCP servers, hooks and permissions travel with the skills.

How agents ask for it: roll our company skills out to the team; share my MCP servers with my other machines; install our private skills repo; give the data team only their domain's plugins

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Agentpack (No legal entity found. The licence reads Copyright (c) olegpustovit and contributors, and the docs name Oleg Pustovit as author)**: Private GitHub repos install with GITHUB_TOKEN or the logged-in gh CLI, modes declare subsets, and hooks and MCP servers travel. Docs say what replicates, but tailnet sharing and library replication are on by default and one OAuth scope covers terminals and installs. GitHub only; non-engineers need git.

## What stops agents finishing

- private sources undocumented or unsupported
- shared sources carry skills and rules only
- replication or tailnet sharing on by default, with one scope covering terminals and installs
- non-engineers cannot take part without git

## Around it

Before: agent-packages.pin-and-restore. After: agent-packages.sync-across-agents.

## Where this comes from

Weight 19 of 100 in Agent package managers: 6 of 31 accounts have this as their main job (share 19.4, rounded by largest remainder to sum 100)

As data: https://www.anchorterminal.com/api/v1/use-cases/agent-packages.team-share.json, or the MCP tool get_use_case with id agent-packages.team-share. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
