원클릭으로 Manus에서 모든 스킬 실행

fix

스타0

포크0

업데이트2026년 5월 30일 23:51

Generate and PoC⁺-validate a patch for each confirmed/proven finding. The fixer agent writes a minimal defensive unified diff plus functional and semantic checks; the host applies it to a SANDBOX COPY, re-runs the existing PoC harness, the functional check, and the semantic oracle check for supported CWEs. A patch is "validated" only if all required gates pass. The working tree is never touched until you explicitly approve the apply step. Requires confirmed/proven findings (run /verify and /poc first).

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

allsmog

allsmog/kuzushi-security-plugin

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Patch generation + PoC⁺ validation

Turn the repo's confirmed/proven findings into validated fixes. Requires findings at confirmed/proven in .kuzushi/findings.json — run /verify (and /poc for empirical harnesses) first.

PoC⁺ moat: a patch is validated only when it stops the existing PoC harness, passes a functional/regression check, and passes the semantic oracle check for supported CWEs. Validation runs against a sandbox copy — your working tree is never modified until you explicitly approve the apply step.

Run node "${CLAUDE_PLUGIN_ROOT}/scripts/cmd/fix-prepare.mjs" --target "<repo root>" (optionally --input '{"maxCandidates":8}'). If there are no fixable findings, tell the user to run /verify and /poc first, and stop. Read the prep's prepPath.
For each candidate, root-cause the bug and write a minimal defensive unified diff + a functionalCheck, using each candidate's findingFingerprint verbatim. If the candidate has semanticOracle, also write a runnable semanticCheck that exercises its positive/negative controls; supported CWE fixes are not validated without that semantic check. Set harnessLinkage honestly. Write the { candidates: [...] } bundle to the prep's draftPath. Write only under the run dir — never edit application code here.
Run the assembleCommand (finalize). It applies each diff to a sandbox copy, re-runs the PoC (expecting NO crash), re-attacks the patch (re-runs the fuzz harness with the variant corpus you seeded, and replays every other finding's PoC that lives in the same function — any reproduced crash ⇒ exploit-still-fires, no status advance), runs the functional check, runs the semantic check for supported CWEs, and assigns the patch verdict. The re-attack executes code in the sandbox; add --trust-local only if the user consents to a local (non-Docker) run. Report the verdict per finding.
Apply step (explicit approval, one finding at a time). For each validated finding, ask the user with AskUserQuestion whether to apply it to the working tree ("Apply patch" / "Skip"). On approval, run exactly node "${CLAUDE_PLUGIN_ROOT}/scripts/cmd/fix-apply.mjs" --target "<root>" --fingerprint "<fp>" — the user will see a permission prompt; that is the consent gate. On success, report the applied files and the rollback command (git apply -R …). Never apply a verdict other than validated (the script refuses anyway).

When NOT to use

Before findings are confirmed/proven — run /verify and /poc first.
When you can't accept code execution — validation builds/runs harnesses in a sandbox.
To auto-fix en masse — each apply is individually approved.

Rationalizations to Reject

"The original PoC stops, so the patch is good." → That is one shape through one caller. Seed the variant corpus and let the re-attack (variants + same-function sibling replay) try to break it before you trust the validated verdict.
"A non-validated verdict is close enough to apply." → Only validated advances to patched, and fix-apply refuses anything else. Re-root-cause instead of forcing the apply.
"Skip the sandbox, the diff obviously holds." → The sanitizer/exit-signal in the sandbox is the verdict, not your reading of the diff. No run ⇒ no validated.

이 저장소의 다른 Skills

같은 저장소

deep-hunt

allsmog/kuzushi-security-plugin

Interprocedural, hypothesis-driven hunt — finds the multi-file source→sink bugs that pattern-gating and same-file taint miss. Ranks trace anchors (entry points + dangerous sinks), then the deep-hunter agent walks each flow ACROSS files (forward/backward call-graph CLIs) over multiple rounds, confirming propagation and defeating guards, and promotes confirmed cross-file flows into findings.json with the path stored as evidenceGraph. Token-expensive, budget-bounded. Part of the HUNT phase (run via /sweep --deep, or ask for it); leads flow to /verify (panel).

2026-06-110

deep-scan

allsmog/kuzushi-security-plugin

Whole-file deep reader — finds bugs by READING risk-ranked files in full and reasoning from first principles, not by grepping for known patterns. Catches the long tail (project-specific wrappers, business logic, cross-function flaws) that pattern-gated producers structurally miss. Token-expensive; budget-bounded and risk-ranked. Promotes leads into .kuzushi/findings.json (source "deep-scan").

2026-06-110

taint-analysis

allsmog/kuzushi-security-plugin

IRIS-style source→sink taint hunt. Ranks a typed CWE catalog for the repo, then drives subagents to label dangerous sinks, label sources of user input, run Joern/CodeQL dataflow queries (or same-file linking) to connect them, and triage each flow as finding/candidate/rejected. Promotes verdicts into .kuzushi/findings.json. Benefits from a prebuilt CodeQL DB / Joern CPG but degrades gracefully.

2026-06-110

threat-hunt

allsmog/kuzushi-security-plugin

Adversarial per-threat review (Carlini doctrine). For each threat in .kuzushi/threat-model.json, state attacker capabilities, walk source→sink, attempt to bypass every guard, and assign a verdict with evidence. Promotes findings into .kuzushi/findings.json. Requires /threat-model first.

2026-06-110

partition

allsmog/kuzushi-security-plugin

Split the attack surface into parallel-discovery partitions so fan-out hunters explore different subsystems instead of converging on the same shallow bug. Deterministic grouping of /x-ray entry points by component → .kuzushi/partitions.json, which a hunt coordinator hands to one subagent per partition. Run /x-ray first.

2026-06-100

poc

allsmog/kuzushi-security-plugin

Empirical proof-of-concept for the PoC-ready findings. For each finding /verify marked confirmed-exploitable or inconclusive, synthesize a minimal harness that triggers the bug; a host script then runs it in a sandbox (Docker --network none when present, else a gated local run) and classifies the crash into a proof verdict. Attaches a poc block onto each finding. Requires /verify first.

2026-06-100

name	fix
description	Generate and PoC⁺-validate a patch for each confirmed/proven finding. The fixer agent writes a minimal defensive unified diff plus functional and semantic checks; the host applies it to a SANDBOX COPY, re-runs the existing PoC harness, the functional check, and the semantic oracle check for supported CWEs. A patch is "validated" only if all required gates pass. The working tree is never touched until you explicitly approve the apply step. Requires confirmed/proven findings (run /verify and /poc first).
context	fork
agent	fixer
user-invocable	true

Patch generation + PoC⁺ validation

Turn the repo's confirmed/proven findings into validated fixes. Requires findings at confirmed/proven in .kuzushi/findings.json — run /verify (and /poc for empirical harnesses) first.

Run node "${CLAUDE_PLUGIN_ROOT}/scripts/cmd/fix-prepare.mjs" --target "<repo root>" (optionally --input '{"maxCandidates":8}'). If there are no fixable findings, tell the user to run /verify and /poc first, and stop. Read the prep's prepPath.
For each candidate, root-cause the bug and write a minimal defensive unified diff + a functionalCheck, using each candidate's findingFingerprint verbatim. If the candidate has semanticOracle, also write a runnable semanticCheck that exercises its positive/negative controls; supported CWE fixes are not validated without that semantic check. Set harnessLinkage honestly. Write the { candidates: [...] } bundle to the prep's draftPath. Write only under the run dir — never edit application code here.
Run the assembleCommand (finalize). It applies each diff to a sandbox copy, re-runs the PoC (expecting NO crash), re-attacks the patch (re-runs the fuzz harness with the variant corpus you seeded, and replays every other finding's PoC that lives in the same function — any reproduced crash ⇒ exploit-still-fires, no status advance), runs the functional check, runs the semantic check for supported CWEs, and assigns the patch verdict. The re-attack executes code in the sandbox; add --trust-local only if the user consents to a local (non-Docker) run. Report the verdict per finding.
Apply step (explicit approval, one finding at a time). For each validated finding, ask the user with AskUserQuestion whether to apply it to the working tree ("Apply patch" / "Skip"). On approval, run exactly node "${CLAUDE_PLUGIN_ROOT}/scripts/cmd/fix-apply.mjs" --target "<root>" --fingerprint "<fp>" — the user will see a permission prompt; that is the consent gate. On success, report the applied files and the rollback command (git apply -R …). Never apply a verdict other than validated (the script refuses anyway).

When NOT to use

Before findings are confirmed/proven — run /verify and /poc first.
When you can't accept code execution — validation builds/runs harnesses in a sandbox.
To auto-fix en masse — each apply is individually approved.

Rationalizations to Reject

"The original PoC stops, so the patch is good." → That is one shape through one caller. Seed the variant corpus and let the re-attack (variants + same-function sibling replay) try to break it before you trust the validated verdict.
"A non-validated verdict is close enough to apply." → Only validated advances to patched, and fix-apply refuses anything else. Re-root-cause instead of forcing the apply.
"Skip the sandbox, the diff obviously holds." → The sanitizer/exit-signal in the sandbox is the verdict, not your reading of the diff. No run ⇒ no validated.