Community생산성 & 협업github.com

getsentry/skill-scanner - 스킬 보안 스캐너

에이전트 스킬의 보안 취약점을 스캔합니다. '스킬 스캔', '스킬 감사', '스킬 보안 검토', '인젝션 확인', 'SKILL.md 검증' 또는 에이전트 스킬 설치 안전성 평가 요청 시 사용합니다. 프롬프트 인젝션, 악성 스크립트, 과도한 권한, 비밀 노출, 공급망 위험을 점검합니다.

skill-scanner - 스킬 보안 스캐너란 무엇인가요?

이 스킬은 AI 에이전트 스킬(예: Claude Code, Cursor, Codex 등)의 보안 취약점을 자동으로 분석하고 진단합니다. 주로 SKILL.md 파일을 검사하여 프롬프트 인젝션 시도, 악성 스크립트 포함, 과도한 권한 요청, API 키나 비밀번호 같은 중요 정보 노출, 그리고 외부 의존성의 공급망 위험을 식별합니다. 사용자가 특정 스킬의 안전성을 평가하려 할 때 이 스킬을 호출할 수 있으며, 다양한 에이전트 플랫폼에서 동작합니다. 스캔 결과는 위험 수준별로 분류되어 보고되므로 개발자가 빠르게 대응할 수 있습니다.

지원 대상✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/getsentry/skills/tree/main/skills/skill-scanner

Installed? Explore more 생산성 & 협업 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

skill-scanner - 스킬 보안 스캐너은(는) 무엇을 하나요?

에이전트 스킬의 보안 취약점을 스캔합니다. "스킬 스캔", "스킬 감사", "스킬 보안 검토", "인젝션 확인", "SKILL.md 검증"과 같은 요청 시 사용하세요. 프롬프트 인젝션, 악성 스크립트, 과도한 권한, 비밀 노출, 공급망 위험을 점검합니다.

사용 방법

스킬을 스캔하려면 다음 명령어를 실행하세요:

skill-scanner scan <skill-path>

또는 URL로 직접 스캔:

skill-scanner scan https://example.com/skill-repo/SKILL.md

검사 항목

항목설명
프롬프트 인젝션SKILL.md에 악의적인 명령을 주입하는 시도 탐지
악성 스크립트셸 명령어, 파이썬 코드 등 실행 가능한 악성 코드 검출
과도한 권한파일 읽기/쓰기, 네트워크 접근 등 불필요한 권한 요청 식별
비밀 노출API 키, 토큰, 비밀번호, SSH 키 등 민감 정보 누출 확인
공급망 위험외부 패키지, 의존성, 다운로드 URL의 안전성 평가

출력 포맷

스캔 결과는 다음 JSON 구조로 반환됩니다:

{
  "risk_level": "high|medium|low",
  "issues": [
    {
      "type": "prompt_injection",
      "severity": "critical",
      "location": "line 42",
      "description": "의심스러운 명령어 주입 시도 발견"
    }
  ],
  "summary": "총 3개의 보안 이슈 발견 (1개 치명적, 2개 중간)"
}

환경 변수

  • SKILL_SCANNER_CONFIG - 설정 파일 경로 (선택 사항)
  • SKILL_SCANNER_CACHE_DIR - 캐시 디렉토리 경로 (선택 사항, 기본값 ~/.skill-scanner/cache)

참고 사항

스캔 결과는 권고 사항입니다. 최종 결정은 항상 사용자가 직접 내리세요. 이 스캐너는 모든 취약점을 보장하지 않습니다.

라이선스

MIT

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

getsentry/agents-md

Creates and maintains concise AGENTS.md and CLAUDE.md project instruction files. Use when asked to create AGENTS.md, update AGENTS.md, maintain agent docs, set up CLAUDE.md, document repository agent conventions, or keep coding-agent instructions minimal and reference-backed.

getsentry/blog-writing-guide

Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this skill.

getsentry/brand-guidelines

Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.

getsentry/claude-settings-audit

Analyze a repository to generate recommended Claude Code settings.json permissions. Use when setting up a new project, auditing existing settings, or determining which read-only bash commands to allow. Detects tech stack, build tools, and monorepo structure.

getsentry/code-simplifier

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.

getsentry/commit

ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.

getsentry/create-branch

Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.

getsentry/django-access-review

Django access control and IDOR security review. Use when reviewing Django views, DRF viewsets, ORM queries, or any Python/Django code handling user authorization. Trigger keywords: "IDOR", "access control", "authorization", "Django permissions", "object permissions", "tenant isolation", "broken access".

getsentry/django-perf-review

Django performance code review. Use when asked to "review Django performance", "find N+1 queries", "optimize Django", "check queryset performance", "database performance", "Django ORM issues", or audit Django code for performance problems.

getsentry/doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

getsentry/find-bugs

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

getsentry/gha-security-review

GitHub Actions security review for workflow exploitation vulnerabilities. Use when asked to "review GitHub Actions", "audit workflows", "check CI security", "GHA security", "workflow security review", or review .github/workflows/ for pwn requests, expression injection, credential theft, and supply chain attacks. Exploitation-focused with concrete PoC scenarios.

getsentry/gh-review-requests

Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member. Use when asked to "find PRs I need to review", "show my review requests", "what needs my review", "fetch GitHub review requests", or "check team review queue".

getsentry/iterate-pr

Iterate on a PR until actionable CI passes and high/medium review feedback is addressed. Use for PR CI failures, review feedback, or green-check loops; do not wait for human approval, draft status, or merge gates.

getsentry/presentation-creator

Create data-driven presentation slides using React, Vite, and Recharts with Sentry branding. Use when asked to "create a presentation", "build slides", "make a deck", "create a data presentation", "build a Sentry presentation". Scaffolds a complete slide-based app with charts, animations, and single-file HTML output.

getsentry/pr-writer

Create, refresh, and rewrite PR titles and descriptions following Sentry conventions. Use when opening a PR, writing or updating a PR title/body/description, refreshing an existing PR after material changes, or preparing branch changes for review.

getsentry/security-review

Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.

getsentry/skill-writer

Create, synthesize, and iteratively improve agent skills following the Agent Skills specification. Use when asked to "create a skill", "write a skill", "synthesize sources into a skill", "improve a skill from positive/negative examples", "update a skill", or "maintain skill docs and registration". Handles source capture, precision passes, authoring, registration, and validation.

getsentry/sred-project-organizer

Take a list of projects and their related documentation, and organize them into the SRED format for submission.

getsentry/sred-work-summary

Go back through the previous year of work and create a Notion doc that groups relevant links into projects that can then be documented as SRED projects.

관련 스킬