Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

crypto-review

Estrellas0

Forks0

Actualizado29 de mayo de 2026 a las 02:51

Crypto-misuse review — non-constant-time comparison of secrets (timing side-channels), missing/compiler-elidable zeroization of secrets, and non-cryptographic RNG used to mint secrets. The crypto-reviewer agent confirms each candidate handles a secret and promotes real issues into .kuzushi/findings.json (source "crypto-review"). Distinct from /sast (injection) and /sharp-edges (API design).

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

allsmog

allsmog/kuzushi-security-plugin

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de seguridad de la informaciónOcupaciones informáticas y matemáticas·SOC 15-1212

SKILL.md

readonly

name	crypto-review
description	Crypto-misuse review — non-constant-time comparison of secrets (timing side-channels), missing/compiler-elidable zeroization of secrets, and non-cryptographic RNG used to mint secrets. The crypto-reviewer agent confirms each candidate handles a secret and promotes real issues into .kuzushi/findings.json (source "crypto-review"). Distinct from /sast (injection) and /sharp-edges (API design).
context	fork
agent	crypto-reviewer
user-invocable	false

Crypto review

Find the crypto-implementation footguns that look fine but leak or weaken secrets.

Run node "${CLAUDE_PLUGIN_ROOT}/scripts/cmd/crypto-review-prepare.mjs" --target "<repo root>" (optionally --input '{"maxCandidates":30}'). If it reports no-candidates, say so and stop. Read the prep's prepPath.
For each candidate, open the site and first confirm the value is secret-derived, then assess by category: timing-side-channel (variable-time compare of a secret), missing-zeroization (secret not securely wiped / elidable memset), or weak-crypto-rng (non-CSPRNG minting a token/key/nonce). Decide finding / candidate / rejected.
Write the { candidates: [...] } bundle to the prep's draftPath, then run the assembleCommand — it validates verdicts/categories and promotes them into .kuzushi/findings.json (source:"crypto-review").
Report findings by category (file:line, the leak/weakness, and the constant-time / secure-zero / CSPRNG fix to use).

When NOT to use

On code with no cryptographic / secret handling — nothing to review.
For injection or API-design misuse — that's /sast, /taint-analysis, and /sharp-edges.

Rationalizations to Reject

"Just a string compare." → If a side is a secret (MAC/token/hash), a variable-time compare leaks it; confirm secret-derivation before clearing.
"memset wipes it." → A plain memset on a dying buffer is often optimized away; only a secure-zero primitive counts.
"The RNG is random enough." → Math.random/rand() are predictable; for secrets that's a finding.

Más de este repositorio

mismo repositorio

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	crypto-review
description	Crypto-misuse review — non-constant-time comparison of secrets (timing side-channels), missing/compiler-elidable zeroization of secrets, and non-cryptographic RNG used to mint secrets. The crypto-reviewer agent confirms each candidate handles a secret and promotes real issues into .kuzushi/findings.json (source "crypto-review"). Distinct from /sast (injection) and /sharp-edges (API design).
context	fork
agent	crypto-reviewer
user-invocable	false

Crypto review

Find the crypto-implementation footguns that look fine but leak or weaken secrets.

Run node "${CLAUDE_PLUGIN_ROOT}/scripts/cmd/crypto-review-prepare.mjs" --target "<repo root>" (optionally --input '{"maxCandidates":30}'). If it reports no-candidates, say so and stop. Read the prep's prepPath.
For each candidate, open the site and first confirm the value is secret-derived, then assess by category: timing-side-channel (variable-time compare of a secret), missing-zeroization (secret not securely wiped / elidable memset), or weak-crypto-rng (non-CSPRNG minting a token/key/nonce). Decide finding / candidate / rejected.
Write the { candidates: [...] } bundle to the prep's draftPath, then run the assembleCommand — it validates verdicts/categories and promotes them into .kuzushi/findings.json (source:"crypto-review").
Report findings by category (file:line, the leak/weakness, and the constant-time / secure-zero / CSPRNG fix to use).

When NOT to use

On code with no cryptographic / secret handling — nothing to review.
For injection or API-design misuse — that's /sast, /taint-analysis, and /sharp-edges.

Rationalizations to Reject

"Just a string compare." → If a side is a secret (MAC/token/hash), a variable-time compare leaks it; confirm secret-derivation before clearing.
"memset wipes it." → A plain memset on a dying buffer is often optimized away; only a secure-zero primitive counts.
"The RNG is random enough." → Math.random/rand() are predictable; for secrets that's a finding.