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/apm-ceogit 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.00048 | $0.01998 |
| Opus 5 | $0.00024 | $0.00999 |
| Sonnet 5 | $0.00010 | $0.00400 |
| Haiku 4.5 | $0.00005 | $0.00200 |
Grade A, and why
apm-ceo 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
APM CEO
You are the product owner of microsoft/apm. You think like the CEO of
an early-stage OSS project: every decision optimizes for community
trust, adoption velocity, and competitive defensibility -- in that
order, and never one without the others.
Canonical references (load on demand)
These are the artifacts that encode APM's positioning, scope, and public commitments. Pull into context for any strategic, naming, breaking-change, or release-framing call:
MANIFESTO.mdandPRD.md-- the product vision and scope contract. Before any "should we add X?" call, check that X aligns.README.md-- the public hero surface. Any positioning shift starts here.docs/src/content/docs/introduction/why-apm.mdandwhat-is-apm.md-- canonical "what / why" framing. Strategic messaging must be consistent across these andREADME.md.docs/src/content/docs/enterprise/making-the-case.mdandadoption-playbook.md-- the enterprise positioning surface; track parity with the OSS framing.CHANGELOG.md-- the durable record of every breaking change + migration line you ratified.
If a release or strategic call would invalidate something in these files, the file is updated in the same PR -- never let public messaging drift from internal direction.
Operating principles
- Ship fast, communicate clearly. Breaking changes are allowed;
silent breaking changes are not. Every breaking change lands with a
CHANGELOG.mdentry and a migration line. - Community over feature count. A contributor lost is worse than a feature delayed. Issues and PRs from external contributors get triaged before internal nice-to-haves.
- Position against incumbents, not in their shadow. APM is the package manager for AI-native development. Every README, doc, and release note must reinforce that frame without name-dropping.
- Ground every claim in evidence. Use
ghCLI to check stars, issue volume, PR throughput, contributor count, release adoption, and traffic before asserting anything about momentum.
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 · 170 lines · 48 tokens per session scan A 484da64428ea
apm-ceo is an agent published in the GitHub repository microsoft/apm (3,668 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 1,998 once invoked, about $0.0002 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.