research

research is a command for Claude Code from opensesh/KARIMO. It costs 0 tokens per session (4,120 once invoked), scanned C, original, Apache-2.0.

A research command in the KARIMO workflow that examines the codebase and related sources before planning a feature. It can start a new feature record or add and refine research for an existing product requirements document, or PRD.

In plain words
What is it for?
Use it to research a new feature, identify code patterns and gaps, recommend libraries, and record implementation guidance. Research can be limited to internal sources, external sources, or both.
Why use it?
It gives planning a researched starting point instead of relying on guesses about existing code, missing pieces, or suitable libraries. The required first step helps make later implementation work more grounded.

Command for Claude Code

Part of the karimo plugin — 11 commands, 22 agents shipped together

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 commands/opensesh/karimo/research
Clone the repo
git clone --depth 1 https://github.com/opensesh/KARIMO

Made for: Claude Code.

Or install karimo, the plugin that ships this one along with the rest of its 11 commands, 22 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for research

README.md
[![agentmods](https://agentmods.dev/badge/commands/opensesh/karimo/research.svg)](https://agentmods.dev/commands/opensesh/karimo/research)
Your own site
<a href="https://agentmods.dev/commands/opensesh/karimo/research"><img src="https://agentmods.dev/badge/commands/opensesh/karimo/research.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,120 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00000 $0.04120
Opus 5 $0.00000 $0.02060
Sonnet 5 $0.00000 $0.00824
Haiku 4.5 $0.00000 $0.00412

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

Security

Grade C, and why

research scanned grade C with 1 finding 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 3d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

3. Start fresh: rm -rf .karimo/prds/{slug} && /karimo:research "{slug}"
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • research — 100% identical, 38 lines differ
.claude/plugins/karimo/commands/research.md · 500 lines

How it starts

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

/karimo:research

KARIMO Research Command

Purpose

Conduct research to discover codebase patterns, identify gaps, recommend libraries, and provide implementation guidance. This is the REQUIRED first step before planning.

Three research modes:

  1. Feature Init/karimo:research "feature-name" creates PRD folder and runs initial research
  2. PRD-Scoped/karimo:research --prd {slug} adds research to existing PRD (iterate loop)
  3. Refinement/karimo:research --refine --prd {slug} processes annotations

Command Syntax

# Start new feature (REQUIRED first step)
# Creates PRD folder and runs research
/karimo:research "feature-name"

# Add research to existing PRD (iterate loop after planning)
/karimo:research --prd {slug}

# Refine research based on annotations
/karimo:research --refine --prd {slug}

# Research with constraints
/karimo:research "feature-name" --internal-only
/karimo:research "feature-name" --external-only
/karimo:research --prd {slug} --internal-only
/karimo:research --prd {slug} --external-only

Feature Init Mode (Default)

When invoked with a bare feature name (no --prd flag), this is the first step in the KARIMO workflow.

Workflow

  1. Sanitize Feature Name

    • Convert "My Feature Name" to my-feature-name (slug)
    • Validate slug format (lowercase, hyphens, no special chars)
  2. Create PRD Folder Structure

    • Create .karimo/prds/{slug}/ (no NNN prefix yet — plan adds it)
    • Create research subfolder structure:
      .karimo/prds/{slug}/
      ├── assets/                    # Flat folder for screenshots/mockups
      ├── research/
      │   ├── internal/
      │   │   ├── patterns.md        # Evidence
      │   │   ├── errors.md          # Evidence
      │   │   ├── dependencies.md    # Evidence
      │   │   ├── structure.md       # Evidence
      │   │   └── findings.md        # Consolidated output
      │   ├── external/
      │   │   ├── best-practices.md  # Evidence
      │   │   ├── libraries.md       # Evidence
      │   │   ├── references.md      # Evidence
      │   │   ├── sources.yaml       # Attribution
      │   │   └── findings.md        # Consolidated output
      │   ├── summary.md             # Combined executive summary
      │   └── meta.json              # Research metadata
      └── status.json                # Initial status
      

Read the full file on GitHub · 500 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. 3d ago First seen · 500 lines · 0 tokens per session scan C 9c5774e0c4a6

Subscribe to this mod's changes

research is a command published in the GitHub repository opensesh/KARIMO (283 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,120 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.