Individual skill
cursor-api-key-management
Configure BYOK API keys for OpenAI, Anthropic, Google, Azure, and custom models in Cursor. Triggers on "cursor api key", "cursor openai key", "cursor anthropic key", "own api key cursor", "BYOK cursor", "cursor azure key".
plugins/saas-packs/cursor-pack/skills/cursor-api-key-management/SKILL.md
Source commit 0500b275e963c027f6b410e8c49c0446945c574e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 12, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,916
- Repository last updated
- Nov 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- automation Repository topic
- claude-code Repository topic
- devops Repository topic
- mcp Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- llm Repository topic
- saas Declared skill tag
- cursor Declared skill tag
- api Declared skill tag
- authentication Declared skill tag
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 8,682 bytesreferences/configuration-methods.mddoc · 732 bytesreferences/cost-management.mddoc · 758 bytesreferences/errors.mddoc · 599 bytesreferences/examples.mddoc · 490 bytesreferences/implementation.mddoc · 827 bytesreferences/security-best-practices.mddoc · 825 bytesreferences/supported-providers.mddoc · 854 bytesreferences/team-key-management.mddoc · 654 bytesreferences/troubleshooting.mddoc · 876 bytes
Read excerpt
# Cursor API Key Management
## Overview
Manage any Cursor BYOK/provider credentials as individual, least-privilege secrets with approved routing, ownership, rotation, spending limits, and exposure response.
## Prerequisites
- An approved provider/model route, named key owner, secrets-manager integration, and budget policy.
- Confirmation that BYOK is permitted for the intended data classification and tenant configuration.
## Instructions
1. Issue one scoped key per owner or approved service through the provider/secrets manager.
2. Configure it through the approved UI/injection path; never commit it, paste it into rules, or share it between users.