القائمة
Run a bounded, evidence-heavy cribdrag workflow for suspected keystream reuse and XOR-style leakage.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Enforce artifact-contract, presence, dependency, freshness, and cross-reference correctness for the artifact graph.
Reuse prior work only when hashes, dependencies, and artifact semantics still support it.
Normalize remote configuration and connection hints into machine-readable, ambiguity-aware remote artifacts.
Drive decode-first problems through explicit candidate generation, convergence tests, and branch stop conditions.
Map mixed decode-plus-crypto chains into explicit stages, transitions, and evidence-backed branch routes.
Build explicit vulnerability hypotheses with preconditions, discriminators, costs, scores, and attack-family context.
| name | crypto_cribdrag |
| description | Run a bounded, evidence-heavy cribdrag workflow for suspected keystream reuse and XOR-style leakage. |
| metadata | {"short-description":"Test repeated-keystream hypotheses with disciplined cribdrag artifacts"} |
This skill handles the very specific but common case where multiple ciphertexts appear to share a keystream or OTP segment. It should not be invoked as a generic “maybe XOR” reflex. It exists to transform that suspicion into structured evidence.
artifacts/out/validation/High-value crib sources include:
Low-value cribs include generic English words with weak structural constraints. Prefer cribs that also constrain alignment and character class plausibility.
Pass only if the skill leaves enough evidence to justify why repeated-keystream confidence increased, decreased, or stayed inconclusive.