ping-universal-services

A skill for configuring shared Ping services used by login and access flows. These include risk scoring, identity checks, multi-factor authentication, verifiable credentials, governance, and fine-grained authorization.

In plain words
What is it for?
Use it to add risk checks, identity proofing, MFA enrollment, verifiable credentials, identity governance, detailed authorization rules, or shared single sign-on services.
Why use it?
It helps you set up service-level policies and connect them to Ping flows, including cases where no direct configuration tool exists. It explains the required settings and placement in the flow.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/pingidentity/agent-plugins/ping-universal-services
Any agent
npx skills add pingidentity/agent-plugins --skill ping-universal-services
Clone the repo
git clone --depth 1 https://github.com/pingidentity/agent-plugins

Made for: Claude Code, Codex.

Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,415 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00097 $0.01415
Opus 5 $0.00048 $0.00707
Sonnet 5 $0.00019 $0.00283
Haiku 4.5 $0.00010 $0.00142

Measured yesterday against content hash b9c1d314e17e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ping-universal-services 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.

plugins/ping-identity/skills/ping-universal-services/SKILL.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ping-universal-services

Shared strategic services used across PingOne, PingOne Advanced Identity Cloud (AIC), and Ping Software Suite — invoked from flows rather than administered as standalone products. Covers PingOne Protect (risk), PingOne Verify (identity proofing / KYC), PingOne Credentials (verifiable credentials), PingOne IGA (governance), PingOne Authorize (fine-grained authorization), and cross-platform SSO.

What this skill does for you: Generates service and policy configuration and drives it through MCP tools where they exist; where a tool does not exist, it guides you through the docs with the policy fields, thresholds, and node-wiring constraints for each service. Both modes are available — it uses whichever the platform supports for the task.

Invocation

Invoke explicitly with /ping-universal-services or by saying "use ping-universal-services to...".

When to use this skill

  • "Add PingOne Protect risk evaluation to my login flow"
  • "Use PingOne Verify for KYC / identity proofing during registration"
  • "Configure PingOne MFA — device management, MFA policies, or MFA-as-a-service enrollment API"
  • "Issue or present a verifiable credential"
  • "Add IGA governance to my PingOne environment"
  • "Use PingOne Authorize for fine-grained authorization"
  • "Score risk with PingOne Protect and adapt the journey based on the signal"
  • "Cross-platform service selection — which shared service do I need?"

When NOT to use this skill

  • If the task is platform setup or admin: use ping-foundation.
  • If the task is flow / journey design (without a specific service invocation): use ping-orchestration.
  • If the user is just orienting or choosing a platform: use ping-quickstart.
  • If the task is integrating a Protect / Verify / Credentials SDK or library into app code: use ping-app-integration — SDK wiring is app integration, not service configuration.
  • If the user mentions "add security" or "prevent suspicious logins" without naming a specific service, ask a clarifying question — the task may be Protect (risk scoring) or just MFA (orchestration).
  • If the task is MFA node/connector wiring within a journey or flow (not MFA policy or device management): use ping-orchestration — that is flow design, not service configuration.
  • If the task is generic app / SDK integration without referencing a named Universal Service: use ping-app-integration.

Read the full file on GitHub · 98 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. yesterday First seen · 98 lines · 97 tokens per session scan A b9c1d314e17e

Subscribe to this mod's changes

ping-universal-services is a skill published in the GitHub repository pingidentity/agent-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 97 tokens to every session and 1,415 once invoked, about $0.0005 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.