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-app-integrationnpx skills add pingidentity/agent-plugins --skill ping-app-integrationgit clone --depth 1 https://github.com/pingidentity/agent-pluginsWhat 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.00073 | $0.01257 |
| Opus 5 | $0.00036 | $0.00629 |
| Sonnet 5 | $0.00015 | $0.00251 |
| Haiku 4.5 | $0.00007 | $0.00126 |
Grade A, and why
ping-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 2d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ping-app-integration
Implementation skill for integrating Ping Identity into web, mobile, and application SDK experiences.
What this skill does for you: Generates app-side integration code — SDK wiring, OIDC/PKCE flows, token handling — and guides you through the SDK docs and troubleshooting where code generation alone is not enough. Primarily an artifact-generating skill.
Invocation
Invoke explicitly with /ping-app-integration or by saying "use ping-app-integration to...".
When to use this skill
- "Integrate Ping into my React app using the orchestration SDK"
- "Use the iOS SDK with AIC journeys"
- "Wire OIDC redirect into a mobile app"
- "Embed a journey in a webview"
- "Migrate from the ForgeRock SDK to the Ping SDK"
- "Add browser-based login to my web application"
- "Connect my Android app to a DaVinci flow"
- "App-side OIDC / OAuth configuration for PingFederate"
- "Redirect URI mismatch error in my app"
- "CORS error on the token endpoint"
When NOT to use this skill
- Platform setup or app registration (no code): use
ping-foundation. - Designing the flow or journey itself: use
ping-orchestration. - General onboarding orientation: use
ping-quickstart.
Multi-skill use cases
A complete app integration spans three layers — all are required for a production outcome:
| Layer | Skill | Typical tasks |
|---|---|---|
| 1. Platform setup + app registration | ping-foundation |
Tenant setup, redirect URI registration, sign-on policy |
| 2. Journey or flow design | ping-orchestration |
Journey nodes, DaVinci flows, MFA policy |
| 3. SDK / app-side implementation | ping-app-integration (this skill) |
SDK install, init, auth flow, token storage |
Complete platform setup first, then flow design, then hand off to this skill for SDK wiring.
End-to-end example (Android + DaVinci on PingOne):
- Use
ping-foundationto register an OIDC application in PingOne, configure the redirect URI (myapp://callback), and note the client ID and environment ID. - Use
ping-orchestrationto build and test a DaVinci login flow with username/password and push MFA nodes. - Use this skill (
ping-app-integration) to add thecom.pingidentity.sdks:davinciandcom.pingidentity.sdks:oidcdependencies, initializePingOne.init(context)with the client ID and discovery endpoint, callPingOne.startAuthentication(activity), and handle theAuthResult.
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 1.1 KB
- references/curated/.gitkeep 0 B
- references/curated/app-integration-overview.md 8.9 KB
- references/curated/integration-troubleshooting-basics.md 17 KB
- references/curated/mobile-integration-basics.md 15 KB
- references/curated/server-side-integration-basics.md 16 KB
- references/curated/web-integration-basics.md 15 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.
- 2d ago First seen · 95 lines · 73 tokens per session scan A 6153a79a7516
ping-app-integration is a skill published in the GitHub repository pingidentity/agent-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 1,257 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
agent-device
Automates Apple-platform apps (iOS, tvOS, macOS), Android devices, and Amazon Vega OS TV apps in Vega Virtual Devices. Use when navigating apps, taking snapshots/screenshots where supported, driving TV remotes, tapping, typing, scrolling, extracting UI info, collecting evidence, or planning agent-device CLI commands.
android-emulator
Verify and debug native, React Native, Expo, or Flutter apps on an Android Emulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an Android virtual device.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
ios-simulator-preview
Show a live iOS Simulator in the dashboard's Browser side panel while building or testing an iOS app. Use when the user asks to preview an iOS/SwiftUI app, run an app in the simulator, "show me the app", test in the iOS simulator, or watch you drive an iOS app. macOS + Xcode only.
rn-device-control
This skill should be used when the user asks to "control the simulator", "take a screenshot", "boot the emulator", "install the app", "read UI hierarchy", "manage device state", "open a deep link", "grant permissions", "stream native logs", "disable animations", "change device locale", or needs guidance on xcrun…