New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Security Scan

by PacificStudio in PacificStudio/openase

Review trust boundaries, auth, input handling, secrets, and dependency risk before release.

Apache-2.0Auto-check passedSecurity

Install Security Scan

skills CLI
$ npx skills add PacificStudio/openase --skill security-scan -a claude-code

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

GitHub CLI
$ gh skill install PacificStudio/openase security-scan --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/PacificStudio/openase.git skills-src && mkdir -p .claude/skills && cp -r skills-src/internal/builtin/skills/security-scan .claude/skills/security-scan && 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
security-scan
GitHub stars
268
Token cost
~865 tokens
SKILL.md length
422 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
Apache-2.0

At a glance

Review trust boundaries, auth, input handling, secrets, and dependency risk before release.

  • Works in 7 steps: Map the attack surface. → Review authentication and authorization. → Review input handling and injection… → …
  • Tasks that involve Security review
  • SKILL.md covers Overview, When To Use, Review Workflow and Security Checklist, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Security Scan is an agent skill from PacificStudio/openase. Review trust boundaries, auth, input handling, secrets, and dependency risk before release.

Its SKILL.md is about 870 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Security, covering Security review. The repository describes itself as: Ticket-Driven Automated Software Engineering. OpenASE is an all-in-one platform that turns tickets into working code — AI agents automatically pick up tickets, execute workflows… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Security review

Example prompts

  • “/security-scan”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Map the attack surface.
  2. Review authentication and authorization.
  3. Review input handling and injection surfaces.
  4. Review secrets and cryptography.
  5. Review dependency and configuration risk.
  6. Review detection and recovery.
  7. Report severity-rated findings with remediation guidance.

What it can do on your machine

Read from SKILL.md and the folder at commit e530faf. 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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

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

  • Credentials

    Names no API keys, tokens, secrets or passwords.

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

Context cost

Security Scan loads about 865 tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 422 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~26
When it runs · the whole SKILL.md, loaded when a task matches
~865

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from PacificStudio/openase at commit e530faf, republished under its Apache-2.0 licence (© PacificStudio). 422 words, ~865 tokens.

