# How to Configure Global Injection for AI Clients (Claude Code, Cursor, Cline) in reverse-skill

> Learn to configure global injection for Claude Code, Cursor, and Cline AI clients in the reverse-skill repository. Master the RULES.md file for automatic MCP registration and tool index loading.

- Repository: [ZhaoXu/reverse-skill](https://github.com/zhaoxuya520/reverse-skill)
- Tags: how-to-guide
- Published: 2026-08-05

---

**The reverse-skill repository uses a single [`RULES.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/RULES.md) file containing a CRITICAL global-injection block that automatically configures Claude Code, Cursor, Cline, and other AI clients to register the MCP and load the tool index.**

The *reverse-skill* project implements a unified bootstrap architecture where all supported AI code assistants—**Claude Code**, **Code Cursor**, **Cline**, and others—receive identical global injection through a centralized configuration pipeline. This article explains the exact mechanism, file paths, and steps required to enable global injection for any AI client in your reverse-skill deployment.

## The Global Injection Architecture

The global injection system in *reverse-skill* operates as a **behavior chain** rather than scattered configuration files. Rather than manually editing each client's settings, you trigger a single CRITICAL block that propagates the necessary configuration across all supported platforms.

The chain follows this sequence:
1. [`README_AI.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/README_AI.md) → triggers section 0 execution
2. [`RULES.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/RULES.md) → contains the CRITICAL global-injection block
3. Client-specific rules files → auto-generated at known paths
4. MCP registration → enables tool invocation
5. Tool-index refresh → ensures routing validity

## Step 1: Trigger the Bootstrap via README_AI.md

AI agents begin by reading **[`README_AI.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/README_AI.md)** at the repository root. This file contains an explicit instruction on lines 5-7: **execute section 0 immediately**.

According to line 37 of [`README_AI.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/README_AI.md), this bootstrap directs the agent to load **[`RULES.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/RULES.md)** and locate the CRITICAL block. The file also mandates refreshing the local tool index before proceeding (lines 18-22).

```bash

# After cloning reverse-skill, ensure the AI reads this first

cat README_AI.md | head -20

```

## Step 2: Execute the CRITICAL Global-Injection Block in RULES.md

The core configuration lives in **[`RULES.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/RULES.md)**, specifically at excerpt line 369. This file contains steps 0-14 of the complete behavior chain, but the **global-injection block** (marked CRITICAL) is what prevents the AI from simply acknowledging the file and stopping.

At line 42, the CRITICAL block performs three essential operations:

| Operation | Purpose | Target |
|-----------|---------|--------|
| Create/append client rules file | Persists configuration across sessions | `~/.claude/CLAUDE.md`, `~/.cursor/CURSOR.md`, `~/.cline/CLINE.md` |
| Register MCP server | Enables real tool invocation | `~/.claude/mcp.json` and equivalents |
| Enforce execution | Prevents early termination | Conditional validation |

The pseudo-structure of this block (derived from the actual [`RULES.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/RULES.md) implementation) follows this pattern:

```yaml

# CRITICAL GLOBAL INJECTION — from RULES.md

- client: Claude Code
  config_path: "~/.claude/CLAUDE.md"
  action: create_or_append
  content: |
    # Auto-generated by reverse-skill

    READ RULES.md → EXECUTE CRITICAL BLOCK
    REFRESH TOOL INDEX → /skills/tool-index.md
    REGISTER MCP → ~/.claude/mcp.json

- mcp:
    name: local-mcp
    endpoint: "http://127.0.0.1:8000"
    register_for:
      - Claude Code
      - Cursor
      - Cline

- enforce:
    condition: "RULES.md read"
    then: "EXECUTE GLOBAL INJECTION"
    else: "ERROR – abort"

```

## Step 3: Configure Client-Specific Paths

The global-injection block auto-populates known configuration directories for each supported AI client. According to [`RULES_zh.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/RULES_zh.md) lines 42-44 and [`docs/PLATFORMS.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/docs/PLATFORMS.md) line 7, these paths are:

- **Claude Code**: `~/.claude/CLAUDE.md`
- **Cursor**: `~/.cursor/CURSOR.md`
- **Cline**: `~/.cline/CLINE.md`

After the injection runs, verify the files exist:

```bash

# Verify Claude Code configuration

ls -la ~/.claude/CLAUDE.md

# Check Cursor rules

cat ~/.cursor/CURSOR.md

# Confirm Cline setup

test -f ~/.cline/CLINE.md && echo "Cline configured"

```

