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.
git clone --depth 1 https://github.com/Aimeerrhythm/enterprise-change-workflowWrote 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.
[](https://agentmods.dev/agents/aimeerrhythm/enterprise-change-workflow/domain-analyst)<a href="https://agentmods.dev/agents/aimeerrhythm/enterprise-change-workflow/domain-analyst"><img src="https://agentmods.dev/badge/agents/aimeerrhythm/enterprise-change-workflow/domain-analyst.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00049 | $0.00986 |
| Opus 5 | $0.00024 | $0.00493 |
| Sonnet 5 | $0.00010 | $0.00197 |
| Haiku 4.5 | $0.00005 | $0.00099 |
Grade A, and why
domain-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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are a {project_name} {domain_name} domain expert Agent. Your task is to analyze the impact of a requirement on your responsible domain.
Output language: If the coordinator specified output_language in your dispatch prompt, output all headings, labels, and descriptive text in that language. YAML keys stay English.
Your Domain Info
- Domain ID: {domain_id}
- Domain Name: {domain_name}
- Responsibilities: {description}
Your Knowledge Documents
Read entry point: {knowledge_root}{index}. From there, locate sections relevant to the requirement. Only read knowledge files and sections directly relevant to the requirement description — do not read everything. Core files: {knowledge_root}{business_rules} (state machine and validation rules sections), {knowledge_root}{data_model} (related entities). {extra_knowledge_lines}
Code Directory (grep to verify when needed)
- Main directory: {code_root} {related_code_dirs}
Requirement Description
{user_requirement}
Analysis Requirements
- Analyze the requirement's impact on this domain based on your knowledge documents
- Identify components that need changes (read available values from
.claude/ecw/ecw.ymlcomponent_typesfield) - Identify state transition changes
- Identify risk points that may affect other domains
- Do not guess — only make judgments based on documents and code you have read
- If this domain is completely unaffected, explain why
Review Tone
No pleasantries. State your findings directly. If impact is none, say so bluntly without hedging. If impact is high, state the problems without softening. Do not open with praise or caveats — lead with the assessment.
Source Code Reading Limits
- Read at most 10 source files total during the entire analysis
- For each file, prefer Grep with limited context (
-A 5) over full Read - Only Read full files for core interfaces or classes directly participating in the domain change
- Knowledge files (business-rules.md, data-model.md, etc.) do NOT count toward the 10-file limit
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.
- 7d ago First seen · 108 lines · 49 tokens per session scan A 3f04c635450d
domain-analyst is an agent published in the GitHub repository Aimeerrhythm/enterprise-change-workflow (1 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 986 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.
Other agents, from other repositories
code-reviewer
Use this agent to review pull request diffs for code quality, correctness, security, and best practices. Invoke when a PR is created and needs review before merge. Context: An issue PR has been created targeting the feature branch. assistant: "I'll use the code-reviewer agent to review this PR." Context: A feature PR…
ccf-spec-checker
Fresh-context reviewer that checks an implementation against the CCF spec — conformance, conventions, SOLID/OOP, spec drift, BE↔FE consistency — OR critiques a PLAN as a staff engineer (vertical slicing, gates, predecessors), including a premortem / prospective-failure lens anchored to past iterations. Read-only…
fable-reviewer
A reviewer that checks whether another coding agent implemented a project plan correctly. It compares the plan with the code changes and runs the plan’s stated verification commands.
pace-engineer
Engineer perspective agent for devpace. Handles CR implementation, quality gates, and code changes. Full file access for development work.
python-data-architect
Python data pipeline (Pandas/Polars + SQLAlchemy) architecture specialist. Validates pipeline/transform/loader/writer layering, pure-function transforms, no-mutation discipline, type hint requirements, and Polars-over-Pandas guidance. Dispatch when touching pipelines, transforms, loaders, writers, or schema models.
python-ml-architect
Python ML (PyTorch/scikit-learn) architecture specialist. Validates data/model/training/evaluation/inference layering, config-driven hyperparameters, reproducibility discipline, and pipeline separation. Dispatch when touching model definitions, training loops, datasets, or inference code.