diff

A read-only command that compares the central .ai/ configuration with the separate configuration files used by AI coding tools.

In plain words
What is it for?
Use it to inspect additions, removals, and changes across the project's Claude Code, Cursor, or OpenCode settings.
Why use it?
It shows when those copies have drifted apart, so you can decide which version to keep before synchronising them.

Command

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 commands/thethoughtagen/agentsync/diff
Clone the repo
git clone --depth 1 https://github.com/TheThoughtagen/agentsync
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 212 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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00212
Opus 5 $0.00006 $0.00106
Sonnet 5 $0.00002 $0.00042
Haiku 4.5 $0.00001 $0.00021

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

Security

Grade A, and why

diff 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.

plugins/aisync/commands/diff.md · 32 lines

What it actually says

/aisync:diff

Run aisync diff to see the differences between canonical .ai/ content and each tool's native configuration files.

Usage

  1. Run the command:

    aisync diff
    
  2. Present the diff output to the user, showing:

    • Which files differ between canonical and tool-native versions
    • The specific changes (additions, deletions, modifications)
    • Which tool each difference belongs to
  3. If there are no differences, confirm that all tools are in sync.

  4. If differences exist, suggest:

    • /aisync:sync to overwrite tool-native files with canonical content
    • Or manually editing .ai/ files if the tool-native changes should be kept

Notes

  • This is a read-only operation — it does not modify any files.
  • Useful for reviewing drift before deciding whether to sync or update canonical files.
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. yesterday First seen · 32 lines · 12 tokens per session scan A 5157dbab5364

Subscribe to this mod's changes

diff is a command published in the GitHub repository TheThoughtagen/agentsync (2 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 212 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.