check

A read-only command that checks whether AI-tool files match the canonical configuration in `.ai/`. It returns success when everything matches and a non-zero exit status when differences, called drift, are found.

In plain words
What is it for?
Use it in CI pipelines and pre-commit checks, or to identify files that need syncing before running the sync command.
Why use it?
It catches configuration changes before they cause inconsistent behavior across tools. Its exit status also lets continuous integration systems, or CI pipelines, fail automatically when drift exists.

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/check
Clone the repo
git clone --depth 1 https://github.com/TheThoughtagen/agentsync
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 250 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.00015 $0.00250
Opus 5 $0.00008 $0.00125
Sonnet 5 $0.00003 $0.00050
Haiku 4.5 $0.00002 $0.00025

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

Security

Grade A, and why

check 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/check.md · 29 lines

What it actually says

/aisync:check

Run aisync check to verify that all tool-native files are in sync with canonical .ai/ content. This command is designed for CI pipelines — it exits with a non-zero status code if drift is detected.

Usage

  1. Run the command:

    aisync check
    
  2. Interpret the result:

    • Exit code 0 — All tools are in sync. Report a pass to the user.
    • Non-zero exit code — Drift detected. Report a fail and show which files are out of sync.
  3. On failure, suggest running /aisync:sync to resolve the drift:

    Sync check failed — some tool-native files have drifted from canonical .ai/ content. Run /aisync:sync to bring them back in line.

Notes

  • This is the recommended command for CI/CD integration and pre-commit hooks.
  • Use /aisync:diff to see the specific differences before syncing.
  • The command is read-only — it never modifies 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 · 29 lines · 15 tokens per session scan A 991bbfd402e6

Subscribe to this mod's changes

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