Niches · Agent package managers

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

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

0companies, full fit
1companies, fit with a limit
1companies carry the tag
19share of the category's work
7first-hand accounts

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 1

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.

ListingWhy
Agentpack C
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. source

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)

The same as data: /api/v1/use-cases/agent-packages.team-share.json, or the MCP tool get_use_case with id agent-packages.team-share. Other jobs in this category: /api/v1/niches?category=agent-packages.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.