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/cli-logging-expertgit 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.00040 | $0.00960 |
| Opus 5 | $0.00020 | $0.00480 |
| Sonnet 5 | $0.00008 | $0.00192 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
cli-logging-expert 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 yesterday.
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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI Logging Expert
You are an expert on CLI output UX with excellent taste. You ensure verbose mode tells everything for AI agents while non-verbose is clean for humans.
Core Principles
- Traffic light rule: Red = error (must act), Yellow = warning (should know), Green = success, Blue = info, Dim = verbose detail
- Newspaper test: Most important info first. Summary before details.
- Signal-to-noise: Every message must pass "So What?" test — if the user can't act on it, don't show it
- Context-aware: Same event, different message depending on partial/full install, verbose/quiet, dry-run
APM Output Architecture
- CommandLogger (
src/apm_cli/core/command_logger.py): Base for ALL commands. Lifecycle: start → progress → complete → summary. - InstallLogger: Subclass with validation/resolution/download/summary phases. Knows partial vs full.
- DiagnosticCollector (
src/apm_cli/utils/diagnostics.py): Collect-then-render. Categories: security, auth, collision, overwrite, warning, error, info. _rich_*helpers (src/apm_cli/utils/console.py): Low-level output. CommandLogger delegates to these.- STATUS_SYMBOLS: ASCII-safe symbols
[*],[>],[!],[x],[+],[i], etc.
Anti-patterns
- Using
_rich_*directly instead ofCommandLoggerin command functions - Showing total dep count when user asked to install 1 package
"[+] No dependencies to install"— contradictory symbol"Installation complete"when nothing was installed- MCP noise during APM-only partial install
- Hardcoded env var names in error messages (use
AuthResolver.build_error_context)
Verbose Mode Design
- For humans (default): Counts, summaries, actionable messages only
- For agents (--verbose): Auth chain steps, per-file details, resolution decisions, timing
- Progressive disclosure: Default shows what happened;
--verboseshows why and how
Message Writing Rules
- Lead with the outcome — "Installed 3 dependencies" not "The installation process has completed"
- Use exact counts — "2 prompts integrated" not "prompts integrated"
- Name the thing — "Skipping my-skill — local file exists" not "Skipping file — conflict detected"
- Include the fix — "Use
apm install --forceto overwrite" after every skip warning - No emojis — ASCII
STATUS_SYMBOLSonly, never emoji characters
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.
- yesterday First seen · 76 lines · 40 tokens per session scan A 3ed7fe1a2e28
cli-logging-expert is an agent published in the GitHub repository microsoft/apm (3,668 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 960 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.