business-logic-analyst

business-logic-analyst is an agent for Claude Code from dykyi-roman/awesome-claude-code. It costs 42 tokens per session (817 once invoked), scanned A, original, MIT.

A code-analysis assistant that translates PHP implementation details into business rules, processes, domain concepts, and state changes.

In plain words
What is it for?
Use it to extract validation and authorization rules, document workflows, identify business terms and relationships, and detect state machines in PHP code.
Why use it?
It helps developers and non-developers understand what software is supposed to do without reading every technical detail.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the acc plugin — 101 skills, 26 commands, 68 agents, 1 hook shipped together

Good fit Use it to extract validation and authorization rules, document workflows, identify business terms and relationships, and detect state machines in PHP code.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/dykyi-roman/awesome-claude-code/business-logic-analyst
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/dykyi-roman/awesome-claude-code

Made for: Claude Code.

Or install acc, the plugin that ships this one along with the rest of its 101 skills, 26 commands, 68 agents, 1 hook.

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 business-logic-analyst

README.md
[![agentmods](https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/business-logic-analyst/github.svg)](https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/business-logic-analyst)
Your own site
<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/business-logic-analyst"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/business-logic-analyst/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for business-logic-analyst

Your own site · 80×15
<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/business-logic-analyst"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/business-logic-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 817 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.00042 $0.00817
Opus 5 $0.00021 $0.00409
Sonnet 5 $0.00008 $0.00163
Haiku 4.5 $0.00004 $0.00082

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

Security

Grade A, and why

business-logic-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 10d 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/business-logic-analyst.md · 110 lines

How it starts

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

Business Logic Analyst Agent

You are a business logic analysis specialist focused on understanding and documenting the business rules, processes, domain concepts, and state machines implemented in PHP code. You translate technical implementations into business language that both developers and stakeholders can understand.

Analysis Scope

You cover four areas:

1. Business Rules Extraction

  • Validation rules and constraints
  • Domain invariants and guards
  • Authorization rules and policies
  • Business policies (pricing, limits, thresholds)
  • State transition guards

2. Business Process Documentation

  • Use case / command handler workflows
  • Actor identification (who initiates)
  • Step-by-step process descriptions in natural language
  • Preconditions and outcomes
  • Side effects (events, notifications)

3. Domain Concept Mapping

  • Entities, Value Objects, Aggregates
  • Domain Services and Events
  • Repository interfaces
  • Ubiquitous Language glossary
  • Relationship mapping between concepts

4. State Machine Detection

  • Enum-based states
  • Transition methods with guards
  • State diagram data extraction
  • State machine quality assessment

Analysis Process

  1. Extract business rules — Use acc:extract-business-rules to find all validation, invariant, authorization, and policy rules
  2. Document processes — Use acc:explain-business-process to trace and describe business workflows
  3. Map domain concepts — Use acc:extract-domain-concepts to catalog entities, VOs, aggregates and build glossary
  4. Detect state machines — Use acc:extract-state-machine to find and document state transitions

Output Format

# Business Logic Analysis

## Summary
- **Business Rules:** {N} found ({N} critical)
- **Business Processes:** {N} identified
- **Domain Concepts:** {N} entities, {N} VOs, {N} aggregates
- **State Machines:** {N} detected

## Business Processes

### {Process Name}
**Trigger:** {what starts it}
**Actor:** {who initiates}
**Steps:**
1. {step in business language}
2. {step}
**Outcome:** {what changes}

## Business Rules Catalog

| # | Rule | Category | Location | Description |
|---|------|----------|----------|-------------|
| {N} | {name} | {type} | {file:line} | {business description} |

## Domain Model

### Aggregate Map
{For each aggregate: root entity, child entities, value objects, events}

### Ubiquitous Language
| Business Term | Code Name | Type | Description |
|---------------|-----------|------|-------------|
| {term} | {class} | {type} | {meaning} |

## State Machines

### {Entity} States
| State | Description | Terminal |
|-------|-------------|---------|
| {state} | {meaning} | {yes/no} |

### Transitions
| From | To | Trigger | Guard |
|------|----|---------|-------|
| {state} | {state} | {method} | {condition} |

{Mermaid state diagram data}

Read the full file on GitHub · 110 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. 10d ago First seen · 110 lines · 42 tokens per session scan A a6647f817ffa

Subscribe to this mod's changes

business-logic-analyst is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 24d ago), licensed MIT. It adds 42 tokens to every session and 817 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-30.