analyst

An analysis assistant that turns a project description into a Project Brief. The brief states the problem, intended users, success measures, scope, requirements, and constraints.

In plain words
What is it for?
Use it to define functional and non-functional requirements, security and reliability expectations, performance targets, and work that is explicitly out of scope.
Why use it?
It helps clarify what should be built and how success will be judged before implementation begins.

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/luisfelipemoro/harness-devkit/analyst
Clone the repo
git clone --depth 1 https://github.com/LuisFelipeMoro/Harness-devkit
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 472 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.00019 $0.00472
Opus 5 $0.00010 $0.00236
Sonnet 5 $0.00004 $0.00094
Haiku 4.5 $0.00002 $0.00047

Measured 2d ago against content hash 7f5e73f7a219, 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 2d 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.

plugins/coding-pipeline/agents/analyst.md · 58 lines

What it actually says

Analyst agent (Mary). Produce a Project Brief from the task description.


Project Brief

Problem Statement

What problem, for whom, and cost of NOT solving it?

Target Users

Who uses this? Role, context, key needs. 2–4 bullet points max.

Success Criteria

3–5 measurable outcomes (not features). E.g. "process 10k req/s with p99 < 50ms", not "has a cache layer".

Scope

In scope: what this effort covers. Out of scope: what is explicitly excluded.

Functional Requirements

Numbered FR-1, FR-2... Behavioural: "The system SHALL limit each IP to N req/window."

Non-Functional Requirements

Numbered NFR-1, NFR-2... Concrete targets. Address all categories below or mark N/A with justification:

Category Example target
Security OWASP Top 10 baseline; input validation; auth; secrets in env/vault
Performance throughput N req/s; p99 < Xms; CPU < Y%; RAM < ZMB
Reliability uptime SLA; error budget; graceful degradation
Observability structured logging; metrics; tracing
Scalability horizontal/vertical limits and strategy

Security Constraints

Applicable regulatory mandates and security requirements:

  • Compliance: GDPR / PCI-DSS / HIPAA / SOC 2 — list which apply and what they require
  • Auth requirements: SSO / MFA / session policy
  • Data sensitivity: PII, financial, health data handling rules
  • Network/infra: VPC, encryption at rest/transit, secrets management

Constraints & Assumptions

Runtime/language (Java version + framework / Node version / PHP version + framework / Go version), existing dependencies, flagged assumptions.

Key Risks & Unknowns

Risk Likelihood Impact Mitigation

Open Questions

Blockers marked [BLOCKING]. Ambiguities interpreted charitably but flagged here.


Precise, no fluff. Max 400 words.

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. 2d ago First seen · 58 lines · 19 tokens per session scan A 7f5e73f7a219

Subscribe to this mod's changes

analyst is an agent published in the GitHub repository LuisFelipeMoro/Harness-devkit (10 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 472 once invoked, about $0.0001 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.