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 skills add pingidentity/agent-plugins --skill ping-migrationgit clone --depth 1 https://github.com/pingidentity/agent-pluginsWrote 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.
[](https://agentmods.dev/skills/pingidentity/agent-plugins/ping-migration)<a href="https://agentmods.dev/skills/pingidentity/agent-plugins/ping-migration"><img src="https://agentmods.dev/badge/skills/pingidentity/agent-plugins/ping-migration/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.
<a href="https://agentmods.dev/skills/pingidentity/agent-plugins/ping-migration"><img src="https://agentmods.dev/badge/skills/pingidentity/agent-plugins/ping-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00078 | $0.01321 |
| Opus 5.5 | $0.00031 | $0.00528 |
| Sonnet 5.5 | $0.00016 | $0.00264 |
| Haiku 4.5 | $0.00008 | $0.00132 |
Grade A, and why
ping-migration 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 4d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ping Migration
Application-level migration from a source system (PingFederate, PingOne for Enterprise) to a destination (PingOne). Bundles a migration orchestrator that extracts, classifies, applies, and validates applications in one command, plus the classification rules, assessment and wave-planning method, and rollback design for everything the orchestrator does not automate.
When to use this skill
- Migrating OAuth clients, SAML SP connections, or IdP connections off PingFederate or P14E into PingOne
- Assessing migration readiness, or previewing what would be migrated without changing anything
- Planning migration waves, sequencing, acceptance criteria, or validation gates
- Deciding whether a specific app can migrate directly, needs redesign, or is out of scope
- Mapping PingFederate grant types, entities, or auth policy topology to PingOne equivalents
- Designing rollback or cutover, or rolling back a completed migration run
- Understanding what the bundled orchestrator does, or extending a source/destination adapter
When NOT to use this skill
- Choosing which migration track applies at all (SDK code vs. server/SaaS vs. PingFederate → PingOne)
- Migrating SDK code from ForgeRock SDKs to Ping Orchestration SDKs → https://developer.pingidentity.com/orchsdks/journey/migration.md
- Routine platform setup unrelated to a migration (create an environment, register an app) → the PingOne admin console and https://docs.pingidentity.com/
- Re-creating a journey or DaVinci flow in the destination → the destination platform's flow-design documentation
Execution rules (unattended)
This skill is agent-first: no user is expected to be present. Resolve missing values from the task prompt, the environment (existing pingcli profiles, a pre-exported source file), and the reference files — not by waiting for an answer.
- Always run
--dry-runfirst. It classifies and writes the assessment report without applying anything, and with--import-fileit needs no credentials at all. - Never pause for optional detail. Derive sensible values (work directory, environment name, wave counts) from context and state them in the output.
- Stop and report only when a required value has no derivable source — name the missing value and the command that needs it, then stop.
- Secrets are supplied out-of-band:
PINGONE_CLIENT_SECRETfor the secret script, never a command-line flag. - Tool order:
pingcli(check withwhich pingcli) → bundled orchestrator inscripts/→ general guidance.
What ships with it
18 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.
- references/blueprints/migration-architecture.md 6.7 KB
- references/blueprints/pingfederate-migration-inventory.md 5.2 KB
- references/catalogs/classification-rules.md 4.8 KB
- references/catalogs/p14e-admin-api-mapping.md 11 KB
- references/examples/sample-prompts.md 2.3 KB
- references/playbooks/assessment-and-wave-planning.md 6.0 KB
- references/playbooks/post-migration-and-rollback.md 6.0 KB
- references/playbooks/run-migration.md 8.9 KB
- scripts/adapters/destinations/pingone-adapter.js 44 KB runs code
- scripts/adapters/sources/p14e-adapter.js 12 KB runs code
- scripts/adapters/sources/p14e-adapter.test.js 3.8 KB runs code
- scripts/adapters/sources/pf-adapter.js 26 KB runs code
- scripts/classifier.js 9.3 KB runs code
- scripts/ping-migration.js 16 KB runs code
- scripts/pingone-client-secret.js 40 KB runs code
- scripts/pingone-client-secret.sh 44 KB runs code
- scripts/reports.js 29 KB runs code
- scripts/rollback.js 6.2 KB runs code
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.
- 4d ago First seen · 72 lines · 78 tokens per session scan A 295b7ff4775e
ping-migration is a skill published in the GitHub repository pingidentity/agent-plugins (3 stars, last pushed 4d ago), licensed MIT. It adds 78 tokens to every session and 1,321 once invoked, about $0.0003 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-10-13.
Other skills, from other repositories
reflection-coach
Reflect on another agent's recent execution record and propose the smallest durable instruction, skill, or tool-description change. Use for evidence-backed coaching proposals, never hot-swaps.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
cf-cli
Cloudflare's official cf CLI (beta) for the public Cloudflare API and Workers projects. Use for finding and running Cloudflare commands from the terminal — sign-in and profiles, cf cli search, cf schema, cf deploy/dev/build, resource commands for DNS, zones, D1, KV, and R2 — and for choosing between cf and Wrangler in…
session-summaries
What the chat right-panel session summary shows, what it costs, and how to make a session summarize well. Load when the user asks about the session summary panel, why a summary looks wrong or empty, or how to turn it on.
create-custom-grader
Use when converting an existing benchmark, rubric, verifier, task YAML/JSON, or domain check into SkillEvaluator BYOG/BYOT custom evaluation.