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-orchestrationnpx skills add pingidentity/agent-plugins --skill ping-orchestrationgit 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.00079 | $0.01509 |
| Opus 5 | $0.00039 | $0.00754 |
| Sonnet 5 | $0.00016 | $0.00302 |
| Haiku 4.5 | $0.00008 | $0.00151 |
Grade A, and why
ping-orchestration 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ping-orchestration
Design and build authentication flows, orchestration logic, and journey-based experiences across Ping Identity platforms. MCP tools handle execution; this skill supplies design patterns, node sequencing, branching logic, and platform-specific constraints.
What this skill does for you: Builds journeys and flows directly through MCP tools where they exist (AIC journeys); where a tool does not exist, it guides you through the design with node sequencing, branching logic, and platform constraints. Both modes are available — it uses whichever the platform supports for the task.
Invocation
Invoke this skill explicitly with /ping-orchestration or by saying "use ping-orchestration to...".
When to use this skill
Trigger on ANY question — including advisory, planning, and "what nodes do I need" requests, not just implementation — when the task involves:
- Building or designing a login, registration, recovery, MFA, or step-up journey in PingOne Advanced Identity Cloud (AIC) / PingAM
- Passwordless authentication flows (passkeys, FIDO2, magic links, biometric)
- Authenticator app login, push MFA, or TOTP enrollment flows
- Transaction approvals via email or push (CIBA / out-of-band step-up)
- Creating or designing a DaVinci flow for authentication, MFA, or orchestration
- Configuring a PingAM authentication tree or scripted decision node
- Planning or reviewing journey structure before implementation
- Deciding between inner journeys, scripted nodes, or DaVinci connectors
- Any question about designing, planning, or advising on authentication flows, journeys, or orchestration logic in PingOne Advanced Identity Cloud (AIC), PingOne / DaVinci, or PingAM
When NOT to use this skill
- If the platform is not yet set up (no tenant, no realm, no app registered): use
ping-foundationfirst - If the task is configuring the platform layer (apps, directories, policies, branding): use
ping-foundation - If the task is invoking a Universal Service (Protect, Verify, IGA, Credentials) without needing flow design: use
ping-universal-services - If the task is integrating the flow into an app or SDK: use
ping-app-integration - If unsure which platform: use
ping-quickstartfirst
What ships with it
25 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/cross-platform/journey-and-flow-promotion.md 11 KB
- references/curated/cross-platform/passkeys-and-passwordless.md 14 KB
- references/curated/pingone-mt/davinci-flow-patterns.md 5.9 KB
- references/curated/pingone-mt/davinci-overview.md 7.6 KB
- references/curated/pingone-mt/davinci-registration-and-mfa.md 8.2 KB
- references/curated/pingone-st/journey-design-patterns.md 16 KB
- references/curated/pingone-st/journey-use-cases/account-recovery-and-username-reminder.md 5.7 KB
- references/curated/pingone-st/journey-use-cases/financial-services-step-up.md 7.7 KB
- references/curated/pingone-st/journey-use-cases/mfa-authentication-multi-method.md 7.3 KB
- references/curated/pingone-st/journey-use-cases/mfa-method-selection-registration.md 6.4 KB
- references/curated/pingone-st/journey-use-cases/password-reset-and-update.md 5.5 KB
- references/curated/pingone-st/journey-use-cases/passwordless-mfa-registration.md 8.1 KB
- references/curated/pingone-st/journey-use-cases/pingone-protect-risk-integration.md 7.4 KB
- references/curated/pingone-st/journey-use-cases/progressive-profiling.md 5.7 KB
- references/curated/pingone-st/journey-use-cases/social-and-local-registration-authentication.md 7.3 KB
- references/curated/pingone-st/nodes/basic-auth-nodes.md 8.3 KB
- references/curated/pingone-st/nodes/federation-contextual-nodes.md 9.4 KB
- references/curated/pingone-st/nodes/identity-management-nodes.md 14 KB
- references/curated/pingone-st/nodes/mfa-nodes.md 17 KB
- references/curated/pingone-st/nodes/node-fundamentals.md 5.9 KB
- references/curated/pingone-st/nodes/risk-management-nodes.md 11 KB
- references/curated/pingone-st/nodes/utility-nodes.md 15 KB
- references/curated/pingone-st/routing-index.md 4.5 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 · 116 lines · 79 tokens per session scan A 914cb5567a29
ping-orchestration 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,509 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-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
agent-collective-intelligence-coordinator
Agent skill for collective-intelligence-coordinator - invoke with $agent-collective-intelligence-coordinator.
agent-orchestrator-task
Agent skill for orchestrator-task - invoke with $agent-orchestrator-task.
length-converter
Convert between common length units (miles, km, feet, meters) using a multiplication factor.
pr-feedback
Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.