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/cockroachdb/cursor-plugin/configuring-sso-and-scimnpx skills add cockroachdb/cursor-plugin --skill configuring-sso-and-scimgit clone --depth 1 https://github.com/cockroachdb/cursor-pluginWrote 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/cockroachdb/cursor-plugin/configuring-sso-and-scim)<a href="https://agentmods.dev/skills/cockroachdb/cursor-plugin/configuring-sso-and-scim"><img src="https://agentmods.dev/badge/skills/cockroachdb/cursor-plugin/configuring-sso-and-scim.svg" alt="Measured on agentmods" 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 | $0.00091 | $0.05917 |
| Opus 5 | $0.00046 | $0.02959 |
| Sonnet 5 | $0.00018 | $0.01183 |
| Haiku 4.5 | $0.00009 | $0.00592 |
Grade A, and why
configuring-sso-and-scim 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.
This is a copy
100% identical to configuring-sso-and-scim — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 562 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuring SSO and SCIM
Configures Single Sign-On (SSO) and SCIM 2.0 provisioning for CockroachDB across four distinct layers:
- Cloud Console SSO — SAML or OIDC for the CockroachDB Cloud web console
- DB Console SSO — OIDC for the DB Console web UI (Advanced/Enterprise only)
- SQL/Cluster SSO — JWT-based or LDAP/AD authentication for SQL client connections
- SCIM 2.0 — Automated user provisioning on the Cloud Console
Prerequisites
- Console SSO/SCIM: Organization Admin +
ccloudCLI - DB Console/SQL SSO: Cluster admin role + Advanced or Enterprise plan (DB Console SSO not on Standard/Basic)
- LDAP/AD: Self-hosted only (not available on CockroachDB Cloud)
- SCIM 2.0: Enterprise plan required
Configuration Decisions
Before proceeding, determine which layers the user needs. Ask which of the following apply, then follow only the relevant Parts below.
Decision 1 — Cloud Console SSO:
- SAML: Best for enterprise IdPs with existing SAML infrastructure (Okta, Azure AD, PingOne)
- OIDC: Simpler setup, supports Google Workspace and modern IdPs natively
- Skip: Not needed
Decision 2 — DB Console SSO:
- Enable (OIDC): SSO for the DB Console web UI. Requires Advanced or Enterprise plan — not available on Standard or Basic
- Skip: Not needed or plan does not support it
Decision 3 — SQL/Cluster SSO method:
- JWT-based: Cloud-native approach using JWT tokens for SQL client connections. Works on both CockroachDB Cloud and self-hosted clusters
- LDAP/AD: Direct directory authentication against Active Directory or OpenLDAP. Self-hosted only (not available on CockroachDB Cloud)
- Skip: Not needed
Decision 4 — SCIM 2.0 provisioning:
- Enable: Automates user lifecycle (create/update/deactivate) between IdP and Cloud Console. Requires Enterprise plan
- Skip: Manage Cloud Console users manually
Steps
Part 1: Cloud Console SSO
Cloud Console SSO enables SAML or OIDC authentication for the CockroachDB Cloud web console.
What ships with it
1 file 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.
- 4d ago First seen · 562 lines · 91 tokens per session scan A d343f2a9e8a2
configuring-sso-and-scim is a skill published in the GitHub repository cockroachdb/cursor-plugin (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 91 tokens to every session and 5,917 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to configuring-sso-and-scim, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
designing-application-transactions
Guides application developers in designing correct and performant transaction patterns for CockroachDB, covering transaction lifetime, implicit vs explicit transactions, retry handling with exponential backoff, pushing invariants into SQL, selective pessimistic locking, set-based operations, connection pooling…
auditing-table-statistics
Audits optimizer table statistics for staleness, missing coverage, and data quality issues using SHOW STATISTICS. Use when diagnosing poor query performance, unexpected plan changes, or after bulk data changes to identify stale statistics requiring refresh via CREATE STATISTICS.
profiling-transaction-fingerprints
Analyzes transaction fingerprints using aggregated statistics from crdbinternal.transactionstatistics to identify high-retry transactions, contention patterns, and commit latency issues. Provides historical transaction-level analysis to understand which statement combinations are causing retries, contention, or…
auditing-cloud-cluster-security
Audits the security posture of a CockroachDB cluster (Cloud or self-hosted) across network, authentication, authorization, encryption, audit logging, and backup dimensions. Use when assessing cluster security readiness, preparing for compliance reviews, or investigating security configuration gaps.
configuring-sso-and-scim
Configures SSO authentication and SCIM 2.0 provisioning for CockroachDB across four distinct layers — Cloud Console SSO (SAML/OIDC), DB Console SSO (OIDC), SQL/Cluster SSO (JWT or LDAP/AD), and SCIM 2.0 automated provisioning. Use when enabling centralized identity management, setting up SSO for compliance, or…
designing-multi-region-applications
Guides developers in selecting and implementing multi-region patterns for CockroachDB applications, covering active-passive vs active-active architectures, REGIONAL BY ROW, GLOBAL tables, manual geo-partitioning with lease preferences, and live demo setup with validation queries. Use when designing multi-region…