classical-cipher-analysis은(는) 무엇을 하나요?
고전 암호 분석 플레이북. CTF 챌린지에서 치환 암호, 비즈네르 암호, 전치 암호, XOR 또는 인코딩된 텍스트를 만나 빈도 분석, 키사키 검사 또는 기지 평문 암호 분석이 필요할 때 사용합니다.
고전 암호 분석 플레이북. CTF 챌린지에서 치환 암호, 비즈네르 암호, 전치 암호, XOR 또는 인코딩된 텍스트를 만나 빈도 분석, 키사키 검사 또는 기지 평문 암호 분석이 필요할 때 사용합니다.
이 스킬은 CTF(Capture The Flag) 챌린지에서 흔히 등장하는 고전 암호들을 분석하고 해독하기 위한 포괄적인 플레이북입니다. 주로 치환 암호(Substitution Cipher), 비즈네르 암호(Vigenere Cipher), 전치 암호(Transposition Cipher), XOR 암호화, 그리고 Base64나 Hex 등의 인코딩된 텍스트를 처리하는 데 사용됩니다. 해당 스킬은 빈도 분석(Frequency Analysis), 키사키 검사(Kasiski Examination), 기지 평문 공격(Known-Plaintext Attack)과 같은 고전적인 암호 해독 기법을 자동화하거나 단계별 가이드를 제공합니다. Yaklang이라는 스크립트 언어를 기반으로 동작하며, Yak 플랫폼(예: Yak Runner)에서 실행할 수 있습니다. 개발자나 보안 연구자에게는 수동 분석 시간을 크게 단축시켜 주며, 특히 CTF 환경에서 빠른 문제 해결을 돕습니다. 또한 각 암호 유형에 맞는 사전 훈련된 통계 모델이나 휴리스틱 알고리즘을 포함하여, 복잡한 암호라도 효율적인 분석 경로를 제시합니다.
npx skills add https://github.com/yaklang/hack-skills/tree/main/skills/classical-cipher-analysisInstalled? Explore more 연구 & 데이터 분석 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
고전 암호 분석 플레이북. CTF 챌린지에서 치환 암호, 비즈네르 암호, 전치 암호, XOR 또는 인코딩된 텍스트를 만나 빈도 분석, 키사키 검사 또는 기지 평문 암호 분석이 필요할 때 사용합니다.
This repo contains 20 individual skills — each has its own dedicated page.
401/403 bypass playbook. Use when encountering access-denied responses on admin panels, API endpoints, or restricted paths. Covers path manipulation, HTTP method tampering, header injection, protocol downgrade, and automated bypass tools.
Active Directory ACL abuse playbook. Use when exploiting misconfigured AD permissions including GenericAll, WriteDACL, DCSync rights, shadow credentials, LAPS reading, GPO abuse, and BloodHound-guided attack paths.
AD Certificate Services attack playbook. Use when targeting misconfigured AD CS for privilege escalation via ESC1-ESC13 template abuse, NTLM relay to enrollment, CA officer abuse, and certificate-based persistence.
Kerberos attack playbook for Active Directory. Use when targeting AD authentication via AS-REP roasting, Kerberoasting, golden/silver/diamond tickets, delegation abuse, or pass-the-ticket attacks.
AI/ML security playbook. Use when assessing model supply chain attacks (pickle RCE, poisoned weights), adversarial examples, model poisoning, model stealing, data privacy attacks (membership inference, model inversion), and autonomous agent security risks.
Android pentesting playbook. Use when testing Android applications for SSL pinning bypass, exported component abuse, WebView vulnerabilities, intent redirection, root detection bypass, tapjacking, and backup extraction during authorized mobile security assessments.
Anti-debugging detection and bypass playbook. Use when reversing protected binaries that detect debuggers via ptrace, PEB flags, timing checks, or signal/exception handlers on Linux and Windows.
API authentication and JWT abuse playbook. Use when testing bearer tokens, API keys, claim trust, header spoofing, rate limits, and API auth boundary weaknesses.
API authorization and BOLA testing playbook. Use when APIs expose object identifiers, nested resources, hidden writable fields, or weak function-level authorization.
API reconnaissance and documentation review playbook. Use when discovering endpoints, schemas, versions, OpenAPI specs, hidden docs, and surface area for API testing.
Entry P1 category router for API security. Use when choosing between API recon, authorization, token abuse, and hidden-parameter workflows before any deeper API topic skill.
Arbitrary write to RCE playbook. Use when you have an arbitrary write primitive (from heap exploitation, format string, or OOB write) and need to convert it into code execution by targeting GOT, hooks, _IO_FILE vtable, exit_funcs, TLS_dtor_list, modprobe_path, .fini_array, or C++ vtables.
Authentication bypass testing playbook. Use when assessing login flows, password reset logic, account recovery, MFA bypass, token predictability, brute-force resistance, and session boundary flaws.
Entry P1 category router for authentication and authorization. Use when testing login flows, sessions, object authorization, JWT, OAuth, CORS, CSRF, and enterprise SSO weaknesses before any deeper auth topic skill.
Binary protection bypass playbook. Use when identifying and bypassing ASLR, PIE, NX/DEP, stack canary, RELRO, FORTIFY_SOURCE, CET, and MTE protections in ELF binaries to enable exploitation.
Browser and V8 exploitation playbook. Use when exploiting JavaScript engine vulnerabilities including JIT type confusion, incorrect bounds elimination, and V8 sandbox bypass to achieve renderer RCE and sandbox escape in Chrome/Chromium.
Entry P1 category router for business logic testing. Use when workflow abuse, race conditions, pricing flaws, or multi-step state attacks matter more than parser-level input injection.
Business logic vulnerability playbook. Use when reasoning about workflows, race conditions, price manipulation, coupon abuse, state machines, and multi-step authorization gaps.
Clickjacking playbook. Use when testing whether target pages can be framed, whether X-Frame-Options or CSP frame-ancestors are properly configured, and whether UI redress attacks can trigger sensitive actions.
Command injection playbook. Use when user input may reach shell commands, process execution, converters, import pipelines, or blind out-of-band command sinks.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.