sync

A command that rebuilds the add-on's project knowledge from the current codebase, then checks evidence, documentation drift, and overall health.

In plain words
What is it for?
Use it to perform a full project sync, find mismatches between documentation and code, and view the resulting health report.
Why use it?
It helps bring stored project information back in line after the code has changed, reducing stale or unsupported documentation.

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/benrben/mpga/sync
Clone the repo
git clone --depth 1 https://github.com/benrben/MPGA
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 122 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.00000 $0.00122
Opus 5 $0.00000 $0.00061
Sonnet 5 $0.00000 $0.00024
Haiku 4.5 $0.00000 $0.00012

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

Security

Grade A, and why

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.

mpga-plugin/commands/sync.md · 17 lines

What it actually says

/mpga:sync

Rebuild the MPGA knowledge layer from the current codebase state. Tremendous rebuild, believe me. No fake docs — Evidence First.

Steps

  1. Check if MPGA is initialized, init if needed
  2. Run full sync: mpga sync --full
  3. Verify evidence health: mpga evidence verify
  4. Run drift check: mpga drift --report
  5. Show health report: mpga health — Very, very special report. Enjoy!

Usage

/mpga:sync
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 · 17 lines · 0 tokens per session scan A 8e5195ef530f

Subscribe to this mod's changes

sync is a command published in the GitHub repository benrben/MPGA (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 122 tokens. 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.