Download SKILL.mdSave it as .claude/skills/security-scan/SKILL.md (or your agent's skills folder).
name
security-scan
description
Review trust boundaries, auth, input handling, secrets, and dependency risk before release.

Security Scan

Overview

Conduct a security-focused review of the code or change set. Map trust boundaries first, then inspect how untrusted input, credentials, permissions, dependencies, and deployment defaults are handled.

When To Use

  • After adding or changing authentication or authorization logic.
  • After adding new API endpoints, uploads, background jobs, or external integrations.
  • Before production deployment.
  • When the change handles untrusted input, secrets, tokens, files, or network calls.
  • When the user explicitly requests a security review or audit.

Review Workflow

  1. Map the attack surface.

    • Entry points, user-controlled input, file access, network access, storage boundaries, and privileged operations.

  2. Review authentication and authorization.

    • Authentication bypasses.
    • Missing authorization checks.
    • Confused trust boundaries between user, service, and admin actions.

  3. Review input handling and injection surfaces.

    • SQL, NoSQL, shell, template, and path injection.
    • XSS and unsafe HTML rendering.
    • SSRF, open redirects, and unsafe outbound requests.

  4. Review secrets and cryptography.

    • Hardcoded keys, tokens, passwords, or connection strings.
    • Weak password hashing or unsafe token generation.
    • Sensitive data exposure in logs, errors, or client payloads.

  5. Review dependency and configuration risk.

    • Known vulnerable dependencies.
    • Overly permissive defaults.
    • Missing secure headers, unsafe CORS, or weak production settings.

  6. Review detection and recovery.

    • Are important security-relevant failures logged?
    • Would an operator be able to detect abuse or investigate an incident?

  7. Report severity-rated findings with remediation guidance.

    • CRITICAL: exploitable issue or active secret exposure; block deployment.
    • HIGH: serious vulnerability or major trust-boundary weakness; fix before release.
    • MEDIUM: meaningful hardening gap or partial control failure.
    • LOW: defense-in-depth improvement or cleanup.
Show full SKILL.md (170 more words)Show less

Security Checklist

  • Authentication and authorization boundaries are explicit and enforced.
  • Untrusted input is validated, normalized, and escaped at the correct boundary.
  • Queries and commands are parameterized and never built from raw user input.
  • Secrets are not stored in source, test fixtures, logs, or client-visible responses.
  • File and network access respect allowlists and path or host validation where appropriate.
  • Dependency versions and deployment defaults do not introduce known high-risk vulnerabilities.

Operating Rules

  • Think in trust boundaries and attacker-controlled inputs, not only code style.
  • Prefer reproducible exploit paths over vague warnings.
  • Name the impacted asset or permission boundary for every serious finding.
  • Include a practical remediation path, not just the vulnerability label.
  • If no critical issues are found, still call out hardening gaps and any unreviewed surfaces.

Default Deliverable Shape

Return these sections:

  1. Attack Surface
  2. Findings - ordered by severity with file and line references where possible.
  3. Exploit Path / Impact - why each important issue matters.
  4. Remediation - concrete fixes and safer patterns.
  5. Residual Risks - remaining uncertainty or unreviewed areas.

© PacificStudio, 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

Just SKILL.md in internal/builtin/skills/security-scan of PacificStudio/openase.

Open the folder on GitHubat commit e530faf

Compare with similar skills

Security Scan 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.

Security Scan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Security Scan this skillPacificStudio/openase268—~865Automated safety check: PassApache-2.0
Deepsec Documentation Guidevercel-labs/deepsec8.1k—~956Automated safety check: PassApache-2.0
Kubernetes Network Security Auditkubeshark/kubeshark12k—~7.3kAutomated safety check: NotesApache-2.0
Native Dependency Updatemono/SkiaSharp5.6k—~4.1kAutomated safety check: PassMIT
Semgrep Security Scantrailofbits/skills7.4k—~3.7kAutomated safety check: NotesCC-BY-SA-4.0
Skillward AuditFangcun-AI/SkillWard143—~2.9kAutomated safety check: PassCustom licence

Similar skills

  • Deepsec Documentation Guide

    vercel-labs/deepsec

    Official

    Points the agent at deepsec's own docs to answer questions about initializing, configuring, resuming, scanning with and extending the vulnerability scanner.

    8.1k GitHub stars~956 tokensUpdated 8 days ago
    SecurityAuto-check passed

  • Kubernetes Network Security Audit

    kubeshark/kubeshark

    Hunts for compromised workloads and malicious traffic in a Kubernetes cluster by sweeping network data through Kubeshark MCP, mapped to MITRE ATT&CK.

    12k GitHub stars~7.3k tokensUpdated 7 days ago
    SecurityAuto-check: notes

  • Native Dependency Update

    mono/SkiaSharp

    Update native dependencies (libpng, libexpat, zlib, libwebp, harfbuzz, freetype, libjpeg-turbo, etc.) in SkiaSharp's Skia fork.

    5.6k GitHub stars~4.1k tokensUpdated today
    SecurityAuto-check passed

  • Semgrep Security Scan

    trailofbits/skills

    Official

    Detects languages, proposes rulesets for approval, then runs the approved Semgrep scan across a codebase and merges the output into one SARIF file.

    7.4k GitHub stars~3.7k tokensUpdated 5 days ago
    SecurityAuto-check: notes

  • Skillward Audit

    Fangcun-AI/SkillWard

    Security-audit a third-party skill bundle (folder with SKILL.md, or .zip / .tar.gz archive) before installing it, using the SkillWard cloud scanner.

    143 GitHub stars~2.9k tokensUpdated 2 mo ago
    SecurityAuto-check passed

  • Security Audit

    TheDecipherist/claude-code-mastery

    Checks a codebase for hardcoded secrets, vulnerable dependencies, weak input handling, weak authentication and unsafe transport settings before deployment or merge.

    550 GitHub stars~1.3k tokensUpdated 5 mo ago
    SecurityAuto-check: notes

More from PacificStudio/openase

All 14 skills in this repo

  • Deploy Coolify Review Env

    PacificStudio/openase

    Create or update a branch-scoped Coolify review environment with one command, and delete it with one command.

    268 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check: notes

  • Deploy Openase

    PacificStudio/openase

    Build and locally redeploy OpenASE from the current branch, including web static assets and the Go binary, then restart the local service and verify health.

    268 GitHub stars~564 tokensUpdated 1 mo ago
    Auto-check: notes

  • Local Bootstrap CLI Auth Debug

    PacificStudio/openase

    Diagnose and repair OpenASE CLI access in local bootstrap mode.

    268 GitHub stars~778 tokensUpdated 1 mo ago
    Auto-check passed

  • Push

    PacificStudio/openase

    Push current branch changes to origin and create or update the corresponding pull request for OpenASE; use when asked to push, publish updates, or create a pull request.

    268 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

  • Report Issue

    PacificStudio/openase

    Create a detailed GitHub issue for OpenASE and add it to the OpenASE Automation project with a caller-selected status (defaults to Todo).

    268 GitHub stars~631 tokensUpdated 1 mo ago
    Auto-check: notes

  • Auto Harness

    PacificStudio/openase

    Diagnose and strengthen a repository's harness layer: AGENTS.md rules, knowledge layout, architecture boundaries, lint and type gates, API and generated-client contracts, test scaffolding…

    268 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Security Scan

What does Security Scan do?

Review trust boundaries, auth, input handling, secrets, and dependency risk before release. Security Scan is an agent skill from PacificStudio/openase. Review trust boundaries, auth, input handling, secrets, and dependency risk before release.

When should I use Security Scan?

Security Scan fits situations like: tasks that involve Security review.

How do I install Security Scan in Claude Code?

Run `npx skills add PacificStudio/openase --skill security-scan -a claude-code`. Or copy the skill folder (internal/builtin/skills/security-scan in PacificStudio/openase) into .claude/skills/security-scan in your project. Claude Code loads it when a task matches its description.

How do I install Security Scan in Codex?

Run `npx skills add PacificStudio/openase --skill security-scan -a codex`. Or copy the skill folder (internal/builtin/skills/security-scan in PacificStudio/openase) into .agents/skills/security-scan in your project. Codex loads it when a task matches its description.

Can I use Security Scan 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 PacificStudio/openase --skill security-scan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/security-scan, .gemini/skills/security-scan, .github/skills/security-scan and .opencode/skills/security-scan in your project.

What does Security Scan need to run?

SKILL.md names no scripts, command-line tools or credentials: Security Scan is instructions for the agent only.

Does Security Scan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Security Scan 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. Review the folder before installing.

What licence does Security Scan use?

Security Scan is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Security Scan use?

About 865 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Security Scan?

Skills that share tags, products or a category with Security Scan: Deepsec Documentation Guide (vercel-labs/deepsec, 8.1k stars), Kubernetes Network Security Audit (kubeshark/kubeshark, 12k stars), Native Dependency Update (mono/SkiaSharp, 5.6k stars) and Semgrep Security Scan (trailofbits/skills, 7.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Security Scan?

PacificStudio (a GitHub organization) maintains it in PacificStudio/openase, which has 268 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on August 9, 2026.

Source: PacificStudio/openase on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.