Agent skill

Implementing Zero Trust For SaaS Applications

by mukul975 in mukul975/Anthropic-Cybersecurity-Skills

Secures SaaS apps (Microsoft 365, Google Workspace, Salesforce, Slack) via CASB/SSPM deployment, conditional access policies, OAuth app governance, and session-level DLP controls enforcing identity…

Apache-2.0Auto-check passedBackend & APIs

Install Implementing Zero Trust For SaaS Applications

skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-zero-trust-for-saas-applications -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills implementing-zero-trust-for-saas-applications --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/implementing-zero-trust-for-saas-applications .claude/skills/implementing-zero-trust-for-saas-applications && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
implementing-zero-trust-for-saas-applications
GitHub stars
34k
Token cost
~2.9k tokens
SKILL.md length
564 words
Files
4 (incl. scripts, references)
Skills in repo
644
Repo updated
First seen
Licence
Apache-2.0

At a glance

Secures SaaS apps (Microsoft 365, Google Workspace, Salesforce, Slack) via CASB/SSPM deployment, conditional access policies, OAuth app governance, and session-level DLP controls enforcing identity…

  • Works in 5 steps: Federate SaaS Authentication Through… → Create Conditional Access Policies for… → Deploy CASB for Shadow IT Discovery and… → …
  • Adding MFA/device-compliance conditional access
  • SKILL.md covers When to Use, Prerequisites, Workflow and Key Concepts, plus 3 more sections
  • Runs Python scripts from its folder; calls curl; reaches api.cloudappsecurity.com and graph.microsoft.com; needs MDCA_API_TOKEN

What it does

