Agent skill

Cross Plugin Detective

by MadAppGang in MadAppGang/claude-code

A skill your agent uses when integrating detective skills across plugins.

MITAuto-check: notesAgent Workflows

Install Cross Plugin Detective

skills CLI
$ npx skills add MadAppGang/claude-code --skill cross-plugin-detective -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install MadAppGang/claude-code cross-plugin-detective --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/MadAppGang/claude-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/code-analysis/skills/cross-plugin-detective .claude/skills/cross-plugin-detective && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cross-plugin-detective
GitHub stars
285
Token cost
~2.4k tokens
SKILL.md length
273 words
Files
1
Skills in repo
69
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when integrating detective skills across plugins.

  • Works in 4 steps: Reference the appropriate detective… → Follow the skill's INDEXED MEMORY ONLY… → Use claudemem for ALL code discovery → …
  • Integrating detective skills across plugins
  • SKILL.md covers ⛔ CORE PRINCIPLE: INDEXED…, Agent-to-Skill Mapping, How to Reference Skills in… and Skill Selection Decision Tree, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Cross Plugin Detective is an agent skill from MadAppGang/claude-code. Use when integrating detective skills across plugins. Maps agent roles to appropriate detective skills (developer → developer-detective, architect → architect-detective). Reference this to connect agents with claudemem investigation capabilities.

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Multi-agent orchestration. The repository describes itself as: claude code plugins marketplace. The licence is MIT.

When your agent uses it

  • Integrating detective skills across plugins
  • Tasks that involve Multi-agent orchestration

Example prompts

  • “/cross-plugin-detective”

Requirements

  • Pre-approved tools (allowed-tools): Bash, Task, Read, AskUserQuestion

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Reference the appropriate detective skill in frontmatter
  2. Follow the skill's INDEXED MEMORY ONLY requirement
  3. Use claudemem for ALL code discovery
  4. NEVER fall back to grep/find/Glob/Grep tools

What it can do on your machine

Read from SKILL.md and the folder at commit 6097ad4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Task
    • Read
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml, typescript and json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cross Plugin Detective loads about 2.4k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 273 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Task, Read, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from MadAppGang/claude-code at commit 6097ad4, republished under its MIT licence (© MadAppGang). 273 words, ~2,392 tokens.

