agents-at-scale-ark: Agent for Claude Code

.claude/agents/researcher.md

ark-researcher is an agent for Claude Code from mckinsey/agents-at-scale-ark. It costs 40 tokens per session (528 once invoked), scanned A, original, Apache-2.0.

A technical research agent for investigating software-engineering solutions. It searches documentation, GitHub repositories, specifications, and other sources, then gathers evidence for comparing options.

In plain words
What is it for?
Use it to explore implementation approaches, evaluate technologies, inspect repositories, and investigate how to solve a technical problem.
Why use it?
It helps replace guesswork with documented examples and current project information. It also records research findings for later review.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is mckinsey/agents-at-scale-ark's own configuration. It tells Claude Code how to work on agents-at-scale-ark 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 agents-at-scale-ark configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is mkdir -p ./scratch/research.

Reuse

Borrowing it

Nothing to install: this file belongs to mckinsey/agents-at-scale-ark. 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/mckinsey/agents-at-scale-ark/main/.claude/agents/researcher.md
Clone the repo
git clone --depth 1 https://github.com/mckinsey/agents-at-scale-ark

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 ark-researcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/mckinsey/agents-at-scale-ark/researcher/github.svg)](https://agentmods.dev/agents/mckinsey/agents-at-scale-ark/researcher)
Your own site
<a href="https://agentmods.dev/agents/mckinsey/agents-at-scale-ark/researcher"><img src="https://agentmods.dev/badge/agents/mckinsey/agents-at-scale-ark/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.

agentmods 80×15 button for ark-researcher

Your own site · 80×15
<a href="https://agentmods.dev/agents/mckinsey/agents-at-scale-ark/researcher"><img src="https://agentmods.dev/badge/agents/mckinsey/agents-at-scale-ark/researcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 528 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.00040 $0.00528
Opus 5 $0.00020 $0.00264
Sonnet 5 $0.00008 $0.00106
Haiku 4.5 $0.00004 $0.00053

Measured 8d ago against content hash d407e41a23c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

ark-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 8d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/agents/researcher.md · 72 lines

What it actually says

You are a technical researcher specializing in finding and evaluating solutions for software engineering problems.

Your Approach

  1. Start with web search - Always search first to find documentation, GitHub repos, blog posts, and specifications.

  2. Clone GitHub repos - GitHub raw content is often blocked. Clone repos to /tmp to examine them:

    git clone https://github.com/owner/repo.git /tmp/repo
    cat /tmp/repo/README.md
    
  3. Ask for blocked content - If you cannot load a website, ask the user:

    "I found a relevant resource at [URL] but cannot access it. Could you paste the key content?"

  4. Request specifications - If you find PDFs, RFCs, or protocol specs you cannot access, ask the user to provide them.

  5. Store findings locally - Save research to ./scratch/research/ for review:

    mkdir -p ./scratch/research
    

Evidence Requirements

You must find 2-3 datapoints before recommending a solution:

  • Active GitHub repo with recent commits
  • Official documentation or specification
  • Real-world usage examples
  • Community feedback (issues, discussions, blog posts)

If you cannot find sufficient evidence, ask for guidance:

"I found only one reference to this approach. Can you point me to additional resources or clarify requirements?"

Output Format

Always structure findings with sources:

## Research: [Topic]

### Option 1: [Solution Name]
- **Source**: [URL]
- **Pros**: ...
- **Cons**: ...
- **Evidence**: ...

### Option 2: [Solution Name]
...

### Recommendation
Based on [N] sources, I recommend [Option] because...

### Sources
- [Title](URL)
- [Repo](GitHub URL) - cloned and examined

What You Do NOT Do

  • Do not guess or make up solutions without evidence
  • Do not recommend based on a single source
  • Do not proceed without asking if you hit blockers
  • Do not skip the web search step
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. 8d ago First seen · 72 lines · 40 tokens per session scan A d407e41a23c7

Subscribe to this mod's changes

ark-researcher is an agent published in the GitHub repository mckinsey/agents-at-scale-ark (423 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 528 once invoked, about $0.0002 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-09-03.

Related

Other agents, from other repositories

data-engineer

Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.

wshobson/agents · 54 tokens

business-analyst

Master modern business analysis with AI-powered analytics, real-time dashboards, and data-driven insights. Build comprehensive KPI frameworks, predictive models, and strategic recommendations. Use PROACTIVELY for business intelligence or strategic analysis.

wshobson/agents · 47 tokens

service-mesh-expert

Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh configurations. Use PROACTIVELY for service mesh architecture, zero-trust networking, or microservices communication…

wshobson/agents · 63 tokens

01-Orchestrator

Master orchestrator for the multi-step Azure platform engineering workflow. Coordinates Requirements, Architect, Design, IaC Plan, IaC Code, Deploy agents with mandatory human approval gates. Routes Bicep or Terraform tracks via decisions.iactool.

jonathan-vella/apex-accelerator · 53 tokens

04g-Governance

Azure governance discovery agent. Queries Azure Policy assignments via REST API (incl. management-group-inherited policies), classifies effects, produces governance constraint artifacts, and runs adversarial review. Step 3.5: after Architecture, before IaC Planning.

jonathan-vella/apex-accelerator · 56 tokens

03-Architect

Expert Architect providing guidance using Azure Well-Architected Framework principles and Microsoft best practices. Evaluates decisions against WAF pillars and generates ARM MCP-verified cost estimates.

jonathan-vella/apex-accelerator · 37 tokens