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-quickstartnpx skills add pingidentity/agent-plugins --skill ping-quickstartgit 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.00090 | $0.01780 |
| Opus 5 | $0.00045 | $0.00890 |
| Sonnet 5 | $0.00018 | $0.00356 |
| Haiku 4.5 | $0.00009 | $0.00178 |
Grade A, and why
ping-quickstart 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ping-quickstart
Front door for all Ping Identity work. Detects the user's platform, identifies what they are trying to accomplish, and routes them to the correct skill.
What this skill does for you: Orientation and routing only — it determines your platform and goal and hands off to the skill that does the work. It does not itself generate configuration or walk through product docs.
Invocation
Invoke this skill explicitly with /ping-quickstart or by saying "use ping-quickstart to...".
When to use this skill
Trigger on ANY of the following — including questions, evaluation discussions, and advisory requests:
- "Where do I start with Ping Identity?" / "I'm new to Ping — what should I set up first?"
- "Which Ping product do I need?"
- "Help me choose between PingOne, PingOne Advanced Identity Cloud, and PingFederate"
- "I inherited a Ping deployment and don't know where to begin"
- "We're evaluating Ping Identity — what should we be asking?"
- "Pros and cons of PingOne vs PingOne Advanced Identity Cloud vs PingFederate; cloud or on-prem?"
- "Advise me on which Ping platform fits our use case"
- "We're migrating from ForgeRock to Ping — what does the migration path look like?"
- "Where do we start with adding [feature] to our app?" (any feature, when the platform is unspecified)
- "We want to add identity verification / KYC — where do we start?"
- "What's the recommended starting point for Ping employee identity?"
- "What license do I need for DaVinci / Protect / Verify?"
- "Test this end to end / validate my Ping setup / how do I prove the path works before going live"
Catch-all rule: Trigger this skill whenever the user's platform or starting point is unknown or unclear, when they use "where do we start", "what should we set up first", "what's the recommended starting point", or "not sure whether to use [product A] or [product B]" framing. Trigger on migration intents (ForgeRock → Ping, Okta → Ping, Auth0 → Ping). Trigger when platform is not yet specified and the user is in evaluation or orientation mode.
What ships with it
9 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/choose-the-right-ping-platform.md 8.6 KB
- references/curated/common-starting-patterns.md 13 KB
- references/curated/end-to-end-validation.md 12 KB
- references/curated/getting-started-overview.md 10 KB
- references/curated/inherited-deployment-orientation.md 12 KB
- references/curated/migration-overview.md 8.7 KB
- references/curated/pingone-licensing-and-packaging.md 9.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.
- yesterday First seen · 121 lines · 90 tokens per session scan A 752461db05d0
ping-quickstart is a skill published in the GitHub repository pingidentity/agent-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 1,780 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.
Other skills, from other repositories
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-pagerank-analyzer
Agent skill for pagerank-analyzer - invoke with $agent-pagerank-analyzer.
agent-pseudocode
Agent skill for pseudocode - invoke with $agent-pseudocode.
agent-performance-analyzer
Agent skill for performance-analyzer - invoke with $agent-performance-analyzer.
agent-neural-network
Agent skill for neural-network - invoke with $agent-neural-network.