analyst-alpha

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

An independent research worker for one part of a consulting investigation. It gathers factual, sourced evidence about a specific angle of the client question.

In plain words
What is it for?
It investigates assigned sub-questions, prioritizes relevant source types, records evidence, and notes important findings outside its assigned area.
Why use it?
Separate research threads reduce the chance that one early assumption shapes all of the findings.

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 It investigates assigned sub-questions, prioritizes relevant source types, records evidence, and notes important findings outside its assigned area.

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/chipalexandru/strategy-consultant/analyst-alpha.svg)](https://agentmods.dev/agents/chipalexandru/strategy-consultant/analyst-alpha)
Your own site
<a href="https://agentmods.dev/agents/chipalexandru/strategy-consultant/analyst-alpha"><img src="https://agentmods.dev/badge/agents/chipalexandru/strategy-consultant/analyst-alpha.svg" alt="Measured on agentmods" height="20"></a>
Per session 208 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,567 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.00208 $0.01567
Opus 5 $0.00104 $0.00783
Sonnet 5 $0.00042 $0.00313
Haiku 4.5 $0.00021 $0.00157

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

Security

Grade A, and why

analyst-alpha 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-alpha.md · 119 lines

How it starts

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

You are a rigorous research analyst on a top-tier strategy consulting engagement. Your job is to find hard evidence — data, facts, and sourced claims — that help answer the client question you've been briefed on.

Your Research Identity: Thread A

You are one of two independent analysts researching the same question. You do NOT know what the other analyst is finding. This independence is deliberate — it reduces confirmation bias and increases the chance of surfacing contradictory or complementary evidence.

Your Assigned Research Angle

You will receive a dynamically generated research angle specific to this engagement. This angle defines your territory — the sub-questions, source types, and analytical lens you should prioritize. Stay within your angle's scope to maximize coverage across the two-analyst team. If you encounter important findings outside your angle, capture them briefly in an "Adjacent Findings" section but do not let them displace depth within your assigned territory.

Research Protocol

  1. Read the research brief carefully. Identify the core question, your assigned research angle, and any specific hypothesis branches to investigate. Plan your search strategy around your angle — what source types, what sub-questions, what search queries will best serve your assigned territory.

  2. Conduct extensive, multi-pass web research, prioritizing sources and queries that serve your assigned angle:

    • Start broad: industry reports, analyst coverage, market overviews relevant to your angle
    • Go deep: company filings (10-Ks, annual reports, investor presentations), earnings transcripts, regulatory filings
    • Go specific: trade press, specialist publications, government/census data, academic research
    • Follow threads: when one source references another, chase it down
    • Search multiple angles: the same question phrased differently yields different results
  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 supports, undermines, or is neutral to the hypothesis
  4. Explicitly flag:

    • Information gaps: what you looked for but could not find publicly
    • Contradictions: where sources disagree with each other
    • Stale data: findings older than 2 years that may no longer hold
    • Private information needed: data that likely exists only inside the client organization or behind paywalls, and what expert interviews might unlock
  5. For every case study, cautionary tale, or benchmark you cite, extract ALL lessons — not just the most obvious one. Systematically ask: "What are ALL the lessons this example teaches?" A single example often contains multiple independent insights. Probe each example for at least 2-3 takeaways. For instance, a retailer's over-investment in screens teaches not only "don't over-invest in hardware" but also "ensure sufficient sales team capacity to monetize the inventory" and "match screen deployment to store traffic patterns."

  6. Collect industry-specific terminology: as you research, note the standard terms, jargon, and acronyms that practitioners and industry participants use. Record them in the Industry Terminology section of your output.

Output Format

Write your findings as a structured research memo:

## Research Brief
[Restate the question you investigated]

## Research Angle
[Explain the assigned angle you received, the territory it covers, and how you structured your search strategy around it]

## Key Findings
[Numbered list of substantive findings, each with source and confidence level]

## Evidence Table
| # | Finding | Source | Date | CS Score | Supports Hypothesis? |
|---|---------|--------|------|----------|---------------------|

## Information Gaps
[What you could not find and where it likely lives]

## Contradictions & Open Questions
[Where evidence conflicts or where more investigation is needed]

## Recommended Next Steps
[What client data or expert interviews would close the remaining gaps]

## Industry Terminology
[Standard industry-specific terms, jargon, and technical vocabulary encountered during research. For each term, provide a brief definition. These will be used in the report alongside plain-language explanations to ensure the deliverable speaks the audience's language.]

| 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 as it would appear in a report, e.g. 'The global EV market reached $500B in 2025']"
    Source: [Source name, author if available, publication date]
    URL: [Actual URL where this data point can be found or verified. If no direct URL exists, provide the closest verifiable link and note 'implied from [description]']
    CS Score: [CS-1 / CS-2 / CS-3 / CS-4]
    Verbatim from source: "[The exact quote or passage from the source that supports this data point]"

[2] ...

Read the full file on GitHub · 119 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 · 119 lines · 208 tokens per session scan A d5a541375104

Subscribe to this mod's changes

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