Awesome Apm Stacks banner
thinkjones thinkjones

Awesome Apm Stacks

Development community

Description

APM (Agent Package Manager) — think NPM for agentic artifacts. A library of ready-to-install stacks that lets engineering teams share skills, agents, hooks, and coding standards once, and have every teammate get the same setup whether they use Claude Code, Copilot, Cursor, or OpenCode.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

Awesome (Agent Package Manager) APM Stacks

[Sponsor me here](https://github.com/sponsors/thinkjones)

[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE) [![APM Packages](https://img.shields.io/badge/APM_Packages-21-green.svg)](#packages) [![Curated Sources](https://img.shields.io/badge/Curated_Sources-10-orange.svg)](#dependency-sources)

Overview

What is APM?

[APM (Agent Package Manager)](https://microsoft.github.io/apm/) is an open-source project hosted under Microsoft's OSS org, created and maintained by [Daniel Meppiel](https://github.com/danielmeppiel). This repo curates the stacks we run on top of it. Think `npm` for everything that configures an AI agent — declare what you want in an `apm.yml`, and APM resolves, fetches, and wires it into whatever AI tool you're using.

Why APM?

AI dev tooling is the Wild West, and APM is the only credible attempt at a cross-agent dependency manager. Composable flavour packages mean you pull in only what each project needs.

Why "awesome-apm-stacks"?

A demo repo that highlights the composability of APM stacks across different software engineering use cases. Every dependency is sourced from a repo with 1,000+ GitHub stars.

AI dev tooling is still the Wild West

Every coding agent has its own way to load context. Claude Code reads `CLAUDE.md` and `.claude/`. Copilot reads `AGENTS.md` and `.github/`. Cursor reads `.cursorrules` and `.cursor/`. OpenCode wants `.opencode/`. The format you wrote your team's coding standards in last month may not be the format your team is using next month.

Meanwhile, the artifacts engineers actually want — TDD enforcers, code reviewers, security scanners, MCP integrations, slash-command libraries — live scattered across hundreds of GitHub repos, each in its own bespoke layout, each tied to one runtime. Want the same `code-reviewer` agent in Claude Code *and* Cursor? You're rewriting it twice. Want to switch agents next quarter? Start over.

**AP