aic-mcp-server: Skill for Claude Code

.claude/skills/monitor-usage/SKILL.md

monitor-usage is a skill for Claude Code from pingidentity/aic-mcp-server. It costs 79 tokens per session (869 once invoked), scanned A, original, Apache-2.0.

A checklist for reviewing code changes, with emphasis on security, correctness, project conventions, and verification.

In plain words
What is it for?
Use it to review a pull request or diff, validate a tool implementation, and run the project’s review or security-review checks.
Why use it?
It helps catch issues such as unsafe paths, incorrect API usage, leaked error details, missing annotations, and incomplete tests before changes are committed.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is pingidentity/aic-mcp-server's own configuration. It tells Claude Code how to work on aic-mcp-server itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything aic-mcp-server configures →

Reuse

Borrowing it

Nothing to install: this file belongs to pingidentity/aic-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/pingidentity/aic-mcp-server/main/.claude/skills/monitor-usage/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/pingidentity/aic-mcp-server

Made for: Claude Code.

Wrote 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.

agentmods badge for monitor-usage

README.md
[![agentmods](https://agentmods.dev/badge/skills/pingidentity/aic-mcp-server/monitor-usage/github.svg)](https://agentmods.dev/skills/pingidentity/aic-mcp-server/monitor-usage)
Your own site
<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/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.

agentmods 80×15 button for monitor-usage

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 869 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00079 $0.00869
Opus 5.5 $0.00032 $0.00348
Sonnet 5.5 $0.00016 $0.00174
Haiku 4.5 $0.00008 $0.00087

Measured 1mo ago against content hash cf988c3976aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.claude/skills/monitor-usage/SKILL.md · 73 lines

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

Read the full file on GitHub · 73 lines

Changes

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.

  1. 1mo ago First seen · 73 lines · 79 tokens per session scan A cf988c3976aa

Subscribe to this mod's changes

monitor-usage is a skill published in the GitHub repository pingidentity/aic-mcp-server (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 79 tokens to every session and 869 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens