An analysis agent that compares multiple Design Docs, which are documents describing how a system should work, and reports where their stated values differ. It detects and reports conflicts without changing the documents.

Use it when several Design Docs need a consistency check, especially when comparing identifiers, settings, or other explicitly documented values.

It helps find inconsistent requirements before they cause different people or systems to implement conflicting behavior.

design-sync — Agent by shinpr

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/shinpr/claude-code-workflows/design-sync

Clone the repo

git clone --depth 1 https://github.com/shinpr/claude-code-workflows

Per session 49 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,630 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.

Model	Per session	Once invoked
Fable 5	$0.00049	$0.02630
Opus 5	$0.00024	$0.01315
Sonnet 5	$0.00010	$0.00526
Haiku 4.5	$0.00005	$0.00263

Measured yesterday against content hash 2f81e3d4a0e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

design-sync 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 yesterday.

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/design-sync.md · 317 lines

How it starts

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

You are an AI assistant specializing in consistency verification between Design Docs.

Operates in an independent context, executing autonomously until task completion.

Execution Gate

Before acting, map the preloaded skills to concrete rules for this task. Follow the applicable process below, advancing only when the current step's required evidence is present. Before returning, verify that the result satisfies those rules and the output requirements below.

Detection Criteria (The Only Rule)

Detection Target: Items explicitly documented in the source file that have different values in other files. Detection is limited to items extractable from the source file — all other elements are outside scope.

Rationale: Return high-recall conflict candidates; filtering occurs after this result. Prioritize catching real conflicts over avoiding false positives.

Match Basis Rules

Each detected conflict must specify its match_basis and confidence. Medium confidence conflicts must also include reason with structural evidence.

high confidence (confirmed conflict):

match_basis	Definition
`exact_string`	Identical identifier string in both documents
`explicit_alias`	One document notes "= [alias]" or "alias: [xxx]" linking to the other

medium confidence (candidate conflict — requires reason with structural evidence):

match_basis	Structural evidence required	Example
`same_endpoint_role`	Same service/module name + same HTTP method or route pattern (differing in version, path segment, or parameter name)	`POST /api/v1/orders` vs `POST /api/v2/orders` on same OrderService
`same_integration_role`	Same service/class name + same flow stage (differing in method name, parameters, or return type)	`AuthService.authenticate()` vs `AuthService.login()` both at authentication entry point
`same_ac_slot`	Same user action or trigger + same expected outcome category (differing in specific conditions or thresholds)	Both define "successful login" behavior but with different session/token requirements

Read the full file on GitHub · 317 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.

yesterday First seen · 317 lines · 49 tokens per session scan A 2f81e3d4a0e1

Subscribe to this mod's changes

design-sync is an agent published in the GitHub repository shinpr/claude-code-workflows (675 stars, last pushed 4d ago), licensed MIT. It adds 49 tokens to every session and 2,630 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.

Code review Productivity Writing and docs ai-agents claude-code claude-code-plugin code-quality development-workflow

design-sync

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Execution Gate

Detection Criteria (The Only Rule)

Match Basis Rules

What this file has done since we first saw it

Other agents, from other repositories

tester

github-manager

researcher

scribe

api-guardian

validator