「exe」の検索結果

Fallback to shell execution when sandbox fails for library-dependent Python code

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

Generate structured PDF documents with tables, sections, and scoring using Python libraries in execute_code_sandbox

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

Fallback pattern for PDF/document generation when execute_code_sandbox fails with opaque errors

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

Reliable PDF generation using shell-based Python execution when sandbox fails

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

Use run_shell with inline Python as a fallback when execute_code_sandbox fails for openpyxl/spreadsheet operations

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

Progressive tool-chain PDF extraction with explicit read_file, run_shell, and execute_code_sandbox sequencing

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

PDF extraction with ordered tool chain: read_file, then run_shell/pdftotext, then execute_code_sandbox/PyMuPDF

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

Fallback pattern for reliable file creation when code execution tools fail

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

Use shell_agent as fallback when execute_code_sandbox fails for Excel file operations

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

Use run_shell with Python heredoc when execute_code_sandbox or read_file fail

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

Identify and classify agent failures occurring before execution starts

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

Document generation with direct pandoc/ReportLab execution (lightweight default) and optional shell_agent fallback for complex scenarios

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

Use run_shell as fallback when execute_code_sandbox or shell_agent fail on filesystem operations

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

Identify and handle pre-execution agent failures occurring before any iterations or tool usage

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

Create Excel files with openpyxl by falling back to run_shell with inline Python heredoc when execute_code_sandbox fails

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

Create Excel files with openpyxl by falling back to shell-based Python heredoc when sandbox execution fails

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

Mutation-driven test vector generation. Finds implementations of a cryptographic algorithm or protocol, runs mutation testing to identify escaped mutants, then generates new test vectors that deliberately exercise the uncovered code paths. Compares before/after mutation kill rates to prove vector effectiveness. Use when generating cryptographic test vectors, measuring Wycheproof coverage gaps, finding escaped mutants via mutation testing, creating cross-implementation test suites, or improving test vector coverage for crypto primitives.

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

Sets up and runs cargo-fuzz, the standard fuzzing tool for Cargo-based Rust projects. Covers cargo fuzz init, the nightly toolchain requirement, fuzz_target! harnesses, Arbitrary-derived structured inputs, sanitizer options, cargo fuzz coverage, and reproducing a crash artifact. Use when fuzzing a Rust crate, writing a fuzz_target!, exercising unsafe blocks or FFI in Rust, or triaging a cargo fuzz crash.

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

Builds custom fuzzers with LibAFL, the modular Rust fuzzing library. Covers composing observers, feedbacks, mutators, schedulers, and executors into a fuzzer for targets the standard tools do not fit. Use when writing a bespoke fuzzer or mutator, fuzzing a non-standard target or architecture, implementing a fuzzing research idea, or when libFuzzer and AFL++ lack the control you need.

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

Audits a project's dependencies for supply-chain risk: version-matched advisories for direct dependencies and the full lockfile tree, abandoned or archived upstreams, npm publisher concentration, and install-time script execution. Use when asked to audit dependencies, assess supply-chain or third-party package risk, or review a dependency tree before an engagement.

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

Incident response workup for a lead in hand — an alert, an IOC, or a /dnr-hunt finding. Scopes the lead across the logs, verdicts whether the attack succeeded, quantifies blast radius, confirms root cause in source with a local PoC, and writes a proposed (never executed) containment/remediation/recovery plan. Use when asked to "respond to this alert", "work this incident", "how bad is this", or "run dnr-respond". /dnr-hunt is the no-alert entry to the same track.

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

Static source-code vulnerability scan. Reads a target directory (and THREAT_MODEL.md if present), spawns parallel review subagents per focus area, and writes VULN-FINDINGS.json + .md for /triage to consume. Read-only — no building, running, or network. For execution-verified crashes, use vuln-pipeline instead. Use when asked to "scan for vulns", "review this code for security issues", "find bugs in <dir>", or as the step between /threat-model and /triage.

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

Generate candidate fixes for verified security findings. Consumes TRIAGE.json (preferred), VULN-FINDINGS.json, INCIDENTS.json, or a vuln-pipeline results directory. Pipeline input is delegated to the execution-verified `vuln-pipeline patch` ladder; static-analysis input gets a per-finding patch subagent + independent reviewer and is written as inert diffs for human review. Writes PATCHES/bug_NN/{patch.diff,patch_result.json}, PATCHES.md, and PATCHES.json. Use when asked to "fix the findings", "patch these vulns", "generate fixes", or "close the loop on triage".

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

Dense methodology covering DNS exfiltration (dnscat2, iodine, dns2tcp), HTTPS tunneling (domain fronting, CDN abuse, legitimate service channels), ICMP tunneling (icmpsh, ptunnel-ng), cloud storage dead drops (S3 presigned URLs, Azure Blob SAS tokens, GCS signed URLs), email-based exfil (SMTP, EWS, draft method), steganography (image, audio, document metadata), encoding/encryption (base64 chunking, XOR, AES), covert channels (custom protocol tunneling, HTTP header encoding, timing channels), and data staging (compression, splitting, encryption). Tools: dnscat2, iodine, dns2tcp, PacketWhisper, chisel, stunnel, icmpsh, ptunnel-ng, steghide, zsteg, OpenStego. MITRE ATT&CK: T1048 (Exfiltration Over Alternative Protocol), T1041 (Exfiltration Over C2 Channel), T1567 (Exfiltration Over Web Service), T1029 (Scheduled Transfer), T1030 (Data Transfer Size Limits), T1132 (Data Encoding), T1001 (Data Obfuscation). Use when planning or executing data exfiltration during authorized red team engagements or post-exploitation.

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