「sec」の検索結果

Use when the user supplies or imports existing security findings, vulnerability reports, or security/vulnerability Jira/Linear tickets from scanners, advisories, GitHub, Atlassian Rovo, Linear, or similar backlog sources and wants static repo-impact triage. Do not use for discovery, duplicate-bug triage, validation, or fixes.

日本語の概要は準備中です。原文の説明を表示しています。

Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.

日本語の概要は準備中です。原文の説明を表示しています。

Use only when the user explicitly requests verification that a security fix remediates a reported vulnerability. Do not invoke automatically while implementing fixes, reviewing ordinary code changes, or running tests. Do not use for non-security fixes, candidate finding validation, or full repository scans.

日本語の概要は準備中です。原文の説明を表示しています。

Review a pull request, commit, branch diff, or working-tree patch for security vulnerabilities.

日本語の概要は準備中です。原文の説明を表示しています。

Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.

日本語の概要は準備中です。原文の説明を表示しています。

Track validated Codex Security findings in Linear, Jira, GitHub issues, or draft GitHub security advisories. Use it for one finding or an explicitly selected batch of up to 25 findings tracked as Linear, Jira, or GitHub issues. Includes duplicate checks, exact previews, approval-gated writes, and readback. Do not use it for scans or fixes.

日本語の概要は準備中です。原文の説明を表示しています。

Clone un site web à l'identique à partir d'une URL : capture Playwright complète (screens full-page + fold par fold sur desktop/tablet/mobile, crops par section, états hover), extraction de tout ce que le navigateur expose (fonts, variables CSS, palette, typo, layout, breakpoints, animations, assets, console/network), reconstruction section par section, puis boucle de vérification par diff pixel et console propre. Utilise ce skill DÈS QUE l'utilisateur veut copier, cloner, répliquer, reproduire, « refaire pareil », s'inspirer fortement d'un site, d'une landing page, d'un template ou d'une page précise (« fais-moi la même chose que X », « copie ce site », « reproduis cette landing », « clone neverboring.ai », « je veux exactement ce design »), même s'il ne dit pas « clone ». Aussi pour auditer visuellement un site existant (screens complets, design tokens, fonts utilisées).

日本語の概要は準備中です。原文の説明を表示しています。

Cross-validate code, architecture or design decisions using a second model. Use for critical decisions, complex refactoring, security reviews.

日本語の概要は準備中です。原文の説明を表示しています。

Structures secondary direct transactions with pricing methodology, transfer restriction analysis, and ROFR navigation. Use when modeling secondary purchases, pricing founder/employee shares, or structuring tender offers.

日本語の概要は準備中です。原文の説明を表示しています。

Identifies fulcrum securities in distressed capital structures with enterprise value allocation and recovery sensitivity analysis. Use when analyzing fulcrum securities, estimating recovery ranges, or determining value breaks.

日本語の概要は準備中です。原文の説明を表示しています。

Extract endpoints, secrets, and hidden routes from JavaScript files using LinkFinder, SecretFinder, JSluice, and source-map analysis. Use when the user has live hosts and needs to mine the JS for attack surface that's not visible in the UI.

日本語の概要は準備中です。原文の説明を表示しています。

Step 4 of the PaperOrchestra pipeline (arXiv:2604.05018). ONE single multimodal LLM call that drafts the remaining paper sections (Abstract, Methodology, Experiments, Conclusion), extracts numeric values from experimental_log.md into LaTeX booktabs tables, splices the generated figures from Step 2, and merges everything into the template that already contains Intro + Related Work from Step 3. TRIGGER when the orchestrator delegates Step 4 or when the user asks to "write the methodology and experiments sections" or "fill in the rest of the paper".

日本語の概要は準備中です。原文の説明を表示しています。

Detect hardcoded credentials, default passwords, fail-open configurations, insecure default settings, and other security misconfigurations that ship as default behavior in applications.

日本語の概要は準備中です。原文の説明を表示しています。

AI-powered code vulnerability analysis and dependency scanning using Gemini CLI security extension patterns. Detects hardcoded secrets, injection attacks, weak cryptography, authentication flaws, and LLM prompt injection. Also scans dependencies against the OSV.dev vulnerability database.

