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 d-padmanabhan/agent-engineering-handbook --skill oktagit clone --depth 1 https://github.com/d-padmanabhan/agent-engineering-handbookWrote 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/d-padmanabhan/agent-engineering-handbook/okta)<a href="https://agentmods.dev/skills/d-padmanabhan/agent-engineering-handbook/okta"><img src="https://agentmods.dev/badge/skills/d-padmanabhan/agent-engineering-handbook/okta/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/d-padmanabhan/agent-engineering-handbook/okta"><img src="https://agentmods.dev/badge/skills/d-padmanabhan/agent-engineering-handbook/okta.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 236 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 238 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00090 | $0.03584 |
| Opus 5 | $0.00045 | $0.01792 |
| Sonnet 5 | $0.00018 | $0.00717 |
| Haiku 4.5 | $0.00009 | $0.00358 |
Grade A, and why
okta 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 8d 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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Okta Workforce Identity - Playbook
Companion rule: 317-okta.mdc. This skill turns those patterns into end-to-end workflows.
Scope: Okta Workforce Identity Cloud (WIC). For Customer Identity Cloud (Auth0 / Okta CIC), patterns differ; consult Auth0 docs for tenants, connections, hooks, and actions.
When to invoke
Use when the user:
- Is adding or changing an SSO/SAML/OIDC app integration
- Needs to tighten or audit sign-on policies, MFA, or authenticator policies
- Is rolling out SCIM provisioning (inbound from HRIS or outbound to apps)
- Is migrating from ADFS, Ping, Azure AD / Entra ID, or OneLogin
- Needs to debug a user login failure with evidence from System Log
- Must rotate signing keys, API tokens, or certificates
- Is auditing admin roles, API token usage, or lifecycle hygiene
- Is designing Workflows for JML or cross-app orchestration
- Is configuring or reviewing Cross App Access (XAA), ID-JAG exchanges, or resource server connectors
- Is managing Okta via
terraform-provider-okta
Golden Rules (anchor for every workflow)
- HRIS is the source of truth, not Okta.
- MFA for everyone; phishing-resistant MFA for admins.
- OAuth 2.0 for Okta (client-credentials) beats long-lived SSWS tokens.
- Per-app sign-on policy, default deny.
- Terraform is the source of config; click-ops is drift.
- System Log belongs in the SIEM, not just the Okta UI.
Workflow 1 - New SSO App Integration
Ship a new app with SSO and (where possible) provisioning.
Steps
- Choose the protocol. OIDC for modern apps and APIs. SAML only when the app requires it.
- Catalog first. If the app is in the Okta Integration Network (OIN), use the OIN template; do not hand-roll config.
- Pick the sign-on flow.
- OIDC: authorization code + PKCE (public clients) or code + client secret (confidential).
- SAML: signed SHA-256, audience restriction set to the exact SP, NameID explicit.
- Configure trusted origins / redirect URIs to the minimum set.
- Attribute mapping. Only map what the app needs. Explicit transforms, no pass-through.
- Provisioning.
- SCIM inbound if the app supports it (Okta creates users in the app).
- SCIM outbound not typical for apps (HRIS -> Okta path already covers this).
- Without SCIM: JIT provisioning at login; document deprovisioning (often manual).
- Group assignment. Via group rules on HRIS attributes, not manual assignment.
- Sign-On Policy. Create a per-app policy:
- Default deny
- Allow specified groups only
- MFA required (phishing-resistant if sensitive)
- Session lifetime appropriate for app
- Testing. Preview org first, then prod. Test with a non-admin user.
- Rollout. Communications, help desk primer, and a rollback plan (deactivate app, re-enable old SSO).
- Terraform. Import or author resources:
okta_app_oauth/okta_app_saml,okta_app_group_assignment,okta_app_policy_signon.
What ships with it
6 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.
- 8d ago First seen · 296 lines · 90 tokens per session scan A bb560a5662aa
okta is a skill published in the GitHub repository d-padmanabhan/agent-engineering-handbook (17 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 3,584 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…