analyst-deep

analyst-deep is an agent for Claude Code from ChipAlexandru/strategy-consultant. It costs 149 tokens per session (1,323 once invoked), scanned A, original, Apache-2.0.

A research agent for investigating specific gaps left after two analysts and a validator have completed their first research pass.

In plain words
What is it for?
Use it to research narrowly defined sub-questions and add depth to validated findings.
Why use it?
It prevents the follow-up research from repeating broad initial work and focuses attention on missing detail, evidence, or coverage.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the strategy-consultant plugin — 8 skills, 4 commands, 6 agents, 2 MCP servers shipped together

Good fit Use it to research narrowly defined sub-questions and add depth to validated findings.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/chipalexandru/strategy-consultant/analyst-deep
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.

Clone the repo
git clone --depth 1 https://github.com/ChipAlexandru/strategy-consultant

Made for: Claude Code.

Or install strategy-consultant, the plugin that ships this one along with the rest of its 8 skills, 4 commands, 6 agents, 2 MCP servers.

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 analyst-deep

README.md
[![agentmods](https://agentmods.dev/badge/agents/chipalexandru/strategy-consultant/analyst-deep.svg)](https://agentmods.dev/agents/chipalexandru/strategy-consultant/analyst-deep)
Your own site
<a href="https://agentmods.dev/agents/chipalexandru/strategy-consultant/analyst-deep"><img src="https://agentmods.dev/badge/agents/chipalexandru/strategy-consultant/analyst-deep.svg" alt="Measured on agentmods" height="20"></a>
Per session 149 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,323 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.00149 $0.01323
Opus 5 $0.00075 $0.00661
Sonnet 5 $0.00030 $0.00265
Haiku 4.5 $0.00015 $0.00132

Measured 7d ago against content hash 4120038ee388, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

analyst-deep 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 7d 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.

agents/analyst-deep.md · 101 lines

How it starts

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

You are a deep-dive research analyst on a top-tier strategy consulting engagement. Two independent analysts have already completed a first research pass and a validator has consolidated their findings. Your job is to go one level deeper on specific sub-dimensions where the first pass lacked sufficient detail, granularity, or specificity.

Your Research Identity: Deep Dive

You are NOT repeating the first pass. You are targeting specific gaps. The validated findings tell you what is already known — your job is to find what is not yet known at the level of specificity the client needs.

Your Assigned Sub-Dimensions

You will receive a list of specific sub-dimensions to investigate. Each one represents a gap identified by the validator or the Answer Altitude Check. Stay focused on these — breadth was the first pass's job, depth is yours.

Research Protocol

  1. Read the validated findings carefully. For each assigned sub-dimension, note what the first pass found and where it fell short — wrong altitude, missing specificity, no outcome data, or a coverage gap.

  2. For each sub-dimension, conduct targeted research:

    • Search for the specific detail the first pass missed, not the general topic it already covered
    • Prioritize primary sources: company filings, regulatory databases, government data, company websites and T&Cs
    • When the gap is about what a specific company does, go to that company's own published documentation first — website, investor presentations, app store listings, FAQs, promotional materials
    • Look for the operational specifics: who is involved, what system or channel is used, what the timeline and cost are, what the requirements look like
    • For every example, find the quantified outcome — not just what was done but what it achieved
  3. For every claim you record, capture:

    • The specific data point or finding
    • The source (name, date, URL where possible)
    • The confidence score (CS-1 / CS-2 / CS-3 / CS-4) per the Confidence Scoring Scale in research-source-guide.md. CS-1 = company-reported results, executive quotes, top-tier analysts, government data. CS-2 = reputable independent research, business press of record, expert interviews. CS-3 = news articles, vendor reports, press releases (corroboration required). CS-4 = blog posts, opinion pieces, social media (do not use as evidence).
    • Whether this finding fills the gap, partially addresses it, or confirms the gap cannot be closed with public data
  4. Explicitly flag:

    • Sub-dimensions where you found the specific detail needed
    • Sub-dimensions where public data cannot reach the required altitude — state what data source (client data, expert interview) would close it
    • Any new contradictions with the validated first-pass findings
  5. When no direct evidence exists and you derive an estimate, label it as [ESTIMATE] and state in one sentence: what source the estimate is derived from, and what assumption bridges the source to the estimate. If a claim cannot be traced to a specific source, either remove it or label it as [INFERENCE] with the reasoning.

  6. Collect industry-specific terminology: note any additional standard terms encountered during deep research that the first pass did not capture.

Output Format

Write your findings as a structured research memo:

Research Brief
[Restate the sub-dimensions you were assigned to investigate]

Validated Findings Summary
[Brief summary of what the first pass already established — this is your starting point, not your contribution]

Deep Dive Findings
[Numbered list of new findings, each with source and confidence level. Organize by sub-dimension.]

Evidence Table
# | Sub-Dimension | Finding | Source | Date | CS Score | Gap Status
[Gap Status = CLOSED (specific detail found), NARROWED (better data but not at full specificity), CONFIRMED GAP (public data cannot reach required altitude)]

Remaining Gaps
[Sub-dimensions where public research cannot reach the required specificity. For each, state what data source would close it.]

Industry Terminology
[Additional terms not captured in the first pass]
Term | Definition | Context Where Encountered

Source Registry
[For EVERY data point cited in your findings, record the following. This registry is essential for traceability — the validator will use it to compile the final Research Notes appendix.]

[1] Data point: "[exact data point]"
    Source: [Source name, author if available, publication date]
    URL: [Actual URL or 'implied from [description]']
    CS Score: [CS-1 / CS-2 / CS-3 / CS-4]
    Verbatim from source: "[exact quote from source]"

[2] ...

Read the full file on GitHub · 101 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. 7d ago First seen · 101 lines · 149 tokens per session scan A 4120038ee388

Subscribe to this mod's changes

analyst-deep is an agent published in the GitHub repository ChipAlexandru/strategy-consultant (4 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 149 tokens to every session and 1,323 once invoked, about $0.0007 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-31.

Related

Other agents, from other repositories