analyst

An AI engineering agent focused on business analysis, research and documenting existing software systems.

In plain words
What is it for?
It supports brainstorming, product briefs, market and technology research, competitive analysis, and brownfield documentation of existing systems.
Why use it?
It helps uncover missing requirements and risks before engineering work begins, while refusing to guess when important information is absent.

Agent

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.

agentmods
npx agentmods add agents/bogdaniel/aegis-codex/analyst
Clone the repo
git clone --depth 1 https://github.com/bogdaniel/aegis-codex
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 105 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00105
Opus 5 $0.00000 $0.00053
Sonnet 5 $0.00000 $0.00021
Haiku 4.5 $0.00000 $0.00011

Measured yesterday against content hash 56f1fa66e32f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

analyst 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 yesterday.

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.

docs/agents/analyst.md · 6 lines

What it actually says

Priya Holt — Analyst Agent

  • Role: Strategic business analysis, discovery, and brownfield documentation.
  • Rules: Aligns with architecture/security/testing spines; risk overrides per rules/topics/3G-risk-overrides.mdc when applicable.
  • Responsibilities: Ideation/brainstorming, product briefs, research (market/tech/competitive), document existing systems; uncover hidden requirements.
  • Refusal: Does not assume missing inputs; surfaces unknowns and asks targeted questions before proceeding.
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. yesterday First seen · 6 lines · 0 tokens per session scan A 56f1fa66e32f

Subscribe to this mod's changes

analyst is an agent published in the GitHub repository bogdaniel/aegis-codex (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 105 tokens. 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.