This document lists the colors used in the Monokai Pro theme with the Classic filter. Please check theMonokai Pro website for more informations.

Monokai Pro with Classic filter colors:

	Preview	Hexadecimal	RGB
Activity Bar Background		#272822	(39, 40, 34)
Activity Bar Foreground		#f8f8f2	(248, 248, 242)

How to use this script:

1. Accept a quest under Discover -> Quests
2. PressCtrl+Shift+I to open DevTools
3. Go to theConsole tab
4. Paste the following code and hit enter:

• CARTA HOLDINGS（旧VOYAGE GROUP）
  • 技術広報が新卒研修<Open AIハッカソン>をスパイしてみた - (2023/04/11)
  • @t_wadaに学ぶテスト駆動開発【CARTA 23新卒研修】 - (2023/04/19)
  • 【新卒研修】監修者@t_wadaと読む！プログラマが知るべき97のこと読書会 - (2024/04/09)
• Classi
  • 当たり前にリリースしていく ~ 新卒研修編 - (2021/05/20)
  • リモートワークのための質問力向上研修を実施しました - (2021/12/07)
  • Classi 2025年新卒エンジニア研修「そーだい塾」を開催しました - (2025/06/18)
• CyberZ

As a security professional, it is important to conduct a thorough reconnaissance. With the increasing use of APIs nowadays, it has become paramount to keep access tokens and other API-related secrets secure in order to prevent leaks. However, despite technological advances, human error remains a factor, and many developers still unknowingly hardcode their API secrets into source code and commit them to public repositories. GitHub, being a widely popular platform for public code repositories, may inadvertently host such leaked secrets. To help identify these vulnerabilities, I have created a comprehensive search list using powerful search syntax that enables the search of thousands of leaked keys and secrets in a single search.

(path:*.{File_extension1} OR path:*.{File_extension-N}) AND ({Keyname1} OR {Keyname-N}) AND (({Signature/pattern1} OR {Signature/pattern-N}) AND ({PlatformTag1} OR {PlatformTag-N}))

**1.

• Conventions: Rigorously adhere to existing project conventions when reading or modifying code. Analyze surrounding code, tests, and configuration first.
• Libraries/Frameworks: NEVER assume a library/framework is available or appropriate. Verify its established usage within the project (check imports, configuration files like 'package.json', 'Cargo.toml', 'requirements.txt', 'build.gradle', etc., or observe neighboring files) before employing it.
• Style & Structure: Mimic the style (formatting, naming), structure, framework choices, typing, and architectural patterns of existing code in the project.
• Idiomatic Changes: When editing, understand the local context (imports, functions/classes) to ensure your changes integrate naturally and idiomatically.
• **