pingone-app-integration

pingone-app-integration is a skill for Claude Code from pingidentity/agent-plugins. It costs 109 tokens per session (762 once invoked), scanned A, original, MIT.

An integration guide for connecting web, mobile, and server applications to PingOne, Ping Identity’s multi-tenant cloud service. It covers SDK setup, OpenID Connect sign-in flows, token handling, and related integration problems.

In plain words
What is it for?
Use it for Android, iOS, JavaScript or React, and backend integrations, including authorization code with PKCE, client credentials, token exchange, and CIBA.
Why use it?
Applications need a secure way to sign users in and exchange access tokens with PingOne. The guide helps avoid common redirect, browser permission, token, and migration errors.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ping-identity-pingone plugin — 4 skills shipped together

Good fit Use it for Android, iOS, JavaScript or React, and backend integrations, including authorization code with PKCE, client credentials, token exchange, and CIBA.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pingidentity/agent-plugins/pingone-app-integration
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.

Any agent
npx skills add pingidentity/agent-plugins --skill pingone-app-integration
Clone the repo
git clone --depth 1 https://github.com/pingidentity/agent-plugins

Made for: Claude Code.

Or install ping-identity-pingone, the plugin that ships this one along with the rest of its 4 skills.

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 pingone-app-integration

README.md
[![agentmods](https://agentmods.dev/badge/skills/pingidentity/agent-plugins/pingone-app-integration/github.svg)](https://agentmods.dev/skills/pingidentity/agent-plugins/pingone-app-integration)
Your own site
<a href="https://agentmods.dev/skills/pingidentity/agent-plugins/pingone-app-integration"><img src="https://agentmods.dev/badge/skills/pingidentity/agent-plugins/pingone-app-integration/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 pingone-app-integration

Your own site · 80×15
<a href="https://agentmods.dev/skills/pingidentity/agent-plugins/pingone-app-integration"><img src="https://agentmods.dev/badge/skills/pingidentity/agent-plugins/pingone-app-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 109 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 762 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.00109 $0.00762
Opus 5.5 $0.00044 $0.00305
Sonnet 5.5 $0.00022 $0.00152
Haiku 4.5 $0.00011 $0.00076

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

Security

Grade A, and why

pingone-app-integration 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 28d 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.

plugins/ping-identity-pingone/skills/pingone-app-integration/SKILL.md · 51 lines

How it starts

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

PingOne App Integration

Implementation skill for connecting web, mobile, and backend applications to a PingOne environment: SDK wiring, OIDC/PKCE token flows, and implementation diagnostics. Platform setup and DaVinci flow authoring are prerequisites, not covered here.

When to use

  • Android, iOS, or JavaScript/React app integrating with PingOne (auth.pingone.com) using the Ping SDKs.
  • OIDC authorization code + PKCE, token storage, redirects, and silent renewal against a PingOne environment.
  • CORS configuration on the PingOne application before in-browser token exchange.
  • Backend integration: Worker applications, client_credentials, token exchange, CIBA, refresh, resilience.
  • App-side failures: redirect_uri_mismatch, CORS on /as/token, push not delivered, ForgeRock → Ping SDK migration.

When NOT to use

  • Creating the PingOne environment or application record, sign-on policies, or populations → PingOne admin console and documentation.
  • Authoring, wiring, or debugging a DaVinci flow → DaVinci studio and flow documentation.
  • On-prem PingFederate or PingAccess app integration → PingFederate / PingAccess documentation.
  • Portfolio or product selection questions → Ping Identity foundations documentation.

Retrieval and output discipline

Fetch live documentation for SDK versions, artifact coordinates, endpoint paths, and console locations before generating code. Live documentation overrides local reference files.

Important: Use the Ping Orchestration SDKs

Always generate code using the current Ping Orchestration SDKs and not legacy ForgeRock SDKs.

Browser-flow prerequisite: configure CORS before token code

A SPA that performs the token exchange in the browser fails at the token request — and at in-app /as/authorize calls — unless the application's CORS settings allow the app origin. This breaks by default on a new tenant. Confirm CORS under Applications → [app] → Configuration → CORS Settings before generating in-browser token-exchange code; details in references/web-integration.md. If cross-origin setup is out of scope, use a BFF instead.

Read the full file on GitHub · 51 lines

Files

What ships with it

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

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. 28d ago First seen · 51 lines · 109 tokens per session scan A f8dba6a3eee6

Subscribe to this mod's changes

pingone-app-integration is a skill published in the GitHub repository pingidentity/agent-plugins (3 stars, last pushed 4d ago), licensed MIT. It adds 109 tokens to every session and 762 once invoked, about $0.0004 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-09-19.