setup

A setup guide for Claude RAG, a system that searches stored past conversations and tool results. It configures the connection between the plugin and its local or remote search service.

In plain words
What is it for?
Checking existing settings, choosing local Docker or cloud access, entering an endpoint and API key, saving configuration, and testing the connection.
Why use it?
It removes the manual work of finding configuration details, choosing a connection, and checking whether the search service is reachable.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/thisisyoyodev/claude-rag/setup
Any agent
npx skills add ThisisYoYoDev/claude-rag --skill setup
Clone the repo
git clone --depth 1 https://github.com/ThisisYoYoDev/claude-rag

Made for: Claude Code, Codex.

Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 988 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.00988
Opus 5 $0.00011 $0.00494
Sonnet 5 $0.00004 $0.00198
Haiku 4.5 $0.00002 $0.00099

Measured 2d ago against content hash 8d84cf99a7fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

setup scanned grade B with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat ~/.claude/plugins/claude-rag/config.json 2>/dev/null || echo "NO_CONFIG"

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s --max-time 3 https://api.clauderag.io/health
skills/setup/SKILL.md · 133 lines

How it starts

The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.

RAG Plugin Setup

Guide the user through first-time setup of the Claude RAG plugin.

Steps

Step 1: Check current config

cat ~/.claude/plugins/claude-rag/config.json 2>/dev/null || echo "NO_CONFIG"

If config exists, show current settings and ask if they want to reconfigure.

Step 2: Choose connection mode

Use AskUserQuestion:

  • header: "Claude RAG Setup"
  • question: "How do you want to connect to the RAG backend?"
  • options:
    • "Local (Docker — for development only)"
    • "Cloud (remote server)"

Step 3: Configure endpoint

If Local:

  • Check if Docker is running and the backend is accessible:
    curl -s --max-time 3 https://api.clauderag.io/health
    
  • If not accessible, tell the user:
    Start the backend with:
    cd <project-root> && docker compose -f docker/docker-compose.yml up -d
    Then: bun run backend/src/index.ts
    

If Cloud:

  • Use AskUserQuestion to get:
    • Endpoint URL
    • API key

Step 4: Write config

Create the config directory and file:

mkdir -p ~/.claude/plugins/claude-rag

Write ~/.claude/plugins/claude-rag/config.json with the chosen settings merged with defaults:

{
  "connection": {
    "endpoint": "<chosen_endpoint>",
    "apiKey": "<if_cloud>"
  },
  "capture": {
    "enabled": true,
    "userPrompts": true,
    "aiOutputs": true,
    "toolCalls": true,
    "toolResults": true,
    "subAgents": true,
    "multimodal": { "copyFiles": true, "maxFileSize": "50MB" },
    "exclude": { "tools": ["AskUserQuestion"], "pathPatterns": ["*.env", "*.secret", "*credentials*"] }
  },
  "rag": {
    "mode": "auto",
    "threshold": 0.6,
    "maxContextTokens": 5000,
    "perPrompt": { "enabled": true, "maxItems": 5, "maxLatencyMs": 500 },
    "sessionStart": { "enabled": true, "maxItems": 3 }
  },
  "privacy": {
    "redactSecrets": true,
    "excludePatterns": ["password", "token", "secret", "api_key", "private_key"]
  }
}

Step 5: Test the connection

curl -s <endpoint>/health

Read the full file on GitHub · 133 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 133 lines · 22 tokens per session scan B 8d84cf99a7fc

Subscribe to this mod's changes

setup is a skill published in the GitHub repository ThisisYoYoDev/claude-rag (9 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 988 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens