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 skills/pingidentity/aic-mcp-server/monitor-usagenpx skills add pingidentity/aic-mcp-server --skill monitor-usagegit clone --depth 1 https://github.com/pingidentity/aic-mcp-serverWrote 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/skills/pingidentity/aic-mcp-server/monitor-usage)<a href="https://agentmods.dev/skills/pingidentity/aic-mcp-server/monitor-usage"><img src="https://agentmods.dev/badge/skills/pingidentity/aic-mcp-server/monitor-usage.svg" alt="Measured on agentmods" 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 | $0.00079 | $0.00869 |
| Opus 5 | $0.00039 | $0.00434 |
| Sonnet 5 | $0.00016 | $0.00174 |
| Haiku 4.5 | $0.00008 | $0.00087 |
Grade A, and why
monitor-usage 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 3d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitor MCP Server Usage
Use the getLogSources and queryLogs tools to retrieve and interpret AIC audit logs. Always check the current time before querying so time ranges are accurate.
MCP Identity Markers
These values identify MCP server activity in the logs:
| Marker | Value | Where it appears |
|---|---|---|
| Initial auth client | AICMCPClient |
am-authentication — PKCE / Device Code login |
| Token exchange client | AICMCPExchangeClient |
am-authentication — one AM-TOKEN-EXCHANGE event per tool call |
| API User-Agent | aic-mcp-server/<version> |
idm-access, am-access — all outbound API requests |
Log Sources and What They Show
| Source | What to look for |
|---|---|
am-authentication |
AM-TOKEN-EXCHANGE events for AICMCPExchangeClient — proxy for tool invocation count and timing; AM-TREE-LOGIN-COMPLETED for user login events |
am-config |
AM-CONFIG-CHANGE events — journey, node, script, and OIDC app changes; userId field shows the authenticated user |
idm-access |
Per-request HTTP log; filter by user-agent co "aic-mcp-server" to isolate MCP traffic from browser and reconciliation jobs |
idm-activity |
Full before/after state for managed object operations (CREATE, PATCH, DELETE on users, groups, roles, etc.); runAs field shows the authenticated user |
Interpreting Results
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.
- 3d ago First seen · 73 lines · 79 tokens per session scan A cf988c3976aa
monitor-usage is a skill published in the GitHub repository pingidentity/aic-mcp-server (2 stars, last pushed 29d ago), licensed Apache-2.0. It adds 79 tokens to every session and 869 once invoked, about $0.0004 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…