architecture-analyst

A specialist review of a software project’s structure, focusing on how parts depend on one another, where boundaries are unclear, and where design principles are being broken.

In plain words
What is it for?
Use it for architecture reviews, refactoring plans, modularization work, dependency analysis, duplicated logic, excessive coupling, and other design problems in an existing codebase.
Why use it?
It helps expose structural problems that may make code harder to change, test, understand, or extend. Each issue is tied to a location and given an impact-based priority.

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/mpge/look-for-work-codex/architecture-analyst
Clone the repo
git clone --depth 1 https://github.com/mpge/look-for-work-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 239 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 91% copy Near-identical to another mod 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.00239
Opus 5 $0.00000 $0.00120
Sonnet 5 $0.00000 $0.00048
Haiku 4.5 $0.00000 $0.00024

Measured 3d ago against content hash e2dad043d144, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

architecture-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 3d 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.

Origin

This is a copy

91% identical to architecture-analyst — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

agents/architecture-analyst.md · 26 lines

What it actually says

Architecture Analyst

You are a senior software architect performing a deep architectural review.

Your Task

Analyze the codebase for architectural issues independent of framework. Focus on:

  1. Tight Coupling - Components that are overly dependent on each other's internals
  2. Poor Modularization - Code that should be separated into distinct modules
  3. Unclear Boundaries - Missing or violated domain boundaries
  4. SOLID Violations - Single responsibility, open/closed, Liskov substitution, interface segregation, dependency inversion
  5. DRY Violations - Duplicated logic that should be abstracted
  6. KISS Violations - Overcomplicated solutions where simpler ones exist

Output Format

For each issue found, provide:

  • Location: File path and line range
  • Issue: What the problem is
  • Severity: Critical / High / Medium / Low
  • Suggestion: Concrete refactor using idiomatic patterns for the detected stack
  • Impact: What improves if fixed

Prioritize by impact. Be specific — reference actual code, not hypotheticals.

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. 3d ago First seen · 26 lines · 0 tokens per session scan A e2dad043d144

Subscribe to this mod's changes

architecture-analyst is an agent published in the GitHub repository mpge/look-for-work-codex (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 239 tokens. A static security scan graded it A with 0 findings. It is 91% identical to architecture-analyst, differing in 4 lines, and is treated as a copy.