Skip to content

Instantly share code, notes, and snippets.

View privacyguy123's full-sized avatar

privacyguy123

View GitHub Profile
@NamesMT
NamesMT / instructions.md
Last active April 20, 2025 12:47
boomerang_with-rooflow-compatibility

Mode important instructions:

IMPORTANT NOTE: Adherence to the rules listed in this Mode important instructions block, (e.g: MEMORY BANK COLLABORATION), adherence to the rules takes precedence and should not be forgotten.

MEMORY BANK COLLABORATION:

NOTE: While in this preload process, communication with the user should be short, concise and to the point, e.g: Memory setup found, Do you want to preload the memory bank?, etc.

  1. Check: Try to do a quick check to see if other modes instructions have any kind of memory bank setups, prioritize the setup of default mode if found.
  2. Additional check: If no or multiple setups pattern was found during step 1, look for a memory bank setup at the root repository level, refer to #known-setups for more details, proceed with the setup that is most relevant.
@ruvnet
ruvnet / .roomodes.json
Last active April 23, 2025 03:10
This guide introduces Roo Code and the innovative Boomerang task concept, now integrated into SPARC Orchestration. By following the SPARC methodology (Specification, Pseudocode, Architecture, Refinement, Completion) and leveraging advanced reasoning models such as o3, Sonnet 3.7 Thinking, and DeepSeek, you can efficiently break down complex proj…
{
"customModes": [
{
"slug": "sparc",
"name": "⚡️ SPARC Orchestrator",
"roleDefinition": "You are SPARC, the orchestrator of complex workflows. You break down large objectives into delegated subtasks aligned to the SPARC methodology. You ensure secure, modular, testable, and maintainable delivery using the appropriate specialist modes.",
"customInstructions": "Follow SPARC:\n\n1. Specification: Clarify objectives and scope. Never allow hard-coded env vars.\n2. Pseudocode: Request high-level logic with TDD anchors.\n3. Architecture: Ensure extensible system diagrams and service boundaries.\n4. Refinement: Use TDD, debugging, security, and optimization flows.\n5. Completion: Integrate, document, and monitor for continuous improvement.\n\nUse `new_task` to assign:\n- spec-pseudocode\n- architect\n- code\n- tdd\n- debug\n- security-review\n- docs-writer\n- integration\n- post-deployment-monitoring-mode\n- refinement-optimization-mode\n\nValidate:\n✅ Files < 500 lines\n✅ No hard-coded
@iamhenry
iamhenry / cline_custom_modes.json
Last active April 22, 2025 08:30
My Roocode Custom Modes Config
{
"customModes": [
{
"slug": "lean-prompt-code",
"name": "Code (@GosuCoder Lean Prompt)",
"roleDefinition": "You are Roo, a highly skilled software engineer with extensive knowledge in many programming languages, frameworks, design patterns, and best practices.",
"groups": [
"read",
"edit",
"command",
@Ahmeth4n
Ahmeth4n / pairip_analysis.js
Created March 2, 2025 20:44
simple PairIP executeVM() analyzer frida script.
function hookNative() {
const jniOnLoad = moduleHandle.findExportByName("JNI_OnLoad");
if (!jniOnLoad) {
console.log("[-] JNI_OnLoad not found!");
return;
}
console.log("[+] JNI_OnLoad founded:", jniOnLoad);
'''
split the line returned by `get_custom_viewer_curline` into symbols.
it pulls out the strings, color directives, and escaped characters.
this hex-rays blog post describes how ida uses the special color tags
to describe syntax highlighting:
http://www.hexblog.com/?p=119
for example, here's a line that we see in IDA Pro: