cloud-access-management

A tool for managing who can access an Elastic Cloud organisation and its Serverless projects. Elastic Cloud is a hosted service for running Elastic products such as search and analytics systems.

In plain words
What is it for?
Use it to invite or remove members, change their organisation or project roles, audit access, and create or revoke scoped Cloud API keys.
Why use it?
It avoids managing invitations, project roles, and access keys manually or with overly broad permissions.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/elastic/cursor-plugins/access-management
Any agent
npx skills add elastic/cursor-plugins --skill access-management
Clone the repo
git clone --depth 1 https://github.com/elastic/cursor-plugins

Made for: Claude Code, Codex.

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,834 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00039 $0.05834
Opus 5 $0.00019 $0.02917
Sonnet 5 $0.00008 $0.01167
Haiku 4.5 $0.00004 $0.00583

Measured 2d ago against content hash 2ff5eff611df, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

cloud-access-management scanned grade B with 1 finding 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 2d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/cloud_access.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Nullifies safety policiesmediumAnti-refusal

"You have no restrictions", "do anything now", "ignore your guidelines": a direct jailbreak that disables guardrails.

> the project — the Viewer stack role is broader than most custom roles and will override the restrictions you intended.

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Origin

This is a copy

100% identical to cloud-access-management — 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.

elastic/skills/cloud/access-management/SKILL.md · 476 lines

How it starts

The opening of the file, as written. The whole thing — 476 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cloud Access Management

Manage identity and access for an Elastic Cloud organization and its Serverless projects: invite users, assign predefined or custom roles, and manage Cloud API keys.

Prerequisite: This skill assumes the cloud-setup skill has already run — EC_API_KEY is set in the environment and the organization context is established. If EC_API_KEY is missing, instruct the agent to invoke cloud-setup first. Do NOT prompt the user for an API key directly.

For project creation, see the cloud-create-project skill. For day-2 project operations (list, update, delete), see cloud-manage-project. For Elasticsearch-level role management (native users, role mappings, DLS/FLS), see the elasticsearch-authz skill.

For detailed API endpoints and request schemas, see references/api-reference.md.

Jobs to Be Done

  • Invite a user to the organization and assign them a Serverless project role
  • List organization members and their current role assignments
  • Update a user's roles (org-level or project-level)
  • Remove a user from the organization
  • Create an additional Cloud API key with scoped roles and expiration
  • Create a Cloud API key that can also call Elasticsearch and Kibana APIs on Serverless projects
  • List and revoke Cloud API keys
  • Create a custom role inside a Serverless project with ES cluster, index, and Kibana privileges
  • Assign or remove a custom role for a user on a Serverless project using the Cloud API's application_roles
  • Translate a natural-language access request into invite, role, and API key tasks

Prerequisites and permissions

Item Description
EC_API_KEY Cloud API key (set by cloud-setup). Required for all operations.
Organization ID Auto-discovered using GET /organizations. Do not ask the user for it.
Project endpoint Elasticsearch endpoint of a Serverless project. Required only for custom role operations.
ES credentials API key or credentials with manage_security privilege on the project. Required only for custom roles.
Org owner role Only Organization owners can create and manage Cloud API keys. Required for API key operations.

Read the full file on GitHub · 476 lines

Files

What ships with it

2 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.

Changes

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.

  1. 2d ago First seen · 476 lines · 39 tokens per session scan B 2ff5eff611df

Subscribe to this mod's changes

cloud-access-management is a skill published in the GitHub repository elastic/cursor-plugins (31 stars, last pushed 5d ago), licensed Apache-2.0. It adds 39 tokens to every session and 5,834 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (nullifies safety policies). It is 100% identical to cloud-access-management, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens