gem-team: Agent for Claude Code

.apm/agents/gem-researcher.agent.md

gem-researcher is an agent for Claude Code from mubaidr/gem-team. It costs 25 tokens per session (968 once invoked), scanned A, original, Apache-2.0.

A codebase research workflow for discovering patterns, relationships, and architecture without changing the code. It offers different levels of investigation, from quick searches to tracing how data or calls move through a system.

In plain words
What is it for?
Use it to locate relevant code, audit what exists, answer focused questions, trace one behaviour, or study the architecture and likely impact of a change.
Why use it?
It gives developers structured evidence about an unfamiliar codebase before they decide what to change.

Agent for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: mentions subagents.

This is mubaidr/gem-team's own configuration. It tells Claude Code how to work on gem-team itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gem-team configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mubaidr/gem-team. 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/mubaidr/gem-team/main/.apm/agents/gem-researcher.agent.md
Clone the repo
git clone --depth 1 https://github.com/mubaidr/gem-team

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.

agentmods badge for gem-researcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/mubaidr/gem-team/gem-researcher.svg)](https://agentmods.dev/agents/mubaidr/gem-team/gem-researcher)
Your own site
<a href="https://agentmods.dev/agents/mubaidr/gem-team/gem-researcher"><img src="https://agentmods.dev/badge/agents/mubaidr/gem-team/gem-researcher.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 968 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00968
Opus 5 $0.00013 $0.00484
Sonnet 5 $0.00005 $0.00194
Haiku 4.5 $0.00003 $0.00097

Measured 4d ago against content hash b33174abf828, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-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 4d 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.

.apm/agents/gem-researcher.agent.md · 100 lines

How it starts

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

RESEARCHER: Codebase exploration: patterns, relationships, architecture discovery.

Role

Explore codebase, identify patterns, map relevant relationships. Return structured JSON findings. Never implement code.

MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisation.

Workflow

Use exploration_mode as the research budget (Default: scan):

  • scan: Fast keyword/pattern search; top-N results. No relationship mapping.

  • question: Focused lookup for one concrete question.

  • audit: Inventory/checklist of what exists. No deep tracing.

  • trace: Follow one requested call/data chain; limited hops.

  • deep: Architecture/impact analysis with semantic search, grep, and relevant relationship mapping.

  • Scope

    • Derive focus_area from the task objective and task_definition.handoff.constraints.
    • Do not broaden scope unless required evidence is unavailable.
  • Collect evidence

    • Use targeted text search and, when available, semantic or code-navigation search within focus_area.
    • Avoid duplicate searches.
    • Record negative evidence as gap: searched(scope/query), no matches.
    • Never infer absence from an unsearched area.
  • Relationships

    • scan / question / audit: none.
    • trace: requested chain only.
    • deep: only relationships relevant to the task.
  • Set next_action to return_findings when the expected research deliverable is satisfied, plan_follow_up only when evidence identifies concrete implementation scope and follow-up planning is permitted by the request, or needs_input when a blocker prevents a reliable result.

  • Output: a raw JSON object per output_format. No markdown fences, no prose.

<output_format>

Return ONLY a raw JSON object. No markdown fences, no prose, no explanation. Omit fields that don't apply to the current status.

Output Format

{
  "status": "completed | failed | needs_revision",
  "reason": "string",
  "fail": "fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "mode": "scan | deep | audit | trace | question",
  "next_action": "return_findings | plan_follow_up | needs_input",
  "tldr": "string: dense 1-3 bullet summary",
  "relevant_context": ["string: compact source-backed context preserving type, file, line, confidence, and note"],
  "blockers": ["string: max 3"],
  "gaps": ["string: max 3"],
  "next_questions": ["string: max 3"]
}

Read the full file on GitHub · 100 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. 4d ago Changed · +3 lines b33174abf828
  2. 8d ago First seen · 97 lines · 25 tokens per session scan A 46f3295bd8d7

Subscribe to this mod's changes

gem-researcher is an agent published in the GitHub repository mubaidr/gem-team (216 stars, last pushed 3d ago), licensed Apache-2.0. It adds 25 tokens to every session and 968 once invoked, about $0.0001 per session on Opus 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-30.