security-scan

security-scan is a skill for Claude Code, Codex from PacificStudio/openase. It costs 21 tokens per session (687 once invoked), scanned A, original, Apache-2.0.

A security-focused code review that examines how software handles users, permissions, outside input, secrets, dependencies, and deployment settings.

In plain words
What is it for?
Use it after changes to authentication, APIs, uploads, background jobs, or external integrations, and before production deployment. It checks trust boundaries, input and injection risks, secrets, cryptography, and dependency risks.
Why use it?
It helps uncover ways an attacker could bypass access controls, inject unsafe data, expose credentials, or misuse network and file operations before release.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it after changes to authentication, APIs, uploads, background jobs, or external integrations, and before production deployment. It checks trust boundaries, input and injection risks, secrets, cryptography, and dependency risks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pacificstudio/openase/security-scan
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.

Any agent
npx skills add PacificStudio/openase --skill security-scan
Clone the repo
git clone --depth 1 https://github.com/PacificStudio/openase

Made for: Claude Code, Codex.

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

agentmods badge for security-scan

README.md
[![agentmods](https://agentmods.dev/badge/skills/pacificstudio/openase/security-scan/github.svg)](https://agentmods.dev/skills/pacificstudio/openase/security-scan)
Your own site
<a href="https://agentmods.dev/skills/pacificstudio/openase/security-scan"><img src="https://agentmods.dev/badge/skills/pacificstudio/openase/security-scan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for security-scan

Your own site · 80×15
<a href="https://agentmods.dev/skills/pacificstudio/openase/security-scan"><img src="https://agentmods.dev/badge/skills/pacificstudio/openase/security-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 687 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found 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.1 $0.00021 $0.00687
Opus 5.5 $0.00008 $0.00275
Sonnet 5.5 $0.00004 $0.00137
Haiku 4.5 $0.00002 $0.00069

Measured 1mo ago against content hash 63138340a990, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

security-scan 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 1mo 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.

internal/builtin/skills/security-scan/SKILL.md · 81 lines

How it starts

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

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.

Read the full file on GitHub · 81 lines

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. 1mo ago First seen · 81 lines · 21 tokens per session scan A 63138340a990

Subscribe to this mod's changes

security-scan is a skill published in the GitHub repository PacificStudio/openase (269 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 687 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

open-code-review

Performs AI-powered code review on Git changes using the ocr CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply…

alibaba/open-code-review · 98 tokens

learn-from-sage

Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.

kirodotdev/KiroCrew · 56 tokens

review

Comprehensive security and correctness audit. Use for review, deep review, thermo nuclear, or thermonuclear requests and branch or PR diff audits.

vercel/eve · 31 tokens

meta-codereview-current-diff

Read the current uncommitted diff, run three independent reviewers (safety + tests-coverage + style) in parallel, then arbitrate a single BLOCK / BLOCKWITHOVERRIDE / PASSWITHNOTES verdict. Use before commit when you want a multi-perspective second-opinion instead of a single-reviewer agent loop.

opensquilla/opensquilla · 73 tokens

omh-image-cards

This is an OMH img-summary workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 79 tokens

omh-ai-slop-cleaner

This is an OMH ai-slop-cleaner workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 72 tokens