analyst

A requirements-analysis agent that turns a user request into a structured TASK.md file with a Requirements Traceability Matrix, a table linking each requirement to planned work.

In plain words
What is it for?
Use it before architecture and planning to capture requirements, create the task artifact, archive an existing task when needed, and audit the task register.
Why use it?
It makes the requested work explicit and checkable before architecture and implementation. This helps prevent requirements from being missed or overwritten without preserving the previous task.

Agent for Claude Code

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/matrixfounder/agentic-development/analyst
Clone the repo
git clone --depth 1 https://github.com/MatrixFounder/Agentic-development

Made for: Claude Code.

Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 258 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.00030 $0.00258
Opus 5 $0.00015 $0.00129
Sonnet 5 $0.00006 $0.00052
Haiku 4.5 $0.00003 $0.00026

Measured yesterday against content hash f3bf4b52a8ea, 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.

.claude/agents/analyst.md · 19 lines

What it actually says

You are the Analyst teammate. Full system prompt, methodology, skill loads, and quality checklist live in System/Agents/02_analyst_prompt.md — read and follow strictly.

Subagent adaptations

  • Write docs/TASK.md directly (primary artifact). If a prior TASK.md exists, apply skill-archive-task before overwriting.
  • Bash is granted for the two scripts the prompt makes mandatory: .agent/tools/task_id_tool.py (Task ID — the prompt forbids eyeballing docs/tasks/) and .agent/skills/artifact-formalizer/scripts/scan_register.py (register audit), plus the skill-archive-task rotation commands. Everything else stays read-only; see skill-safe-commands.
  • Return JSON summary: {"task_file": "docs/TASK.md", "blocking_questions": [...]}.
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 · 19 lines · 30 tokens per session scan A f3bf4b52a8ea

Subscribe to this mod's changes

analyst is an agent published in the GitHub repository MatrixFounder/Agentic-development (5 stars, last pushed 19d ago), licensed Apache-2.0. It adds 30 tokens to every session and 258 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-08-31.