## Step 4: Register the MCP Server

The global-injection step registers the **local MCP server**—the tool-orchestration layer that allows AI agents to call real security tools directly. This registration is documented in [`skills/js-reverse/SKILL.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/skills/js-reverse/SKILL.md) line 34 and [`skills/ida-reverse/SKILL.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/skills/ida-reverse/SKILL.md) line 339.

The MCP exposes capabilities including:
- Browser automation
- Frida dynamic instrumentation
- IDA Pro integration
- Burp Suite coordination

The registration creates or modifies the client-specific MCP configuration (e.g., `~/.claude/mcp.json`) with the local endpoint at `http://127.0.0.1:8000`.

## Step 5: Refresh the Tool Index

Before task routing can function, the client must execute the tool-index refresh script. As specified in [`README_AI.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/README_AI.md) lines 18-22, run:

```bash

# Navigate to reverse-skill root

cd /path/to/reverse-skill

# Execute the refresh script

./skills/scripts/refresh-tool-index.sh

# Verify output files exist

ls -la skills/tool-index.md skills/tool-index.json

```

This script populates [`tool-index.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/tool-index.md) and [`tool-index.json`](https://github.com/zhaoxuya520/reverse-skill/blob/main/tool-index.json), which the global-injection block expects to be present. Without these files, routing will fail.

## Step 6: Proceed to Task-Specific Routing

With global injection complete, the AI reads **[`SKILL.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/SKILL.md)** (the skill-specific entry point) and **[`skills/routing.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/skills/routing.md)** line 53 to select appropriate methodologies for reverse-engineering, penetration testing, or other security tasks.

This routing is referenced in [`README_AI.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/README_AI.md) line 81 as the final step of the initialization chain.

## Verification Checklist

Confirm global injection succeeded with this checklist:

- [ ] `~/.claude/CLAUDE.md` (or equivalent) contains auto-generated header
- [ ] MCP configuration file exists with `local-mcp` endpoint
- [ ] [`skills/tool-index.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/skills/tool-index.md) and [`tool-index.json`](https://github.com/zhaoxuya520/reverse-skill/blob/main/tool-index.json) are current
- [ ] [`RULES.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/RULES.md) CRITICAL block was executed (not just acknowledged)

## Summary

- **Single source of truth**: [`RULES.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/RULES.md) drives all global injection through its CRITICAL block
- **Auto-generation**: Client-specific files at `~/.claude/`, `~/.cursor/`, `~/.cline/` are created automatically
- **MCP registration**: Enables real tool invocation from any supported AI client
- **Tool-index dependency**: [`refresh-tool-index.sh`](https://github.com/zhaoxuya520/reverse-skill/blob/main/refresh-tool-index.sh) must run before routing functions
- **Execution enforcement**: The CRITICAL block prevents early termination with conditional validation

## Frequently Asked Questions

### What happens if the AI client stops after "understanding" RULES.md?

The CRITICAL block contains an **enforce** condition that triggers an error state if global injection is not executed. According to [`RULES.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/RULES.md) line 369 implementation, the AI must proceed through the entire behavior chain or explicitly abort. Simply acknowledging the file without executing the CRITICAL block violates the protocol.

### Can I manually configure global injection without using RULES.md?

Manual configuration is possible but not recommended. The paths `~/.claude/CLAUDE.md`, `~/.cursor/CURSOR.md`, and `~/.cline/CLINE.md` must contain specific routing instructions that reference [`RULES.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/RULES.md) and the MCP endpoint. Missing the conditional enforcement logic or incorrect tool-index paths will cause routing failures.

### Why does the MCP endpoint use 127.0.0.1:8000?

The local endpoint `http://127.0.0.1:8000` ensures tool execution remains on the host machine for security-sensitive reverse-engineering operations. As implemented in [`skills/pentest-tools/references/burpsuite-mcp-guide.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/skills/pentest-tools/references/burpsuite-mcp-guide.md), this keeps Frida, IDA, and browser automation on localhost rather than exposing capabilities externally.

### Which AI clients beyond Claude, Cursor, and Cline are supported?

The architecture supports any AI client that can read markdown files and execute shell commands. [`docs/PLATFORMS.md`](https://github.com/zhaoxuya520/reverse-skill/blob/main/docs/PLATFORMS.md) line 7 mentions Windsurf and Kiro as additional supported platforms. The global-injection block adapts to each client's configuration directory structure while maintaining identical behavior chain semantics.