Implementing Zero Trust For SaaS Applications is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Secures SaaS apps (Microsoft 365, Google Workspace, Salesforce, Slack) via CASB/SSPM deployment, conditional access policies, OAuth app governance, and session-level DLP controls enforcing identity verification and device compliance. Use when adding MFA/device-compliance conditional access, discovering shadow IT, governing OAuth consent grants, or applying session controls to sensitive SaaS data.

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/api-reference.md` and `scripts/agent.py`).

It sits in Backend & APIs, covering Cloud office suites, OAuth and OpenID Connect and CRM management. It works with Google Workspace, Microsoft 365, Salesforce and Slack. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.

When your agent uses it

  • Adding MFA/device-compliance conditional access
  • Discovering shadow IT
  • Governing OAuth consent grants
  • Applying session controls to sensitive SaaS data

Example prompts

  • “Use the implementing-zero-trust-for-saas-applications skill to secure SaaS apps (Microsoft 365, Google Workspace, Salesforce, Slack) via CASB/SSPM…”
  • “/implementing-zero-trust-for-saas-applications”

Requirements

  • Python 3
  • A credential in MDCA_API_TOKEN

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Federate SaaS Authentication Through Identity Provider
  2. Create Conditional Access Policies for SaaS Applications
  3. Deploy CASB for Shadow IT Discovery and App Governance
  4. Configure OAuth App Governance
  5. Implement SaaS Security Posture Management (SSPM)

What it can do on your machine

Read from SKILL.md and the folder at commit 54a7988. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.cloudappsecurity.com
    • graph.microsoft.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • MDCA_API_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Implementing Zero Trust For SaaS Applications loads about 2.9k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 111 tokens; SKILL.md has 564 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~111
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from mukul975/Anthropic-Cybersecurity-Skills at commit 54a7988, republished under its Apache-2.0 licence (© mukul975). 564 words, ~2,868 tokens.

Download SKILL.mdSave it as .claude/skills/implementing-zero-trust-for-saas-applications/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
implementing-zero-trust-for-saas-applications
description
Secures SaaS apps (Microsoft 365, Google Workspace, Salesforce, Slack) via CASB/SSPM deployment, conditional access policies, OAuth app governance, and session-level DLP controls enforcing identity verification and device compliance. Use when adding MFA/device-compliance conditional access, discovering shadow IT, governing OAuth consent grants, or applying session controls to sensitive SaaS data.
domain
cybersecurity
subdomain
zero-trust-architecture
tags
zero-trust, saas-security, casb, sspm, conditional-access, oauth-governance, session-controls
version
1.0
author
mahipal
license
Apache-2.0
nist_csf
PR.AA-01, PR.AA-05, PR.IR-01, GV.PO-01
mitre_attack
T1078, T1190, T1059, T1078.004, T1530

Implementing Zero Trust for SaaS Applications

When to Use

  • When securing access to SaaS applications (Microsoft 365, Google Workspace, Salesforce, Slack)
  • When implementing conditional access policies requiring MFA and device compliance for SaaS
  • When deploying CASB for shadow IT discovery and unsanctioned app blocking
  • When enforcing session-level controls (DLP, download restrictions) for sensitive SaaS data
  • When governing OAuth application permissions and detecting excessive consent grants

Do not use as a replacement for SaaS-native security controls (configure those first), for applications with no SAML/OIDC support, or when SaaS vendor does not support API integration for CASB/SSPM.

Prerequisites

  • Identity provider with conditional access: Microsoft Entra ID P1/P2, Okta
  • CASB solution: Microsoft Defender for Cloud Apps, Netskope, or Zscaler CASB
  • SaaS applications configured with SSO via SAML 2.0 or OIDC
  • MDM enrollment for device compliance signals (Intune, Jamf)
  • DLP policies defined for sensitive data categories

Workflow

Step 1: Federate SaaS Authentication Through Identity Provider

Centralize authentication for all SaaS applications through a single IdP.

powershell
# Configure SAML SSO for Salesforce via Entra ID
Connect-MgGraph -Scopes "Application.ReadWrite.All"

# Create enterprise application for Salesforce
$app = New-MgServicePrincipal -AppId "SALESFORCE_APP_ID" -DisplayName "Salesforce"

# Configure SAML SSO settings
$samlSettings = @{
    preferredSingleSignOnMode = "saml"
    samlSingleSignOnSettings = @{
        relayState = ""
    }
}
Update-MgServicePrincipal -ServicePrincipalId $app.Id -BodyParameter $samlSettings

# Assign user groups to the application
New-MgServicePrincipalAppRoleAssignment -ServicePrincipalId $app.Id -BodyParameter @{
    principalId = "SALES_GROUP_ID"
    resourceId = $app.Id
    appRoleId = "DEFAULT_ROLE_ID"
}
Step 2: Create Conditional Access Policies for SaaS Applications

Enforce identity and device requirements before granting SaaS access.

powershell
# Block access from non-compliant devices to sensitive SaaS apps
$policy = @{
    displayName = "ZT - Require Compliant Device for SaaS"
    state = "enabled"
    conditions = @{
        applications = @{
            includeApplications = @("SALESFORCE_APP_ID", "M365_APP_ID", "SLACK_APP_ID")
        }
        users = @{
            includeUsers = @("All")
            excludeGroups = @("BREAK_GLASS_GROUP")
        }
        clientAppTypes = @("browser", "mobileAppsAndDesktopClients")
    }
    grantControls = @{
        operator = "AND"
        builtInControls = @("mfa", "compliantDevice")
    }
    sessionControls = @{
        cloudAppSecurity = @{
            isEnabled = $true
            cloudAppSecurityType = "mcasConfigured"
        }
        signInFrequency = @{
            value = 8
            type = "hours"
            isEnabled = $true
        }
    }
}
New-MgIdentityConditionalAccessPolicy -BodyParameter $policy

# Block downloads on unmanaged devices
$downloadPolicy = @{
    displayName = "ZT - Block Downloads on Unmanaged Devices"
    state = "enabled"
    conditions = @{
        applications = @{ includeApplications = @("SHAREPOINT_APP_ID") }
        users = @{ includeUsers = @("All") }
        devices = @{
            deviceFilter = @{
                mode = "include"
                rule = "device.isCompliant -ne True -or device.trustType -ne 'ServerAD'"
            }
        }
    }
    sessionControls = @{
        cloudAppSecurity = @{
            isEnabled = $true
            cloudAppSecurityType = "mcasConfigured"
        }
    }
}
New-MgIdentityConditionalAccessPolicy -BodyParameter $downloadPolicy
Step 3: Deploy CASB for Shadow IT Discovery and App Governance

Configure Microsoft Defender for Cloud Apps to discover and control SaaS usage.

bash
# Query discovered cloud apps via Defender for Cloud Apps API
curl -X GET "https://api.cloudappsecurity.com/api/v1/discovery/" \
  -H "Authorization: Token ${MDCA_API_TOKEN}" \
  -H "Content-Type: application/json"

# Get list of unsanctioned apps
curl -X GET "https://api.cloudappsecurity.com/api/v1/discovery/discovered_apps/" \
  -H "Authorization: Token ${MDCA_API_TOKEN}" \
  -d '{
    "filters": {
      "appTag": {"eq": "unsanctioned"},
      "traffic": {"gte": 1000}
    },
    "sortField": "traffic",
    "sortDirection": "desc"
  }'

# Create session policy for DLP enforcement
curl -X POST "https://api.cloudappsecurity.com/api/v1/policies/" \
  -H "Authorization: Token ${MDCA_API_TOKEN}" \
  -d '{
    "name": "Block PII Upload to SaaS",
    "policyType": "SESSION",
    "severity": "HIGH",
    "enabled": true,
    "sessionPolicyType": "CONTROL_UPLOAD",
    "filters": {
      "fileType": {"eq": ["DOCUMENT", "SPREADSHEET"]},
      "contentInspection": {
        "dataType": ["CREDIT_CARD", "SSN", "PASSPORT"]
      }
    },
    "actions": {
      "block": true,
      "notify": {
        "emailRecipients": ["security-team@company.com"]
      }
    }
  }'
Step 4: Configure OAuth App Governance

Review and restrict OAuth application permissions to prevent excessive consent.

powershell
# Query OAuth apps with high-privilege permissions
$oauthApps = Invoke-MgGraphRequest -Method GET `
  "https://graph.microsoft.com/v1.0/servicePrincipals?\$filter=tags/any(t:t eq 'WindowsAzureActiveDirectoryIntegratedApp')&\$select=displayName,appId,oauth2PermissionScopes"