日本語の概要は準備中です。原文の説明を表示しています。

Smart contract and secure API contract security analysis — invariant checking, access control, reentrancy, and integer overflow patterns. Implements Checks-Effects-Interactions pattern, formal invariant verification, and OpenSCV vulnerability taxonomy for Solidity/EVM and Rust/Solana contracts.

日本語の概要は準備中です。原文の説明を表示しています。

OAuth 2.1, JWT (RFC 8725), encryption, and authentication security expert. Enforces 2026 security standards.

日本語の概要は準備中です。原文の説明を表示しています。

Produce a visible, evidence-backed privacy and security report for a local iOS app by scanning permission declarations, network code, dependencies, persistence, and risky APIs, while complementing the official Claude Code security-guidance plugin. Use after implementation, in a live security lane, or before claiming that an app is offline and account-free.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user needs to deploy, operate, secure, or scale running infrastructure — cloud architecture (multi-region, VPC, FinOps), CI/CD and deployment strategies, secrets/IAM/supply-chain security, observability and SLO alerting, SRE and incident response, Kubernetes vs ECS and autoscaling, Terraform/Pulumi/CDK, or platform engineering and DORA metrics. Also for generating runbooks, pipeline configs, Terraform modules, or Kubernetes manifests. For choosing the system's architecture or stack before it runs (monolith vs microservices, which database), use software-architect.

日本語の概要は準備中です。原文の説明を表示しています。

Maintain a changelog following Keep a Changelog format. Covers entry categorization (Added, Changed, Deprecated, Removed, Fixed, Security), version section management, and unreleased tracking. Use when starting a new project that needs a changelog, adding entries after completing features or fixes, preparing a release by promoting Unreleased entries to a versioned section, or converting a free-form changelog to Keep a Changelog format.

日本語の概要は準備中です。原文の説明を表示しています。

Configure Nginx as a web server and reverse proxy. Covers static file serving, reverse proxy to upstream services, SSL/TLS termination with Let's Encrypt, location blocks, load balancing, rate limiting, and security headers. Use when serving static files in production, reverse proxying to backend services (Node.js, Python, R/Shiny), terminating SSL/TLS, load balancing across instances, or adding rate limiting and security headers to harden an endpoint.

日本語の概要は準備中です。原文の説明を表示しています。

Use when examining ELF binaries with readelf, objdump, nm, or ldd: dependencies, symbols, sections, relocations, build IDs, or hardening, or when enabling RELRO, PIE, stack canaries, FORTIFY_SOURCE, CET, CFI, or seccomp filters, or checking a binary with checksec. Not for modifying binaries: use binutils. Not for runtime sanitizer builds: use sanitizers.

日本語の概要は準備中です。原文の説明を表示しています。

Connect to and query ClickHouse (a local server or a ClickHouse Cloud service) from the terminal. For ClickHouse Cloud analytics, use the configured direct ClickHouse Query API endpoint with per-user CH_API_KEY and CH_API_SECRET credentials; do not use clickhousectl cloud service query. For local or host/port servers, use clickhousectl local client. Use when the user wants to run SQL against ClickHouse, explore schemas and tables, inspect Cloud services, or authenticate. For building a local dev environment or deploying to Cloud, defer to the official ClickHouse skills (see Scope).

日本語の概要は準備中です。原文の説明を表示しています。

Audit and remediate NowStack Mobile security flaws. Use for auth/session abuse, Apple or Stripe payment bypass, Convex authorization, cross-user data leaks, unsafe deep links, R2 uploads, client secrets, SSRF, XSS, or pentest follow-up.

日本語の概要は準備中です。原文の説明を表示しています。

Generates structured cyber threat intelligence reports at strategic, operational, and tactical levels tailored to specific audiences including executives, security operations teams, and technical analysts. Use when producing finished intelligence products from raw collection data, creating sector threat briefings, or delivering post-incident intelligence assessments. Activates for requests involving CTI report writing, threat briefings, intelligence products, finished intelligence, or executive security reporting.

日本語の概要は準備中です。原文の説明を表示しています。