Download SKILL.mdSave it as .claude/skills/cross-plugin-detective/SKILL.md (or your agent's skills folder).
name
cross-plugin-detective
description
Use when integrating detective skills across plugins. Maps agent roles to appropriate detective skills (developer → developer-detective, architect → architect-detective). Reference this to connect agents with claudemem investigation capabilities.
allowed-tools
Bash, Task, Read, AskUserQuestion
updated
2026-01-20
keywords
cross-plugin, detective, agent-mapping, claudemem, integration

Cross-Plugin Detective Integration

Version: 1.0.0 Purpose: Connect ANY agent to the appropriate detective skill based on role

⛔ CORE PRINCIPLE: INDEXED MEMORY ONLY

╔══════════════════════════════════════════════════════════════════════════════╗
║                                                                              ║
║   ALL DETECTIVE SKILLS USE claudemem (INDEXED MEMORY) EXCLUSIVELY            ║
║                                                                              ║
║   When ANY agent references a detective skill, they MUST:                    ║
║   ❌ NEVER use grep, find, rg, Glob tool, Grep tool                         ║
║   ✅ ALWAYS use claudemem search "query"                                    ║
║                                                                              ║
╚══════════════════════════════════════════════════════════════════════════════╝

Agent-to-Skill Mapping

Frontend Plugin Agents
AgentShould Use SkillPurpose
typescript-frontend-devcode-analysis:developer-detectiveFind implementations, trace data flow
frontend-architectcode-analysis:architect-detectiveAnalyze architecture, design patterns
test-architectcode-analysis:tester-detectiveCoverage analysis, test quality
senior-code-reviewercode-analysis:ultrathink-detectiveComprehensive code review
ui-developercode-analysis:developer-detectiveFind UI implementations
designercode-analysis:architect-detectiveUnderstand component structure
plan-reviewercode-analysis:architect-detectiveReview architecture plans
Bun Backend Plugin Agents
AgentShould Use SkillPurpose
backend-developercode-analysis:developer-detectiveFind implementations, trace data flow
api-architectcode-analysis:architect-detectiveAPI architecture analysis
apidogcode-analysis:developer-detectiveFind API implementations
Code Analysis Plugin Agents
AgentShould Use SkillPurpose
codebase-detectiveAll detective skillsFull investigation capability
Any Other Plugin
Agent RoleShould Use Skill
Any "developer" agentcode-analysis:developer-detective
Any "architect" agentcode-analysis:architect-detective
Any "tester" agentcode-analysis:tester-detective
Any "reviewer" agentcode-analysis:ultrathink-detective
Any "debugger" agentcode-analysis:debugger-detective

How to Reference Skills in Agent Frontmatter

Example: Developer Agent
yaml
---
name: my-developer-agent
description: Implements features
skills: code-analysis:developer-detective
---

# My Developer Agent

When investigating code, use the developer-detective skill.
This gives you access to indexed memory search via claudemem.

## Investigation Pattern

Before implementing:
1. Check claudemem status: `claudemem status`
2. Search for related code: `claudemem search "feature I'm implementing"`
3. Read specific files from results
4. NEVER use grep or find for discovery
Example: Architect Agent
yaml
---
name: my-architect-agent
description: Designs architecture
skills: code-analysis:architect-detective
---

# My Architect Agent

When analyzing architecture, use the architect-detective skill.

## Architecture Discovery

1. Check claudemem status: `claudemem status`
2. Search for patterns: `claudemem search "service layer architecture"`
3. Map dependencies: `claudemem search "import dependency injection"`
4. NEVER use grep or find for discovery
Example: Multi-Skill Agent
yaml
---
name: comprehensive-reviewer
description: Reviews all aspects
skills: code-analysis:ultrathink-detective, code-analysis:tester-detective
---

Skill Selection Decision Tree

┌─────────────────────────────────────────────────────────────────────────────┐
│                     WHICH DETECTIVE SKILL TO USE?                           │
├─────────────────────────────────────────────────────────────────────────────┤
│                                                                             │
│  What is the agent's PRIMARY focus?                                         │
│                                                                             │
│  ├── IMPLEMENTING code / Finding where to change                            │
│  │   └── Use: developer-detective                                           │
│  │                                                                          │
│  ├── DESIGNING architecture / Understanding patterns                        │
│  │   └── Use: architect-detective                                           │
│  │                                                                          │
│  ├── TESTING / Coverage analysis / Quality                                  │
│  │   └── Use: tester-detective                                              │
│  │                                                                          │
│  ├── DEBUGGING / Finding root cause                                         │
│  │   └── Use: debugger-detective                                            │
│  │                                                                          │
│  └── COMPREHENSIVE analysis / Technical debt / Audit                        │
│      └── Use: ultrathink-detective                                          │
│                                                                             │
└─────────────────────────────────────────────────────────────────────────────┘

Integration Examples

Example 1: Frontend Developer Agent Needing to Find Code
typescript
// In frontend plugin's typescript-frontend-dev agent:

// ❌ WRONG - Never do this
Grep({ pattern: "UserService", type: "ts" });
Glob({ pattern: "**/user*.ts" });

// ✅ CORRECT - Use indexed memory via developer-detective skill
// The skill teaches the agent to use:
claudemem search "UserService implementation methods"
Example 2: Backend Architect Analyzing API Structure
typescript
// In bun plugin's api-architect agent:

// ❌ WRONG - Never do this
find . -name "*.controller.ts"
grep -r "router\." . --include="*.ts"

// ✅ CORRECT - Use indexed memory via architect-detective skill
claudemem search "API controller endpoint handler"
claudemem search "router pattern REST GraphQL"
Example 3: Test Architect Finding Coverage Gaps
typescript
// In frontend plugin's test-architect agent:

// ❌ WRONG - Never do this
Glob({ pattern: "**/*.test.ts" });
Grep({ pattern: "describe" });

// ✅ CORRECT - Use indexed memory via tester-detective skill
claudemem search "test coverage describe spec"
claudemem search "mock stub test assertion"

Skill Inheritance Pattern

When an agent needs code investigation, it should:

  1. Reference the appropriate detective skill in frontmatter
  2. Follow the skill's INDEXED MEMORY ONLY requirement
  3. Use claudemem for ALL code discovery
  4. NEVER fall back to grep/find/Glob/Grep tools
yaml
---
name: any-agent-that-needs-investigation
skills: code-analysis:developer-detective  # or architect/tester/debugger/ultrathink
---

# This agent inherits:
# - INDEXED MEMORY requirement (claudemem only)
# - Role-specific search patterns
# - Output format guidance
# - FORBIDDEN: grep, find, Glob, Grep tools

Plugin Dependencies

If your plugin has agents that need code investigation, add this dependency:

json
{
  "name": "your-plugin",
  "dependencies": {
    "code-analysis@mag-claude-plugins": "^1.6.0"
  }
}

This ensures:

  • claudemem skills are available
  • Detective skills are accessible via code-analysis:* prefix
  • Agents can reference skills in frontmatter

Summary: The Golden Rule

╔══════════════════════════════════════════════════════════════════════════════╗
║                                                                              ║
║   ANY AGENT + CODE INVESTIGATION = claudemem ONLY                            ║
║                                                                              ║
║   Developer agents → code-analysis:developer-detective                       ║
║   Architect agents → code-analysis:architect-detective                       ║
║   Tester agents    → code-analysis:tester-detective                          ║
║   Debugger agents  → code-analysis:debugger-detective                        ║
║   Reviewer agents  → code-analysis:ultrathink-detective                      ║
║                                                                              ║
║   grep/find/Glob/Grep = FORBIDDEN (always, everywhere, no exceptions)        ║
║                                                                              ║
╚══════════════════════════════════════════════════════════════════════════════╝

Maintained by: MadAppGang Plugin: code-analysis Last Updated: December 2025

© MadAppGang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/code-analysis/skills/cross-plugin-detective of MadAppGang/claude-code.

Open the folder on GitHubat commit 6097ad4

Compare with similar skills

Cross Plugin Detective next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cross Plugin Detective compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cross Plugin Detective this skillMadAppGang/claude-code285—~2.4kAutomated safety check: NotesMIT
Orca CLIstablyai/orca89k2 repos~593Automated safety check: PassMIT
Paseo Advisor Second Opiniongetpaseo/paseo20k1 repos~756Automated safety check: PassCustom licence
O2 Review Loopopenobserve/openobserve22k—~3.7kAutomated safety check: PassAGPL-3.0
Paseo Committeegetpaseo/paseo20k1 repos~496Automated safety check: PassCustom licence
Mission Control Agent APIbuilderz-labs/mission-control6.3k—~2.1kAutomated safety check: PassMIT

Similar skills

  • Orca CLI

    stablyai/orca

    Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…

    89k GitHub starsUsed in 2 repos~593 tokens
    Agent WorkflowsAuto-check passed
  • Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.

    20k GitHub starsUsed in 1 repo~756 tokens
    Agent WorkflowsAuto-check passed
  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Paseo Committee

    getpaseo/paseo

    Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.

    20k GitHub starsUsed in 1 repo~496 tokens
    Agent WorkflowsAuto-check passed
  • Mission Control Agent API

    builderz-labs/mission-control

    Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth.

    6.3k GitHub stars~2.1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Paseo Agent Handoff

    getpaseo/paseo

    Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.

    20k GitHub starsUsed in 1 repo~606 tokens
    Agent WorkflowsAuto-check passed

More from MadAppGang/claude-code

All 69 skills in this repo
  • Content Brief

    MadAppGang/claude-code

    Content brief template and creation methodology for SEO-optimized content.

    285 GitHub starsUsed in 1 repo~959 tokens
    Auto-check passed
  • Context Detection

    MadAppGang/claude-code

    A skill your agent uses when detecting project technology stack from files/configs/directory structure, auto-loading framework-specific skills, or analyzing multi-stack fullstack projects (e.g…

    285 GitHub stars~5.4k tokensUpdated 6 mo ago
    Auto-check passed
  • Content Optimizer

    MadAppGang/claude-code

    On-page SEO optimization techniques including keyword density, meta tags, heading structure, and readability.

    285 GitHub starsUsed in 1 repo~694 tokens
    Auto-check passed
  • Keyword Cluster Builder

    MadAppGang/claude-code

    Techniques for expanding seed keywords and clustering by topic and intent.

    285 GitHub starsUsed in 1 repo~674 tokens
    Auto-check passed
  • Serp Analysis

    MadAppGang/claude-code

    SERP analysis techniques for intent classification, feature identification, and competitive intelligence.

    285 GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed
  • Agent Coordination Discipline

    MadAppGang/claude-code

    A skill your agent uses when deciding whether to launch an agent, selecting which agent to use, or coordinating multiple agents.

    285 GitHub stars~3.8k tokensUpdated 6 mo ago
    Auto-check passed

Categories

Questions about Cross Plugin Detective

What does Cross Plugin Detective do?

A skill your agent uses when integrating detective skills across plugins. Cross Plugin Detective is an agent skill from MadAppGang/claude-code. Use when integrating detective skills across plugins.

When should I use Cross Plugin Detective?

Cross Plugin Detective fits situations like: integrating detective skills across plugins; tasks that involve Multi-agent orchestration.

How do I install Cross Plugin Detective in Claude Code?

Run `npx skills add MadAppGang/claude-code --skill cross-plugin-detective -a claude-code`. Or copy the skill folder (plugins/code-analysis/skills/cross-plugin-detective in MadAppGang/claude-code) into .claude/skills/cross-plugin-detective in your project. Claude Code loads it when a task matches its description.

How do I install Cross Plugin Detective in Codex?

Run `npx skills add MadAppGang/claude-code --skill cross-plugin-detective -a codex`. Or copy the skill folder (plugins/code-analysis/skills/cross-plugin-detective in MadAppGang/claude-code) into .agents/skills/cross-plugin-detective in your project. Codex loads it when a task matches its description.

Can I use Cross Plugin Detective in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MadAppGang/claude-code --skill cross-plugin-detective -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cross-plugin-detective, .gemini/skills/cross-plugin-detective, .github/skills/cross-plugin-detective and .opencode/skills/cross-plugin-detective in your project.

What does Cross Plugin Detective need to run?

SKILL.md names no scripts, command-line tools or credentials: Cross Plugin Detective is instructions for the agent only. Its frontmatter pre-approves these tools: Bash, Task, Read, AskUserQuestion.

Does Cross Plugin Detective access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cross Plugin Detective safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Cross Plugin Detective use?

Cross Plugin Detective is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cross Plugin Detective use?

About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cross Plugin Detective?

Skills that share tags, products or a category with Cross Plugin Detective: Orca CLI (stablyai/orca, 89k stars), Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars), O2 Review Loop (openobserve/openobserve, 22k stars) and Paseo Committee (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cross Plugin Detective?

MadAppGang (a GitHub organization) maintains it in MadAppGang/claude-code, which has 285 GitHub stars. The repository holds 69 skills in this directory. The repository was last updated on March 15, 2026.

Source: MadAppGang/claude-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.