# Review consent grants
$grants = Get-MgOauth2PermissionGrant -All
$highRisk = $grants | Where-Object {
    $_.Scope -match "Mail.ReadWrite|Files.ReadWrite.All|Directory.ReadWrite.All"
}

Write-Host "High-risk OAuth grants: $($highRisk.Count)"
$highRisk | ForEach-Object {
    $sp = Get-MgServicePrincipal -ServicePrincipalId $_.ClientId
    Write-Host "  App: $($sp.DisplayName) | Scope: $($_.Scope) | Type: $($_.ConsentType)"
}

# Configure app consent policy to require admin approval
$consentPolicy = @{
    displayName = "Require Admin Approval for High-Risk Permissions"
    conditions = @{
        clientApplications = @{ includeAllClientApplications = $true }
        permissions = @{
            permissionClassification = "high"
            permissions = @(
                @{ permissionValue = "Mail.ReadWrite"; permissionType = "delegated" }
                @{ permissionValue = "Files.ReadWrite.All"; permissionType = "delegated" }
            )
        }
    }
}
Step 5: Implement SaaS Security Posture Management (SSPM)

Audit and remediate SaaS security configuration drift.

bash
# Query SaaS security posture via CASB API
curl -X GET "https://api.cloudappsecurity.com/api/v1/security_config/" \
  -H "Authorization: Token ${MDCA_API_TOKEN}" \
  -d '{"app": "Microsoft 365"}'

# Common SSPM checks:
# - MFA enforcement for all admin accounts
# - External sharing restrictions in SharePoint/OneDrive
# - Email forwarding rules to external domains blocked
# - Idle session timeout configured (< 8 hours)
# - Legacy authentication protocols disabled
# - Admin consent workflow enabled
# - Conditional access policies active
# - Audit logging enabled for all services

Key Concepts

TermDefinition
CASBCloud Access Security Broker - intermediary enforcing security policies between users and SaaS applications
SSPMSaaS Security Posture Management - continuous monitoring of SaaS application security configurations
OAuth GovernanceReview and control of third-party application permissions granted through OAuth consent flows
Session ControlsReal-time access restrictions (block downloads, DLP inspection, watermarking) applied during active SaaS sessions
Shadow ITUnauthorized SaaS applications used by employees without IT approval or security review
Conditional AccessPolicy engine evaluating identity, device, location, and risk signals before granting SaaS access
Show full SKILL.md (243 more words)Show less

Tools & Systems

  • Microsoft Defender for Cloud Apps: CASB providing shadow IT discovery, session controls, DLP, and SSPM
  • Microsoft Entra ID Conditional Access: Policy engine for identity-based access control to SaaS applications
  • Netskope CASB: Cloud-native CASB with inline and API-based SaaS security controls
  • Okta Identity Governance: OAuth app governance and access certification for SaaS applications
  • SSPM Tools: AppOmni, Adaptive Shield, Valence Security for SaaS configuration monitoring

Common Scenarios

Scenario: Securing Microsoft 365 and Salesforce for 1,000-User Organization

Context: A professional services firm with 1,000 users uses Microsoft 365, Salesforce, Slack, and 20+ other SaaS apps. Several data breaches in the industry drive a zero trust initiative for all SaaS access.

