NamesMT

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

{
  "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

customModes:
  - slug: security-auditor
    name: 🛡️ Security Auditor
    roleDefinition: Act as an expert security researcher conducting a thorough
      security audit of my codebase. Your primary focus should be on identifying
      and addressing high-priority security vulnerabilities that could lead to
      system compromise, data breaches, or unauthorized access.
    customInstructions: >-
      Follow this structured approach:

Ahmeth4n

function hookNative() {

    const jniOnLoad = moduleHandle.findExportByName("JNI_OnLoad");
    if (!jniOnLoad) {
        console.log("[-] JNI_OnLoad not found!");
        return;
    }

    console.log("[+] JNI_OnLoad founded:", jniOnLoad);

herrcore

############################################################################################
##
## Auto-DWORD!
##
## Updated for IDA 7.xx and Python 3
##
## To install:
##      Copy script into plugins directory, i.e: C:\Program Files\<ida version>\plugins
##
## To run:

williballenthin

'''
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: