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 aic-app-integrationgit 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/aic-app-integration)<a href="https://agentmods.dev/skills/pingidentity/agent-plugins/aic-app-integration"><img src="https://agentmods.dev/badge/skills/pingidentity/agent-plugins/aic-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.
<a href="https://agentmods.dev/skills/pingidentity/agent-plugins/aic-app-integration"><img src="https://agentmods.dev/badge/skills/pingidentity/agent-plugins/aic-app-integration.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.00110 | $0.00795 |
| Opus 5.5 | $0.00044 | $0.00318 |
| Sonnet 5.5 | $0.00022 | $0.00159 |
| Haiku 4.5 | $0.00011 | $0.00080 |
Grade A, and why
aic-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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIC App Integration
Implementation skill for connecting web, mobile, and backend applications to a PingOne Advanced Identity Cloud (AIC) tenant: SDK wiring, journey callback rendering, OIDC/PKCE token flows, and implementation diagnostics. Tenant setup and journey authoring are prerequisites, not covered here.
When to use
- Android, iOS, or JavaScript/React app integrating with AIC using the Ping SDK Journey modules or journey client.
- OIDC authorization code + PKCE against realm-scoped endpoints, token storage, redirects, silent renewal.
- Tenant CORS configuration before in-browser token exchange.
- SAML SP integration for enterprise apps federating through AIC.
- Backend integration: OAuth 2.0 clients, client_credentials, token validation, refresh, resilience.
- App-side failures: redirect_uri_mismatch, CORS token failures, push not delivered, ForgeRock → Ping SDK migration.
When NOT to use
- Creating tenants, realms, application agents, or AM services → AIC admin console and documentation.
- Authoring, wiring, or debugging journeys or PingAM trees → journey-design tooling and AIC documentation.
- Self-managed PingAM trees → PingAM documentation for the target release.
- 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. Verify tenant-scoped values (realm path, FQDN, endpoints) against the target tenant.
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 journey calls — unless tenant CORS allows the app origin. This breaks by default on a new tenant. Confirm CORS under Tenant settings → Global Settings → Cross-Origin Resource Sharing (CORS) 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.
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.
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.
- 28d ago First seen · 53 lines · 110 tokens per session scan A c37eb3ea57b1
aic-app-integration is a skill published in the GitHub repository pingidentity/agent-plugins (3 stars, last pushed 4d ago), licensed MIT. It adds 110 tokens to every session and 795 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.
Other skills, from other repositories
durable-objects
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.
cloudflare-email-service
Implement or troubleshoot Cloudflare Email Sending and Email Routing integrations and their delivery configuration.
workers-best-practices
Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
news-search
Search current news for a topic, company, competitor, or hook and return dated, attributed articles. Uses the newsjack CLI and Medialyst REST API when available, tries direct Medialyst MCP if the CLI is missing, and falls back to host web/browser search with explicit caveats only when neither cloud path is available.
agentcore-register
Given an MCP server URL, probe the server via curl to discover its metadata and tools, then generate a markdown file with copy-pasteable content for each field in the Amazon Bedrock AgentCore "Create record" form.
api-caller
Call any REST API dynamically. Make GET, POST, PUT, DELETE requests to any endpoint with custom headers and JSON body.