Category · Agent frameworks
Package managers for coding agents
Tools that install, pin and share what coding agents load, skills, plugins, MCP servers and settings, across several agents and machines, the way a lockfile pins a project's libraries. Compared on what they pin and how (versions, commits or content hashes), which agents they stage for, what runs at install time, and what they share between machines.
Capability keys agent.packages · agent.mcp-client · agent.multi-agent · All tools
letme.dev/agent.packages picks the top-graded tool in this list and says how to call it direct (how letme works).
The same listing from the live API. Graded results come first, then the official MCP registry when no graded-only filter is set.
https://www.anchorterminal.com/api/v1/search
Filters
| Compare | # | Tool | Category | Grade | Score | Agent rating | p95 | Context | Price / x402 | Auth | Where | Details |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 759 | AgentpackOleg Pustovit · Agent harness | Packages | C | 56.4 | none | n/a | n/a | Free · OSS | OAuth | Local | ||
|
Agentpack is an MIT-licensed Go CLI that pins skills, plugins and MCP servers in a lockfile and stages them for seven coding agents. Its gateway runs agent sessions across a person's Tailscale machines and answers MCP at `/mcp`. Top strength Every package is locked to a commit and a content hash, and since 0.7.0 (17 October 2026) an npx-started MCP server's whole npm tree is locked and run without package scripts Top weakness Pre-release at 0.12.7. The project says CLI behaviour, lockfiles, staging layouts and defaults may break between versions with no migration window |
||||||||||||
Nothing matches these filters. .
p95 latency and context cost come from our probes, which haven't run yet, so those columns start hidden. Grades run from AA to F, and agent-ready means BB or better. Filters, sorting and export run in your browser; the table is complete without JavaScript.
How we test this category
The same set of skills, plugins and MCP servers added to a fresh project, synced into two coding agents on two machines, then one upstream skill changed. We check that both agents get identical files, that the change waits until it's updated on purpose, what runs during install, and what crosses between the machines. This test hasn't run yet, so Task success is pending and the grades here come from the categories assessed from public evidence.
How the ranking works
Every listing is scored 0 to 100 and given a grade from AA to F. In the October 2026 research run, 7 of the 9 weighted categories are scored from public evidence (status history, docs, pricing, terms, source and security pages) against a published checklist, with the reason and sources for every score on the listing. Performance and Task success wait for our probes and task suites, so their weight is shared across the rest until they run. Negative events deduct up to 15 points. Read the methodology.
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.