[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CG0EXNEJ40TD6JMBEHMVD":3,"skill-same:01M75CG0EXNEJ40TD6JMBEHMVD":84},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75CG0EXNEJ40TD6JMBEHMVD","constant-time-analysis",null,"Detects timing side-channel vulnerabilities in cryptographic code. Use when implementing or reviewing crypto code, encountering division on secrets, secret-dependent branches, or constant-time programming questions in C, C++, Go, Rust, Swift, Java, Kotlin, C#, PHP, JavaScript, TypeScript, Python, or Ruby.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconstant-time-analysis\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: constant-time-analysis\ndescription: Detects timing side-channel vulnerabilities in cryptographic code. Use when implementing or reviewing crypto code, encountering division on secrets, secret-dependent branches, or constant-time programming questions in C, C++, Go, Rust, Swift, Java, Kotlin, C#, PHP, JavaScript, TypeScript, Python, or Ruby.\n---\n\n# Constant-Time Analysis\n\nAnalyze cryptographic code to detect operations that leak secret data through execution timing variations.\n\n## When to Use\n\n```text\nUser writing crypto code? ──yes──> Use this skill\n         │\n         no\n         │\n         v\nUser asking about timing attacks? ──yes──> Use this skill\n         │\n         no\n         │\n         v\nCode handles secret keys\u002Ftokens? ──yes──> Use this skill\n         │\n         no\n         │\n         v\nSkip this skill\n```\n\n**Concrete triggers:**\n\n- User implements signature, encryption, or key derivation\n- Code contains `\u002F` or `%` operators on secret-derived values\n- User mentions \"constant-time\", \"timing attack\", \"side-channel\", \"KyberSlash\"\n- Reviewing functions named `sign`, `verify`, `encrypt`, `decrypt`, `derive_key`\n\n## When NOT to Use\n\n- Non-cryptographic code (business logic, UI, etc.)\n- Public data processing where timing leaks don't matter\n- Code that doesn't handle secrets, keys, or authentication tokens\n- High-level API usage where timing is handled by the library\n\n## Language Selection\n\nBased on the file extension or language context, refer to the appropriate guide:\n\n| Language   | File Extensions                   | Guide                                                    |\n| ---------- | --------------------------------- | -------------------------------------------------------- |\n| C, C++     | `.c`, `.h`, `.cpp`, `.cc`, `.hpp` | [references\u002Fcompiled.md](references\u002Fcompiled.md)         |\n| Go         | `.go`                             | [references\u002Fcompiled.md](references\u002Fcompiled.md)         |\n| Rust       | `.rs`                             | [references\u002Fcompiled.md](references\u002Fcompiled.md)         |\n| Swift      | `.swift`                          | [references\u002Fswift.md](references\u002Fswift.md)               |\n| Java       | `.java`                           | [references\u002Fvm-compiled.md](references\u002Fvm-compiled.md)   |\n| Kotlin     | `.kt`, `.kts`                     | [references\u002Fkotlin.md](references\u002Fkotlin.md)             |\n| C#         | `.cs`                             | [references\u002Fvm-compiled.md](references\u002Fvm-compiled.md)   |\n| PHP        | `.php`                            | [references\u002Fphp.md](references\u002Fphp.md)                   |\n| JavaScript | `.js`, `.mjs`, `.cjs`             | [references\u002Fjavascript.md](references\u002Fjavascript.md)     |\n| TypeScript | `.ts`, `.tsx`                     | [references\u002Fjavascript.md](references\u002Fjavascript.md)     |\n| Python     | `.py`                             | [references\u002Fpython.md](references\u002Fpython.md)             |\n| Ruby       | `.rb`                             | [references\u002Fruby.md](references\u002Fruby.md)                 |\n\n## Quick Start\n\n```bash\n# Analyze any supported file type\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py \u003Csource_file>\n\n# Include conditional branch warnings\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --warnings \u003Csource_file>\n\n# Filter to specific functions\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --func 'sign|verify' \u003Csource_file>\n\n# JSON output for CI\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --json \u003Csource_file>\n```\n\n### Native Compiled Languages Only (C, C++, Go, Rust)\n\n```bash\n# Cross-architecture testing (RECOMMENDED)\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --arch x86_64 crypto.c\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --arch arm64 crypto.c\n\n# Multiple optimization levels\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --opt-level O0 crypto.c\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --opt-level O3 crypto.c\n```\n\n### VM-Compiled Languages (Java, Kotlin, C#)\n\n```bash\n# Analyze Java bytecode\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py CryptoUtils.java\n\n# Analyze Kotlin bytecode (Android\u002FJVM)\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py CryptoUtils.kt\n\n# Analyze C# IL\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py CryptoUtils.cs\n```\n\nNote: Java, Kotlin, and C# compile to bytecode (JVM\u002FCIL) that runs on a virtual machine with JIT compilation. The analyzer examines the bytecode directly, not the JIT-compiled native code. The `--arch` and `--opt-level` flags do not apply to these languages.\n\n### Swift (iOS\u002FmacOS)\n\n```bash\n# Analyze Swift for native architecture\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py crypto.swift\n\n# Analyze for specific architecture (iOS devices)\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --arch arm64 crypto.swift\n\n# Analyze with different optimization levels\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --opt-level O0 crypto.swift\n```\n\nNote: Swift compiles to native code like C\u002FC++\u002FGo\u002FRust, so it uses assembly-level analysis and supports `--arch` and `--opt-level` flags.\n\n### Prerequisites\n\n| Language               | Requirements                                              |\n| ---------------------- | --------------------------------------------------------- |\n| C, C++, Go, Rust       | Compiler in PATH (`gcc`\u002F`clang`, `go`, `rustc`)           |\n| Swift                  | Xcode or Swift toolchain (`swiftc` in PATH)               |\n| Java                   | JDK with `javac` and `javap` in PATH                      |\n| Kotlin                 | Kotlin compiler (`kotlinc`) + JDK (`javap`) in PATH       |\n| C#                     | .NET SDK + `ilspycmd` (`dotnet tool install -g ilspycmd`) |\n| PHP                    | PHP with VLD extension or OPcache                         |\n| JavaScript\u002FTypeScript  | Node.js in PATH                                           |\n| Python                 | Python 3.x in PATH                                        |\n| Ruby                   | Ruby with `--dump=insns` support                          |\n\n**macOS users**: Homebrew installs Java and .NET as \"keg-only\". You must add them to your PATH:\n\n```bash\n# For Java (add to ~\u002F.zshrc)\nexport PATH=\"\u002Fopt\u002Fhomebrew\u002Fopt\u002Fopenjdk@21\u002Fbin:$PATH\"\n\n# For .NET tools (add to ~\u002F.zshrc)\nexport PATH=\"$HOME\u002F.dotnet\u002Ftools:$PATH\"\n```\n\nSee [references\u002Fvm-compiled.md](references\u002Fvm-compiled.md) for detailed setup instructions and troubleshooting.\n\n## Quick Reference\n\n| Problem                | Detection                       | Fix                                          |\n| ---------------------- | ------------------------------- | -------------------------------------------- |\n| Division on secrets    | DIV, IDIV, SDIV, UDIV           | Barrett reduction or multiply-by-inverse     |\n| Branch on secrets      | JE, JNE, BEQ, BNE               | Constant-time selection (cmov, bit masking)  |\n| Secret comparison      | Early-exit memcmp               | Use `crypto\u002Fsubtle` or constant-time compare |\n| Weak RNG               | rand(), mt_rand, Math.random    | Use crypto-secure RNG                        |\n| Table lookup by secret | Array subscript on secret index | Bit-sliced lookups                           |\n\n## Interpreting Results\n\n**PASSED** - No variable-time operations detected.\n\n**FAILED** - Dangerous instructions found. Example:\n\n```text\n[ERROR] SDIV\n  Function: decompose_vulnerable\n  Reason: SDIV has early termination optimization; execution time depends on operand values\n```\n\n## Verifying Results (Avoiding False Positives)\n\n**CRITICAL**: Not every flagged operation is a vulnerability. The tool has no data flow analysis - it flags ALL potentially dangerous operations regardless of whether they involve secrets.\n\nFor each flagged violation, ask: **Does this operation's input depend on secret data?**\n\n1. **Identify the secret inputs** to the function (private keys, plaintext, signatures, tokens)\n\n2. **Trace data flow** from the flagged instruction back to inputs\n\n3. **Common false positive patterns**:\n\n   ```c\n   \u002F\u002F FALSE POSITIVE: Division uses public constant, not secret\n   int num_blocks = data_len \u002F 16;  \u002F\u002F data_len is length, not content\n\n   \u002F\u002F TRUE POSITIVE: Division involves secret-derived value\n   int32_t q = secret_coef \u002F GAMMA2;  \u002F\u002F secret_coef from private key\n   ```\n\n4. **Document your analysis** for each flagged item\n\n### Quick Triage Questions\n\n| Question                                          | If Yes                | If No                 |\n| ------------------------------------------------- | --------------------- | --------------------- |\n| Is the operand a compile-time constant?           | Likely false positive | Continue              |\n| Is the operand a public parameter (length, count)?| Likely false positive | Continue              |\n| Is the operand derived from key\u002Fplaintext\u002Fsecret? | **TRUE POSITIVE**     | Likely false positive |\n| Can an attacker influence the operand value?      | **TRUE POSITIVE**     | Likely false positive |\n\n## Limitations\n\n1. **Static Analysis Only**: Analyzes assembly\u002Fbytecode, not runtime behavior. Cannot detect cache timing or microarchitectural side-channels.\n\n2. **No Data Flow Analysis**: Flags all dangerous operations regardless of whether they process secrets. Manual review required.\n\n3. **Compiler\u002FRuntime Variations**: Different compilers, optimization levels, and runtime versions may produce different output.\n\n## Real-World Impact\n\n- **KyberSlash (2023)**: Division instructions in post-quantum ML-KEM implementations allowed key recovery\n- **Lucky Thirteen (2013)**: Timing differences in CBC padding validation enabled plaintext recovery\n- **RSA Timing Attacks**: Early implementations leaked private key bits through division timing\n\n## References\n\n- [Cryptocoding Guidelines](https:\u002F\u002Fgithub.com\u002Fveorq\u002Fcryptocoding) - Defensive coding for crypto\n- [KyberSlash](https:\u002F\u002Fkyberslash.cr.yp.to\u002F) - Division timing in post-quantum crypto\n- [BearSSL Constant-Time](https:\u002F\u002Fwww.bearssl.org\u002Fconstanttime.html) - Practical constant-time techniques\n","# Constant-Time Analysis\n\nAnalyze cryptographic code to detect operations that leak secret data through execution timing variations.\n\n## When to Use\n\n```text\nUser writing crypto code? ──yes──> Use this skill\n         │\n         no\n         │\n         v\nUser asking about timing attacks? ──yes──> Use this skill\n         │\n         no\n         │\n         v\nCode handles secret keys\u002Ftokens? ──yes──> Use this skill\n         │\n         no\n         │\n         v\nSkip this skill\n```\n\n**Concrete triggers:**\n\n- User implements signature, encryption, or key derivation\n- Code contains `\u002F` or `%` operators on secret-derived values\n- User mentions \"constant-time\", \"timing attack\", \"side-channel\", \"KyberSlash\"\n- Reviewing functions named `sign`, `verify`, `encrypt`, `decrypt`, `derive_key`\n\n## When NOT to Use\n\n- Non-cryptographic code (business logic, UI, etc.)\n- Public data processing where timing leaks don't matter\n- Code that doesn't handle secrets, keys, or authentication tokens\n- High-level API usage where timing is handled by the library\n\n## Language Selection\n\nBased on the file extension or language context, refer to the appropriate guide:\n\n| Language   | File Extensions                   | Guide                                                    |\n| ---------- | --------------------------------- | -------------------------------------------------------- |\n| C, C++     | `.c`, `.h`, `.cpp`, `.cc`, `.hpp` | [references\u002Fcompiled.md](references\u002Fcompiled.md)         |\n| Go         | `.go`                             | [references\u002Fcompiled.md](references\u002Fcompiled.md)         |\n| Rust       | `.rs`                             | [references\u002Fcompiled.md](references\u002Fcompiled.md)         |\n| Swift      | `.swift`                          | [references\u002Fswift.md](references\u002Fswift.md)               |\n| Java       | `.java`                           | [references\u002Fvm-compiled.md](references\u002Fvm-compiled.md)   |\n| Kotlin     | `.kt`, `.kts`                     | [references\u002Fkotlin.md](references\u002Fkotlin.md)             |\n| C#         | `.cs`                             | [references\u002Fvm-compiled.md](references\u002Fvm-compiled.md)   |\n| PHP        | `.php`                            | [references\u002Fphp.md](references\u002Fphp.md)                   |\n| JavaScript | `.js`, `.mjs`, `.cjs`             | [references\u002Fjavascript.md](references\u002Fjavascript.md)     |\n| TypeScript | `.ts`, `.tsx`                     | [references\u002Fjavascript.md](references\u002Fjavascript.md)     |\n| Python     | `.py`                             | [references\u002Fpython.md](references\u002Fpython.md)             |\n| Ruby       | `.rb`                             | [references\u002Fruby.md](references\u002Fruby.md)                 |\n\n## Quick Start\n\n```bash\n# Analyze any supported file type\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py \u003Csource_file>\n\n# Include conditional branch warnings\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --warnings \u003Csource_file>\n\n# Filter to specific functions\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --func 'sign|verify' \u003Csource_file>\n\n# JSON output for CI\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --json \u003Csource_file>\n```\n\n### Native Compiled Languages Only (C, C++, Go, Rust)\n\n```bash\n# Cross-architecture testing (RECOMMENDED)\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --arch x86_64 crypto.c\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --arch arm64 crypto.c\n\n# Multiple optimization levels\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --opt-level O0 crypto.c\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --opt-level O3 crypto.c\n```\n\n### VM-Compiled Languages (Java, Kotlin, C#)\n\n```bash\n# Analyze Java bytecode\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py CryptoUtils.java\n\n# Analyze Kotlin bytecode (Android\u002FJVM)\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py CryptoUtils.kt\n\n# Analyze C# IL\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py CryptoUtils.cs\n```\n\nNote: Java, Kotlin, and C# compile to bytecode (JVM\u002FCIL) that runs on a virtual machine with JIT compilation. The analyzer examines the bytecode directly, not the JIT-compiled native code. The `--arch` and `--opt-level` flags do not apply to these languages.\n\n### Swift (iOS\u002FmacOS)\n\n```bash\n# Analyze Swift for native architecture\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py crypto.swift\n\n# Analyze for specific architecture (iOS devices)\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --arch arm64 crypto.swift\n\n# Analyze with different optimization levels\nuv run {baseDir}\u002Fct_analyzer\u002Fanalyzer.py --opt-level O0 crypto.swift\n```\n\nNote: Swift compiles to native code like C\u002FC++\u002FGo\u002FRust, so it uses assembly-level analysis and supports `--arch` and `--opt-level` flags.\n\n### Prerequisites\n\n| Language               | Requirements                                              |\n| ---------------------- | --------------------------------------------------------- |\n| C, C++, Go, Rust       | Compiler in PATH (`gcc`\u002F`clang`, `go`, `rustc`)           |\n| Swift                  | Xcode or Swift toolchain (`swiftc` in PATH)               |\n| Java                   | JDK with `javac` and `javap` in PATH                      |\n| Kotlin                 | Kotlin compiler (`kotlinc`) + JDK (`javap`) in PATH       |\n| C#                     | .NET SDK + `ilspycmd` (`dotnet tool install -g ilspycmd`) |\n| PHP                    | PHP with VLD extension or OPcache                         |\n| JavaScript\u002FTypeScript  | Node.js in PATH                                           |\n| Python                 | Python 3.x in PATH                                        |\n| Ruby                   | Ruby with `--dump=insns` support                          |\n\n**macOS users**: Homebrew installs Java and .NET as \"keg-only\". You must add them to your PATH:\n\n```bash\n# For Java (add to ~\u002F.zshrc)\nexport PATH=\"\u002Fopt\u002Fhomebrew\u002Fopt\u002Fopenjdk@21\u002Fbin:$PATH\"\n\n# For .NET tools (add to ~\u002F.zshrc)\nexport PATH=\"$HOME\u002F.dotnet\u002Ftools:$PATH\"\n```\n\nSee [references\u002Fvm-compiled.md](references\u002Fvm-compiled.md) for detailed setup instructions and troubleshooting.\n\n## Quick Reference\n\n| Problem                | Detection                       | Fix                                          |\n| ---------------------- | ------------------------------- | -------------------------------------------- |\n| Division on secrets    | DIV, IDIV, SDIV, UDIV           | Barrett reduction or multiply-by-inverse     |\n| Branch on secrets      | JE, JNE, BEQ, BNE               | Constant-time selection (cmov, bit masking)  |\n| Secret comparison      | Early-exit memcmp               | Use `crypto\u002Fsubtle` or constant-time compare |\n| Weak RNG               | rand(), mt_rand, Math.random    | Use crypto-secure RNG                        |\n| Table lookup by secret | Array subscript on secret index | Bit-sliced lookups                           |\n\n## Interpreting Results\n\n**PASSED** - No variable-time operations detected.\n\n**FAILED** - Dangerous instructions found. Example:\n\n```text\n[ERROR] SDIV\n  Function: decompose_vulnerable\n  Reason: SDIV has early termination optimization; execution time depends on operand values\n```\n\n## Verifying Results (Avoiding False Positives)\n\n**CRITICAL**: Not every flagged operation is a vulnerability. The tool has no data flow analysis - it flags ALL potentially dangerous operations regardless of whether they involve secrets.\n\nFor each flagged violation, ask: **Does this operation's input depend on secret data?**\n\n1. **Identify the secret inputs** to the function (private keys, plaintext, signatures, tokens)\n\n2. **Trace data flow** from the flagged instruction back to inputs\n\n3. **Common false positive patterns**:\n\n   ```c\n   \u002F\u002F FALSE POSITIVE: Division uses public constant, not secret\n   int num_blocks = data_len \u002F 16;  \u002F\u002F data_len is length, not content\n\n   \u002F\u002F TRUE POSITIVE: Division involves secret-derived value\n   int32_t q = secret_coef \u002F GAMMA2;  \u002F\u002F secret_coef from private key\n   ```\n\n4. **Document your analysis** for each flagged item\n\n### Quick Triage Questions\n\n| Question                                          | If Yes                | If No                 |\n| ------------------------------------------------- | --------------------- | --------------------- |\n| Is the operand a compile-time constant?           | Likely false positive | Continue              |\n| Is the operand a public parameter (length, count)?| Likely false positive | Continue              |\n| Is the operand derived from key\u002Fplaintext\u002Fsecret? | **TRUE POSITIVE**     | Likely false positive |\n| Can an attacker influence the operand value?      | **TRUE POSITIVE**     | Likely false positive |\n\n## Limitations\n\n1. **Static Analysis Only**: Analyzes assembly\u002Fbytecode, not runtime behavior. Cannot detect cache timing or microarchitectural side-channels.\n\n2. **No Data Flow Analysis**: Flags all dangerous operations regardless of whether they process secrets. Manual review required.\n\n3. **Compiler\u002FRuntime Variations**: Different compilers, optimization levels, and runtime versions may produce different output.\n\n## Real-World Impact\n\n- **KyberSlash (2023)**: Division instructions in post-quantum ML-KEM implementations allowed key recovery\n- **Lucky Thirteen (2013)**: Timing differences in CBC padding validation enabled plaintext recovery\n- **RSA Timing Attacks**: Early implementations leaked private key bits through division timing\n\n## References\n\n- [Cryptocoding Guidelines](https:\u002F\u002Fgithub.com\u002Fveorq\u002Fcryptocoding) - Defensive coding for crypto\n- [KyberSlash](https:\u002F\u002Fkyberslash.cr.yp.to\u002F) - Division timing in post-quantum crypto\n- [BearSSL Constant-Time](https:\u002F\u002Fwww.bearssl.org\u002Fconstanttime.html) - Practical constant-time techniques\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fconstant-time-analysis",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill constant-time-analysis",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill constant-time-analysis",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill constant-time-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconstant-time-analysis\u002FSKILL.md",true,[46,52,56,60,64,68,72,76,80],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"README.md","REFERENCE","参考文档",3893,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconstant-time-analysis\u002FREADME.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcompiled.md",4108,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconstant-time-analysis\u002Freferences\u002Fcompiled.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fjavascript.md",4449,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconstant-time-analysis\u002Freferences\u002Fjavascript.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fkotlin.md",6784,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconstant-time-analysis\u002Freferences\u002Fkotlin.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fphp.md",4831,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconstant-time-analysis\u002Freferences\u002Fphp.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fpython.md",5261,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconstant-time-analysis\u002Freferences\u002Fpython.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fruby.md",5391,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconstant-time-analysis\u002Freferences\u002Fruby.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fswift.md",8194,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconstant-time-analysis\u002Freferences\u002Fswift.md",{"path":81,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fvm-compiled.md",10409,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconstant-time-analysis\u002Freferences\u002Fvm-compiled.md",[85,92,99,108,115,122],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":103,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]