Approach:

  1. Federate all SaaS authentication through Entra ID with SAML SSO
  2. Create conditional access policies requiring MFA + compliant device for all SaaS apps
  3. Deploy Defender for Cloud Apps for shadow IT discovery (identify 150+ unauthorized apps)
  4. Mark unauthorized apps as unsanctioned and block via SWG/proxy
  5. Configure session controls: block downloads on unmanaged devices, DLP for file uploads
  6. Review OAuth app permissions: revoke 45 high-risk consent grants, enable admin approval workflow
  7. Enable SSPM monitoring for Microsoft 365 and Salesforce configurations
  8. Set up weekly automated posture reports for security leadership

Pitfalls: Conditional access policies need break-glass exclusions. Some legacy SaaS apps may not support modern authentication. Session controls require proxy-based CASB which can impact performance. OAuth app revocation may break integrations; coordinate with app owners first.

Output Format

Zero Trust SaaS Security Report
==================================================
Organization: ProServices Corp
Report Date: 2026-02-23

SAAS INVENTORY:
  Sanctioned Apps: 25
  Unsanctioned (blocked): 127
  Shadow IT Users: 342 (discovered in last 30 days)

CONDITIONAL ACCESS:
  Policies active: 8
  Sign-ins evaluated: 456,789
  Blocked by policy: 2,345 (0.5%)
  MFA enforced: 100% of sign-ins

DEVICE COMPLIANCE:
  Compliant device required: All 25 sanctioned apps
  Sign-ins from compliant: 448,123 (98.1%)
  Sign-ins blocked (non-compliant): 8,666

CASB / DLP:
  DLP violations detected: 89
  Files blocked from upload: 34
  Downloads blocked (unmanaged): 1,234

OAUTH GOVERNANCE:
  Total OAuth apps: 312
  High-risk permissions: 12 (reviewed)
  Revoked consents: 45
  Pending admin approval: 8

SSPM FINDINGS:
  Critical misconfigurations: 3
  High: 7
  Medium: 15
  Remediated this month: 18

© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in skills/implementing-zero-trust-for-saas-applications of mukul975/Anthropic-Cybersecurity-Skills.

  • SKILL.md
  • LICENSE
  • references/api-reference.md
  • scripts/agent.py

Open the folder on GitHubat commit 54a7988

Compare with similar skills

Implementing Zero Trust For SaaS Applications next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Implementing Zero Trust For SaaS Applications compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Implementing Zero Trust For SaaS Applications this skillmukul975/Anthropic-Cybersecurity-Skills34k—~2.9kAutomated safety check: PassApache-2.0
API GatewayCraftOS-dev/CraftBot3923 repos~7.1kAutomated safety check: PassMIT
Cloud App Security Posturevinayaklatthe/microsoft-security-skills175—~2.1kAutomated safety check: PassMIT
Latchkeyimbue-ai/latchkey130—~1.3kAutomated safety check: PassMIT
Sf IntegrationJaganpro/sf-skills424—~1.5kAutomated safety check: PassMIT
Slack To Teamsmicrosoft/work-iq1k1 repos~2.3kAutomated safety check: PassCustom licence

Similar skills

  • API Gateway

    CraftOS-dev/CraftBot

    Connect to 100+ APIs (Google Workspace, Microsoft 365, Notion, Slack, Airtable, HubSpot, etc.) with managed OAuth.

    392 GitHub starsUsed in 3 repos~7.1k tokens
    Backend & APIsAuto-check passed
  • Cloud App Security Posture

    vinayaklatthe/microsoft-security-skills

    Guidance for cloud and SaaS security posture management - combining Defender for Cloud CSPM (IaaS/PaaS) and Defender for Cloud Apps SSPM (SaaS) to assess and harden posture across cloud and SaaS apps.

    175 GitHub stars~2.1k tokensUpdated 3 mo ago
    SecurityAuto-check passed
  • Latchkey

    imbue-ai/latchkey

    Interact with third-party or self-hosted services (Slack, Google Workspace, Dropbox, GitHub, Linear, Coolify...) using their HTTP APIs on the user's behalf.

    130 GitHub stars~1.3k tokensUpdated today
    Backend & APIsAuto-check passed
  • Sf Integration

    Jaganpro/sf-skills

    Salesforce integration architecture with 120-point scoring. An agent skill from Jaganpro/sf-skills.

    424 GitHub stars~1.5k tokensUpdated 5 mo ago
    Backend & APIsAuto-check passed
  • Slack To Teams

    microsoft/work-iq

    Official

    Sub-skill of microsoft-365-agents-toolkit. An agent skill from microsoft/work-iq.

    1k GitHub starsUsed in 1 repo~2.3k tokens
    Documents & OfficeAuto-check passed
  • Google Workspace

    RedWoodOG/Hermes-Desktop

    Gmail, Calendar, Drive, Contacts, Sheets, and Docs integration via Python.

    177 GitHub stars~2.1k tokensUpdated 4 mo ago
    Backend & APIsAuto-check passed

