domain-negotiator

domain-negotiator is an agent for Claude Code from Aimeerrhythm/enterprise-change-workflow. It costs 28 tokens per session (886 once invoked), scanned A, original, MIT.

An agent that compares change plans from different parts of a multi-domain project. It checks whether another part's planned changes affect this domain's rules, interfaces, or shared resources.

In plain words
What is it for?
Use it during a cross-domain change review to assess interface changes, message changes, shared-resource effects, and risks raised by other domains.
Why use it?
It helps teams detect conflicts and missing coordination before separate changes are implemented.

Agent for Claude Code

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

Part of the ecw plugin — 15 skills, 3 commands, 7 agents shipped together

Good fit Use it during a cross-domain change review to assess interface changes, message changes, shared-resource effects, and risks raised by other domains.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/aimeerrhythm/enterprise-change-workflow/domain-negotiator
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/Aimeerrhythm/enterprise-change-workflow

Made for: Claude Code.

Or install ecw, the plugin that ships this one along with the rest of its 15 skills, 3 commands, 7 agents.

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 domain-negotiator

README.md
[![agentmods](https://agentmods.dev/badge/agents/aimeerrhythm/enterprise-change-workflow/domain-negotiator/github.svg)](https://agentmods.dev/agents/aimeerrhythm/enterprise-change-workflow/domain-negotiator)
Your own site
<a href="https://agentmods.dev/agents/aimeerrhythm/enterprise-change-workflow/domain-negotiator"><img src="https://agentmods.dev/badge/agents/aimeerrhythm/enterprise-change-workflow/domain-negotiator/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 domain-negotiator

Your own site · 80×15
<a href="https://agentmods.dev/agents/aimeerrhythm/enterprise-change-workflow/domain-negotiator"><img src="https://agentmods.dev/badge/agents/aimeerrhythm/enterprise-change-workflow/domain-negotiator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 886 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.00028 $0.00886
Opus 5 $0.00014 $0.00443
Sonnet 5 $0.00006 $0.00177
Haiku 4.5 $0.00003 $0.00089

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

Security

Grade A, and why

domain-negotiator 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 8d 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/domain-negotiator.md · 99 lines

How it starts

The opening of the file, as written. The whole thing — 99 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 (negotiation round).

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.

In Round 1 you performed independent analysis of the requirement. Now other domains have also completed their analysis. Your task is to assess whether other domains' change plans affect your domain.

Original Requirement


{user_requirement}

Your Round 1 Analysis Result

{round1_yaml_output}

Other Domains' Change Plans (Summary)

{for each other domain:}

{other_domain_name} Domain — {impact_level}

{summary} Changes: {affected_components as comma-separated "type:name" list} Risks pointing to you: {cross_domain_risks where target == current domain, one line each, or "None"}

If you need to verify business rules, read as needed: {knowledge_root}{business_rules}. Only read when other domains' changes may affect your domain's rules — do not preemptively read everything.

Negotiation Task

  1. Check if other domains' changes affect your domain (interface changes, message body changes, shared resource changes, etc.)
  2. If affected, describe the specific impact point and the companion changes needed on your side
  3. If you reported impact_level: none in Round 1, but other domains' changes do affect you, update your assessment
  4. If you discover conflicts between other domains' change plans and your domain (modifying same interface simultaneously, incompatible state machines, etc.), flag the conflict points
  5. If other domains' changes have zero impact on you, simply report revised_impact_level matching Round 1, leave other fields empty

Review Tone

No pleasantries. State conflicts and impacts directly. Do not soften findings or hedge assessments. If another domain's changes create a problem for yours, state the problem bluntly. Do not open with "other domains' plans look reasonable overall."

Read the full file on GitHub · 99 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. 8d ago First seen · 99 lines · 28 tokens per session scan A 81fa172bdd11

Subscribe to this mod's changes

domain-negotiator is an agent published in the GitHub repository Aimeerrhythm/enterprise-change-workflow (1 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 886 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.

Related

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…

skullninja/coco-workflow · 127 tokens

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…

naniiluja/ccf · 88 tokens

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.

newrise0410/claude-codex-workflow · 60 tokens

pace-engineer

Engineer perspective agent for devpace. Handles CR implementation, quality gates, and code changes. Full file access for development work.

arch-team/devpace · 29 tokens

python-cli-architect

Python CLI (Click/Typer) architecture specialist. Validates command/service layering, arg-parsing discipline, Rich output usage, and Pydantic Settings config. Dispatch when touching CLI commands, services, config, or output formatting.

onlygian/G-Forge · 51 tokens

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.

onlygian/G-Forge · 68 tokens