테스트·보안 스킬

Add team-specific evaluation criteria to plugin-eval by designing a metric pack, a set of custom checks and measurements. Create its manifest and JSON-producing script, then run it through the evaluator using a consistent output structure.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add team-specific evaluation criteria
• Define custom checks and numerical metrics
• Build a metric-pack manifest and script

Evaluate local Codex skills and plugins, understand their scores, and identify fixes to prioritize. Get explanations of token estimates, set up benchmark scenarios, and prepare workflows for measuring actual token usage.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Evaluate a local skill or plugin
• Understand scores and prioritize fixes
• Explain token estimates and prepare actual measurements

Evaluate a local Codex plugin to understand its scores and identify what to fix first. Review stronger and weaker skills, prepare benchmark runs, compare saved results across versions, and produce a readable report.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review an entire plugin before comparing versions
• Understand scores and prioritize fixes
• Compare strengths and weaknesses across included skills

Compares a prototype’s rendered screens with its source design to find differences in typography, spacing, colors, images, and text. Produces prioritized fixes and records visual evidence from follow-up checks before handoff.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check a prototype against its Figma source before handoff
• Compare an image-based build with the original visual
• Review visual differences across screen sizes and states

Test browser games through player actions and screenshot review. It checks startup, controls, scene changes, and interface visibility, then reports concrete issues with severity, reproduction steps, and the likely responsible subsystem.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check startup and core gameplay actions
• Review HUD visibility and playfield obstruction
• Test 3D camera and menu interactions

Trace a security finding from an attacker’s entry point to its impact using repository evidence. Examine access, permissions, existing defenses, and counterevidence to assess severity and decide whether the finding warrants reporting.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Trace how an attacker could exploit a finding
• Reassess severity against existing defenses
• Check counterevidence before reporting

Create, update, or reuse a repository threat model: a document describing system architecture, attacker capabilities, trust boundaries, and potential security failures. Produce a Markdown model grounded in source evidence for standalone use or a security scan.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating a threat model for a repository
• Updating a model after architecture changes
• Preparing a model for a security scan

Assess candidate security findings using focused reproduction, tests, or code tracing. Record the evidence, confidence, and remaining proof gaps for each candidate, helping determine which findings warrant reporting and which remain uncertain.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Verify whether a suspected vulnerability can be reproduced
• Reassess a finding previously marked as a false positive
• Trace vulnerable paths when runtime services are unavailable

Audit a repository or selected source paths for security issues in a single pass. Produce a report with source evidence, severity, possible attack paths, validation results, and an honest account of what was reviewed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Run a standard security audit across a repository
• Review one package or folder for security issues
• Audit source code against a supplied threat model

Develop security design improvements from vulnerability reports, incident documents, source code, or scan results. Compare architectural options with before-and-after diagrams, engineering tradeoffs, and migration plans to support a concrete design decision.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find structural causes shared by several vulnerabilities
• Compare security architecture options and costs
• Explain proposed changes with before-and-after diagrams

Review pull requests, commits, or local changes for security vulnerabilities, including deleted files. Validate potential issues, trace how attacks could reach them, and produce a report showing confirmed findings and gaps in review coverage.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Security review of a pull request
• Checking a commit or branch diff for vulnerabilities
• Reviewing local changes before committing

Assess a fixed code patch for behavior changes, regression risks, test coverage, and recovery options. Receive an evidence-based report and structured assessment indicating whether it is ready to merge and qualifies as an automatic merge candidate.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing the risks of an AI-generated patch
• Checking affected behavior before merging a pull request
• Assessing whether tests protect changed behavior

Design tests for charts, dashboards, and interactive diagrams. Combine data checks, component tests, screenshot comparisons, and end-to-end workflows to catch incorrect values, broken interactions, and visual changes while keeping tests stable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choose test coverage for a chart component
• Set up stable screenshot comparisons for a dashboard
• Verify mobile interactions and degraded network states

Examines code or code changes for plausible security vulnerabilities by tracing attacker-controlled input to dangerous operations or failed safeguards. Records candidate issues with affected locations, supporting evidence, potential impact, and controls that need further validation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Discover candidate vulnerabilities in code changes
• Trace input paths to authorization gaps or injection risks
• Investigate code locations linked to a security advisory

Verify whether a reported vulnerability is fixed in the current code without changing repository files. Trace the original attack path, examine possible bypasses and legitimate behavior, and return an evidence-based verdict for each supplied finding.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Verify remediation of a reported vulnerability
• Check for bypasses around a security fix
• Verify a fix after code moves or refactoring

Turn validated Codex Security findings into tracked issues in Linear, Jira, or GitHub, or draft GitHub security advisories. Checks duplicates and visibility, previews exact changes for approval, and verifies results after writing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create issues for validated security findings
• Check whether a finding is already tracked
• Register a reviewed batch of findings

Create or review SECURITY.md guidance so Codex Security understands what to examine, which protections must hold, and what is excluded. Compare existing policies with repository evidence and preview proposed changes before writing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Define security review scope for a repository
• Document required security protections
• Check whether existing guidance matches the code

Evaluate supplied security findings against repository code and security policy without running the software. Classify each claim as confirmed, not actionable, or needing review, then rank relevant findings by exploitability and explain evidence gaps and next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assess findings from a vulnerability scanner
• Review security tickets from Jira or Linear
• Evaluate GitHub alerts and security advisories

Turn vulnerability notes, proof-of-concept code, source code, or security findings into self-contained reports. The skill checks claims against evidence, explains prerequisites and demonstrated impact, and supports both individual vulnerabilities and collections of disclosure reports.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning vulnerability notes into a disclosure report
• Checking source code and proof-of-concept claims
• Preparing separate reports for multiple vulnerabilities

Audit page loading speed with Chrome DevTools MCP, a tool connection for browser inspection. Measure performance indicators, investigate network delays and layout shifts, check accessibility gaps, and produce prioritized fixes with estimated impact and relevant code findings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate slow page loads
• Find causes of layout shifts
• Identify improvements related to Lighthouse scores

Fix a validated or plausible security vulnerability with a focused code change, then verify that the attack no longer works and legitimate behavior remains intact. Report when existing code is safe or essential evidence is missing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fix a reported vulnerability and verify the result
• Check for alternate inputs that bypass a proposed fix
• Confirm that a security patch preserves legitimate behavior

Run repeated, independent security audits of a repository or selected directory with Codex Security. It combines validated findings into a report that records the reviewed scope, exclusions, and any incomplete coverage.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Run repeated security audits across a repository
• Audit a specific directory
• Combine validated findings from independent scans

Investigate failing macOS tests in Xcode or SwiftPM by running a focused test scope, classifying errors, and separating setup issues from code regressions. Get a concise explanation of likely causes and the next verification step.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Narrowing down failing macOS tests
• Distinguishing setup issues from code regressions
• Investigating assertions and crashes

Capture and analyze iOS memory snapshots to find objects that remain allocated unexpectedly. Trace the references keeping them alive, identify a targeted fix, and compare the same app flow before and after to document evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating memory growth in an iOS app
• Tracing retain cycles that keep objects alive
• Analyzing an existing .memgraph file