More from mukul975/Anthropic-Cybersecurity-Skills

All 644 skills in this repo
  • Campaign Attribution Evidence Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.

    34k GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Go Malware Analysis in Ghidra

    mukul975/Anthropic-Cybersecurity-Skills

    Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • LNK and Jump List Forensics

    mukul975/Anthropic-Cybersecurity-Skills

    Guides forensic analysis of Windows LNK shortcut files and Jump Lists with LECmd, JLECmd and manual parsing to show file access and program execution.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Malware Persistence Analysis with Autoruns

    mukul975/Anthropic-Cybersecurity-Skills

    Hunts Windows malware persistence with Sysinternals Autoruns, covering run keys, services, scheduled tasks and drivers, with baseline comparison.

    34k GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • NTFS MFT Deleted File Recovery

    mukul975/Anthropic-Cybersecurity-Skills

    Guides a Windows forensic examination of the NTFS Master File Table to recover deleted-file evidence, build timelines and spot timestomping.

    34k GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Network Covert Channel Analysis

    mukul975/Anthropic-Cybersecurity-Skills

    Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.

    34k GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Implementing Zero Trust For SaaS Applications

What does Implementing Zero Trust For SaaS Applications do?

Secures SaaS apps (Microsoft 365, Google Workspace, Salesforce, Slack) via CASB/SSPM deployment, conditional access policies, OAuth app governance, and session-level DLP controls enforcing identity…. Implementing Zero Trust For SaaS Applications is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Secures SaaS apps (Microsoft 365, Google Workspace, Salesforce, Slack) via CASB/SSPM deployment, conditional access policies, OAuth app governance, and session-level DLP controls enforcing identity verification and device compliance.

When should I use Implementing Zero Trust For SaaS Applications?

Implementing Zero Trust For SaaS Applications fits situations like: adding MFA/device-compliance conditional access; discovering shadow IT; governing OAuth consent grants; applying session controls to sensitive SaaS data.

How do I install Implementing Zero Trust For SaaS Applications in Claude Code?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-zero-trust-for-saas-applications -a claude-code`. Or copy the skill folder (skills/implementing-zero-trust-for-saas-applications in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/implementing-zero-trust-for-saas-applications in your project. Claude Code loads it when a task matches its description.

How do I install Implementing Zero Trust For SaaS Applications in Codex?

Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-zero-trust-for-saas-applications -a codex`. Or copy the skill folder (skills/implementing-zero-trust-for-saas-applications in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/implementing-zero-trust-for-saas-applications in your project. Codex loads it when a task matches its description.

Can I use Implementing Zero Trust For SaaS Applications in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-zero-trust-for-saas-applications -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implementing-zero-trust-for-saas-applications, .gemini/skills/implementing-zero-trust-for-saas-applications, .github/skills/implementing-zero-trust-for-saas-applications and .opencode/skills/implementing-zero-trust-for-saas-applications in your project.

What does Implementing Zero Trust For SaaS Applications need to run?

Going by SKILL.md and its folder, Implementing Zero Trust For SaaS Applications needs Python for the scripts in its folder, the command-line tools its instructions call (curl) and credentials named MDCA_API_TOKEN. Our summary lists: Python 3; A credential in MDCA_API_TOKEN.

Does Implementing Zero Trust For SaaS Applications access the network?

SKILL.md names 2 domains. In commands or code: api.cloudappsecurity.com and graph.microsoft.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Implementing Zero Trust For SaaS Applications safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Implementing Zero Trust For SaaS Applications use?

Implementing Zero Trust For SaaS Applications is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Implementing Zero Trust For SaaS Applications use?

About 2.9k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 430 tokens, read only when the agent opens those files.

What are the alternatives to Implementing Zero Trust For SaaS Applications?

Skills that share tags, products or a category with Implementing Zero Trust For SaaS Applications: API Gateway (CraftOS-dev/CraftBot, 392 stars), Cloud App Security Posture (vinayaklatthe/microsoft-security-skills, 175 stars), Latchkey (imbue-ai/latchkey, 130 stars) and Sf Integration (Jaganpro/sf-skills, 424 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Implementing Zero Trust For SaaS Applications?

mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 33,993 GitHub stars. The repository holds 644 skills in this directory. The repository was last updated on August 31, 2026.

Source: mukul975/Anthropic-Cybersecurity-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.