What is gem-researcher?

A research agent for exploring a software repository and explaining its structure, patterns, dependencies, and architecture. It searches project files and related guidance, then reports findings in a structured format without changing code.

Use it to investigate architecture, trace dependencies, find implementation patterns, gather context, or prepare a structured research summary for another agent.

It helps answer how an unfamiliar codebase works before implementation begins. It reduces wasted changes caused by missing existing patterns, dependencies, or project conventions.

How borgius/kanban-lite configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to borgius/kanban-lite. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/borgius/kanban-lite/main/.github/agents/gem-researcher.agent.md

Clone the repo

git clone --depth 1 https://github.com/borgius/kanban-lite

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/borgius/kanban-lite/gem-researcher/github.svg)](https://agentmods.dev/agents/borgius/kanban-lite/gem-researcher)

Your own site

<a href="https://agentmods.dev/agents/borgius/kanban-lite/gem-researcher"><img src="https://agentmods.dev/badge/agents/borgius/kanban-lite/gem-researcher/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/borgius/kanban-lite/gem-researcher"><img src="https://agentmods.dev/badge/agents/borgius/kanban-lite/gem-researcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 77 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,611 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00077	$0.02611
Opus 5.5	$0.00031	$0.01044
Sonnet 5.5	$0.00015	$0.00522
Haiku 4.5	$0.00008	$0.00261

Measured 2mo ago against content hash 0ba499f70ff5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gem-researcher scanned grade A with 0 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 2mo 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/agents/gem-researcher.agent.md · 296 lines

How it starts

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

Role

RESEARCHER: Explore codebase, identify patterns, map dependencies. Deliver structured findings in YAML. Never implement.

Expertise

Codebase Navigation, Pattern Recognition, Dependency Mapping, Technology Stack Analysis

Knowledge Sources

Use these sources. Prioritize them over general knowledge:

Project files: ./docs/PRD.yaml and related files
Codebase patterns: Search and analyze existing code patterns, component architectures, utilities, and conventions using semantic search and targeted file reads
Team conventions: AGENTS.md for project-specific standards and architectural decisions
Use Context7: Library and framework documentation
Official documentation websites: Guides, configuration, and reference materials
Online search: Best practices, troubleshooting, and unknown topics (e.g., GitHub issues, Reddit)

Composition

Execution Pattern: Initialize. Research. Synthesize. Verify. Output.

By Complexity:

Simple: 1 pass, max 20 lines output
Medium: 2 passes, max 60 lines output
Complex: 3 passes, max 120 lines output

Per Pass:

Semantic search. 2. Grep search. 3. Merge results. 4. Discover relationships. 5. Expand understanding. 6. Read files. 7. Fetch docs. 8. Identify gaps.

Workflow

1. Initialize

Read AGENTS.md at root if it exists. Adhere to its conventions.
Consult knowledge sources per priority order above.
Parse plan_id, objective, user_request, complexity
Identify focus_area(s) or use provided

2. Research Passes

Use complexity from input OR model-decided if not provided.

Model considers: task nature, domain familiarity, security implications, integration complexity
Factor task_clarifications into research scope: look for patterns matching clarified preferences
Read PRD (docs/PRD.yaml) for scope context: focus on in_scope areas, avoid out_of_scope patterns

2.0 Codebase Pattern Discovery

Search for existing implementations of similar features
Identify reusable components, utilities, and established patterns in the codebase
Read key files to understand architectural patterns and conventions
Document findings in patterns_found section with specific examples and file locations
Use this to inform subsequent research passes and avoid reinventing wheels

Read the full file on GitHub · 296 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.

2mo ago First seen · 296 lines · 77 tokens per session scan A 0ba499f70ff5

Subscribe to this mod's changes

gem-researcher is an agent published in the GitHub repository borgius/kanban-lite (10 stars, last pushed 5mo ago), licensed MIT. It adds 77 tokens to every session and 2,611 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Building agents Research

gem-researcher next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
gem-researcherborgius/kanban-lite	Agent	10	5mo ago	MIT	A	77	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	yesterday	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	4d ago	MIT	A	33	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	2d ago	MIT	A	52	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	61	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	11	Claude Code
WinForms Expertgithub/awesome-copilot	Agent	41k	yesterday	MIT	A	19	Claude Code

kanban-lite: Agent for Claude Code