Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/microsoft/apm/spec-pkgmgr-editorgit clone --depth 1 https://github.com/microsoft/apmWhat 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 | $0.00051 | $0.00810 |
| Opus 5 | $0.00026 | $0.00405 |
| Sonnet 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 2d 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.
- 2d 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 (3,668 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 810 once invoked, about $0.0003 per session on Opus 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
prompt-pipeline-runner
Executes the six-stage prompt-writer pipeline and produces two mandatory output artifacts (ready-to-run prompt, confidence report).
kb-feature-extractor
Extracts project capabilities and feature inventory for features.md from pre-filtered anchor-class files.
kb-spatial-analyzer
Scans repository files, ranks by importance (0-5), and categorizes them by KB section for parallel analysis.
project-documenter
Generates a digestible 3-tier/9-section birds-eye-view document from KB + codebase, with per-claim provenance in hidden HTML comments.
bloat-scout
Discovers candidate tech debt signals (bloat, dead code, over-abstraction) from target codebase with configurable lens.
kb-concept-extractor
Extracts domain concepts and terminology for conceptmap.md from pre-filtered files.