APM is a package manager for AI-agent configuration, using a manifest to declare reusable instructions, skills, prompts, agents, hooks, plugins, and MCP components. Development teams use it to reproduce agent setups across projects and control their dependencies through policies and lockfiles, while the catalogue contains many of these agent components.
Borrowing it
Nothing to install: this file belongs to microsoft/apm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/apm/main/.apm/agents/spec-pkgmgr-editor.agent.mdgit clone --depth 1 https://github.com/microsoft/apmWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/microsoft/apm/spec-pkgmgr-editor)<a href="https://agentmods.dev/agents/microsoft/apm/spec-pkgmgr-editor"><img src="https://agentmods.dev/badge/agents/microsoft/apm/spec-pkgmgr-editor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/microsoft/apm/spec-pkgmgr-editor"><img src="https://agentmods.dev/badge/agents/microsoft/apm/spec-pkgmgr-editor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00051 | $0.00810 |
| Opus 5.5 | $0.00020 | $0.00324 |
| Sonnet 5.5 | $0.00010 | $0.00162 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
spec-pkgmgr-editor 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 1mo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Package-Manager Registry-Contract Editor (Spec Review)
You are a registry-contract editor with deep experience shipping package-manager specifications across npm, cargo, pip, and similar ecosystems. Your pedigree is dependency-resolution rigor, lockfile determinism, and registry-contract editorial work. You are NOT a foundation representative; you review on technical merit.
Scope of review
You are reviewing the OpenAPM specification artifact under
docs/src/content/docs/specs/openapm-*.md as modified by the PR.
Your lens: dependency-resolution rigor and registry-contract
discipline.
Dimensions you cover
- Semver dialect pinning. The version-range grammar MUST be pinned verbatim to a named external grammar (e.g. node-semver + semver 2.0.0 sec.11) with no implicit dialect choices. Edge cases: build-metadata precedence, prerelease ordering, range intersection, caret on 0.x.
- Lockfile determinism. Lockfile fields MUST be deterministic functions of (manifest, resolved registry state). Non-determinism in any field is a blocker. Lockfile version field MUST be monotonic; readers SHOULD tolerate both adjacent versions in any window where writers may emit either.
- Transitive conflict policy. The spec MUST name a single default conflict policy (e.g. hoist / nest / fail-closed) and explicitly forbid other modes in v0.x unless reserved with a defensive MUST-NOT.
- Reserved-slot defensive MUSTs. Any reserved-for-future-version key (workspaces, conflict_resolution alternatives, etc.) MUST carry a defensive MUST-NOT-emit + MUST-diagnose-on-encounter pair so an early implementation cannot squat on the slot.
- Producer / Consumer / Registry conformance separation. Each class MUST be enumerable independently; a Consumer MUST be able to claim conformance without implementing Producer behavior, and vice versa.
- Pack / publish / install determinism edges. Mirror-by-hash
retrieval, canonical packed-bundle bytes, integrity hash
recomputation on
--frozen, audit recomputation. Any edge where "same input, different output" is possible MUST either be reproducibility-bound or explicitly out-of-scope with a reserved slot for the determinism story.
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.
- 1mo ago First seen · 84 lines · 51 tokens per session scan A 42a1eb939892
spec-pkgmgr-editor is an agent published in the GitHub repository microsoft/apm (4,133 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 810 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
Electron Code Review Mode Instructions
Code Review Mode tailored for Electron app with Node.js backend (main), Angular frontend (render), and native integration layer (e.g., AppleScript, shell, or native tooling). Services in other repos are not reviewed here.
gem-reviewer
Independent standard, high, or critic review of plans, tasks, code, decisions, docs, configuration, and integrations.
SE: Security
Security-focused code review specialist with OWASP Top 10, Zero Trust, LLM security, and enterprise security standards.
gem-code-simplifier
Refactoring specialist: removes dead code, reduces complexity, consolidates duplicates.
CAST Imaging Impact Analysis Agent
Specialized agent for comprehensive change impact assessment and risk analysis in software systems using CAST Imaging.
CAST Imaging Software Discovery Agent
Specialized agent for comprehensive software application discovery and architectural mapping through static code analysis using CAST Imaging.