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/agent-plugins/ping-identity-for-ainpx skills add pingidentity/agent-plugins --skill ping-identity-for-aigit clone --depth 1 https://github.com/pingidentity/agent-pluginsWrote 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/agent-plugins/ping-identity-for-ai)<a href="https://agentmods.dev/skills/pingidentity/agent-plugins/ping-identity-for-ai"><img src="https://agentmods.dev/badge/skills/pingidentity/agent-plugins/ping-identity-for-ai.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.1 | $0.00079 | $0.01205 |
| Opus 5 | $0.00039 | $0.00602 |
| Sonnet 5 | $0.00016 | $0.00241 |
| Haiku 4.5 | $0.00008 | $0.00120 |
Grade A, and why
ping-identity-for-ai 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 5d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ping-identity-for-ai
AI-era identity patterns: Identity for AI, Verified Trust, agent identity, agent security, and AI application authentication.
What this skill does for you: Guides you through architecture, patterns, and design decisions for securing AI agents with Ping. It is currently conceptual rather than executable — there are no dedicated ID4AI MCP tools, so it does not generate ID4AI-specific configuration. For the parts that map to existing platform capabilities (e.g. agent client credentials, PingGateway routes), it hands off to ping-foundation and ping-app-integration, which generate config and code.
Invocation
Invoke explicitly with /ping-identity-for-ai or by saying "use ping-identity-for-ai to...".
When to use this skill
- "Give my AI agent a verified identity for API access"
- "Use Verified Trust signals in my MCP server"
- "Secure agent-to-agent authentication using Ping"
- "Workforce helpdesk AI — how do I authenticate users for my AI assistant?"
- "Identity for AI architecture with Ping"
- "AI app authentication patterns on PingOne"
- "Agent security and authorization for agentic workflows"
- "Short-lived tokens or token rotation for an autonomous agent"
- "Delegated token for an AI assistant acting on behalf of an employee"
- "Revoke a compromised AI agent's access immediately"
When NOT to use this skill
- General platform setup or tenant administration: use
ping-foundation. - Building a journey or DaVinci flow for human authentication (not AI-specific): use
ping-orchestration. - App SDK integration without AI context: use
ping-app-integration. - User is orienting or selecting a platform: use
ping-quickstart. - Using Ping Protect, PingOne Verify, or PingOne Authorize as standalone services without AI agent context: use
ping-universal-services. - "Automated process", "batch job", "scheduled task", or "service account" without any AI / LLM / agent context — ask a clarifying question to determine whether this involves an AI agent or a conventional machine process before routing here.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- ping-marketplace.json 1001 B
- references/curated/.gitkeep 0 B
- references/curated/agent-gateway-mcp.md 8.9 KB
- references/curated/agent-security-patterns.md 15 KB
- references/curated/identity-for-ai-overview.md 12 KB
- references/curated/verified-trust-overview.md 8.9 KB
- references/curated/workforce-helpdesk-ai.md 10 KB
- references/runtime/mcp-preflight.md 3.8 KB
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.
- 5d ago First seen · 91 lines · 79 tokens per session scan A f420593387f4
ping-identity-for-ai is a skill published in the GitHub repository pingidentity/agent-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 1,205 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
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
session-summaries
What the chat right-panel session summary shows, what it costs, and how to make a session summarize well. Load when the user asks about the session summary panel, why a summary looks wrong or empty, or how to turn it on.
debug
Debug issues in the MCP Gateway Registry using first-principles thinking. Invoke when something is broken, timing out, returning errors, or behaving unexpectedly. Forces structured root-cause analysis before any code change is proposed.